Is there any way to release an application that references several DLL's - but have these DLL's located in one area. If I change a version of the DLL, it will be picked up by the application and used?
Printable View
Is there any way to release an application that references several DLL's - but have these DLL's located in one area. If I change a version of the DLL, it will be picked up by the application and used?
i didnt test this, but i think that u can safely replace the dll without
problem on the same location.
if it did not, just register it with regsrv32.exe (found in windows directory, or one of its subfolder )
hope this will help.
well, at least i guess this works on vb6, im not sure if this
changed on .NET.
You don't have to register DLL's in .NET though.
If they are in the GAC then you can.
But the GAC keeps each version of your DLL. So if my application is on a client machine and have DLL1 version 1, and I build DLL1 version 2 and want the application already on the client to use version 2, how do I do it?
I think I would be able to set up a policy in the .NET configuration settings, but I would still have to go to each client machine, which is what I am trying to avoid.
You would just keep the same strong name for the dll (I believe) and when you add the 2nd version you need to replace the old one with it instead of add it as a new one.