DLL Deployment Question

[lucyv]

When I package up my application and distribute to my users, all of its references are placed into the same directory as my application.

If I make a modification that adds another reference to my project, will I have to re-install my application on every workstation, or could I get away with coping the new executable and references to each workstation?

I read somewhere that the .NET Framework gets away from "DLL Hell" by performing a true "XCopy". Is this true?

-lucyv

 

[chrissie1]

If I make a modification that adds another reference to my project, will I have to re-install my application on every workstation, or could I get away with coping the new executable and references to each workstation?

In theory, yeah.

I read somewhere that the .NET Framework gets away from "DLL Hell" by performing a true "XCopy". Is this true?

In theory, yeah. (Am I repeating myself?)
All depends on the what dll's you use. If there are com dll's that need to be registred you will need to make an install or do it manually. If you only use the framework then a true xcopy will do provided that the correct framework is installed on the system.




Christiaan Baes
Belgium

"Time for a new sig." - Me

 

[lucyv]

Chrissie, thanks for the reply. I am using some third party controls from a company that claims they are "True C#" controls. I would assume then that the "xcopy" would work. How can I tell if they are COM DLLs?

-lucyv

 

[chrissie1]

they are considered true comm dll's if you have to register them (regasm). Even if they say they are true C# they could be wrappers around a com but that shouldn't bother you.

Christiaan Baes
Belgium

"Time for a new sig." - Me

 

[lucyv]

Thank you.