**RESOLVED**DLL Hell VB6 vs .NET

[JMvVliet]

Hello,

when I understand VB .NET well, I can make dll's, and use them in my program. When I compile my program, a dll is automatically copied to the directory where the executable is created (normally <proj. path>\<app. path>\bin).

I've tested this, edited my dll, and simply replaced that dll by the program, without recompiling the program. It worked! Even when I removed some stuff out of the classes in the dll!

So, my question is: does this always work, assuming that the functions and subs don't change, and also not the parameters, or are there any hidden tricks, that make it not working?

[kovan]

that is the general idea...
so if u get it broken u contact microsoft and tell them that millions if not billions of dollars they spent on .net just went down the drain

[JMvVliet]

thnx

[DevGrp]

Well considering you dont change method signitures, and parameters, everything should work.