OFGemini
asked on
visual studio 2008 deployment project
I recently upgraded my deployment project from VS 2005 to VS 2008 and I had problems with the deployment project not updating my DLLs because I was not incrementing the DLL's version # when I built a new version of my project. I resolved that issue by incrementing my DLLs when I build my deployment project. However I'm running into a problem with 3rd party DLLs. The 3rd party DLLs are being updated but the version # is not.
Is there a setting to make the Deployment project replace all my files when I update my application?
Is there a setting to make the Deployment project replace all my files when I update my application?
oobayly
Sorry, I'm not getting why you want to overwrite dlls when doing the upgrade if their version hasn't changed.
ASKER
I want to overwrite some 3rd party DLLs because some have been modified but not the version #s for the dlls were not incremented.
Also a COM component DLL from a 3rd party was updated and when I updated the reference in my project the new Interop DLL's version # is still 1.0.0.0. So when I deploy the updated Interop dll it doesn't replace the existing interop DLL.
Also a COM component DLL from a 3rd party was updated and when I updated the reference in my project the new Interop DLL's version # is still 1.0.0.0. So when I deploy the updated Interop dll it doesn't replace the existing interop DLL.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've asked the vendor to do that already. Its been on their todo list for awhile. :-)
I'll look into the Creating the interop DLL myself. Thanks.
I'll look into the Creating the interop DLL myself. Thanks.
Just had a look at the Resourse Hacker tool I've got on my machine:
http://angusj.com/resourcehacker/
You can modify the version of a DLL with this. Haven't tested whether it destroys a .Net dll whilst doing so, but I very much doubt it. It helpully makes a backup of it too (in case you forget).
It might be against the terms of use for a 3rd party dll, but to be honest not incrementing the version on a build isn't just lazy, it's very bad form. So you've got common sense on your side :-)
http://angusj.com/resourcehacker/
You can modify the version of a DLL with this. Haven't tested whether it destroys a .Net dll whilst doing so, but I very much doubt it. It helpully makes a backup of it too (in case you forget).
It might be against the terms of use for a 3rd party dll, but to be honest not incrementing the version on a build isn't just lazy, it's very bad form. So you've got common sense on your side :-)