I'm glad DLL hell is gone, but having 50, or 100 of the "same" DLL deployed doesn't strike me as nirvana either. And woudln't you want to know when you've broken the signature/interface of a DLL? Isn't that just good software engineeing?
----- Herfried K. Wagner [MVP] wrote: -----
* Roy Osherove <ro**@iserializable.com> scripsit:
There is no need for binary conpatebility with .net. the whole "DLL
Hell" thing tht we had with COM is old news. You should ditribute your
aoolication's dependecies along with your application (so basically
you can have 50 versions of the same DLL lying around the user's
machine).
ACK. More information on this topic can be found here:
Components and Assemblies
<http://msdn.microsoft.com/library/en-us/vbcon/html/vbconComponentsAssemblies.asp>>> How do you maintain VB6 like Binary Compatibility in .net?
--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>