Upgrading components without re-installing application that uses component 
Author Message
 Upgrading components without re-installing application that uses component


This is really more a question of how you manage your compatibility issues
across dependent components. If your interfaces didn't change, you can juset
unregister, copy over and re-register the component. If they did change, you
have no choice but to recompile the clients. There's no workaround for that.

Please post/reply to the newsgroup(s) so
that everyone can benefit from the discussion.


Klaus H. Probst, MCP

       ICQ: 22454937
      The VB Box: http://www.*-*-*.com/

What's the best way of doing this ... Is there a Windows standard for doing
this ..
Thanx in advance
Marlon Reid

Fri, 09 Nov 2001 03:00:00 GMT  
 [ 1 post ] 

 Relevant Pages 

1. Installing ActiveX Component Upgrade

2. MTS component install & component registry

3. VB4 16bit App runs from CD without installing components into windows\system

4. Error installing VB.NET component into COM+ Application

5. Installing windows components in Application Setup

6. VBA reinstall without Office install

7. Using a synchronous component in an asynchronous component

8. How to reinstall MDAC 2.5 on Win2k with Component Checker

9. Republishing a component using Visual Component Manager does not work

10. Can ocx components be used without forms?

11. COM+ error 80110501 when using Install Component Wizard

12. VB6 Learning Edition Install Problems when searching for installed components


Powered by phpBB® Forum Software