Hi,
I am having a dll that forms a part of a COM+ application. I have changed a piece of code and not touched any of the method signatures, hoping not to destroy the compatability. I have replaced the existing dll with my new one and restarted IIS and COM+ services that use this dll. Should i have to register the dll again or will it work (should it work )
Please respond as this is under a hot discussion with my team..
Many Thanks and Best Regards,
Franklin
COM+ Component registration for VB6 dll
DRoden
Thank you so much ! I have already tested and proved as you said. Things are fine. I will take this as a conformation and blow-off all those who say "may be this works in test environment..But..".. :-)
Thanks again !
Best Regards,
Franklin
bopritchard
This is a tricky issue: theoretically if you do not change any public contracts (this includes method signatures, type names, etc) then you can replace the DLL with the new one and it should work. It's best to test this in a closed environment first.
However, even if you can patch the DLL, it might not mean that your application will work - sometimes changing implementation detail (ie, those things not publically enforceable) might cause clients to break for a multitude of reasons.