visual studio 2008 deployment project

Posted on 2009-04-16
Medium Priority
Last Modified: 2012-05-06
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?

Question by:OFGemini
  • 3
  • 2
LVL 15

Expert Comment

ID: 24160020
Sorry, I'm not getting why you want to overwrite dlls when doing the upgrade if their version hasn't changed.

Author Comment

ID: 24161640
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  So when I deploy the updated Interop dll it doesn't replace the existing interop DLL.
LVL 15

Accepted Solution

oobayly earned 2000 total points
ID: 24162144
Ah, makes sense.

No chance of you telling the vendors to sort themselves out and version their products properly is there :-)

Versioning a COM Interop dll is possible by creating the interop dll yourself, and adding it as a reference to your project:
tlbimp.exe {0}.dll /strictref /namespace:{0} /out:Interop.{0}.dll
where {0} is the name of dll
ie. TlbImp.exe /out:Interop.AAC_DLib.dll /namespace:AAC_DLib.dll /asmversion:5.1.2600.0 c:\WINDOWS\system32\iashlpr.dll

TlbImp.exe is in in my Microsoft SDK directory.
Source: http://www.jonorossi.com/blog/archive/2009/01/04/creating-com-interop-assemblies-like-visual-studio.aspx


Author Comment

ID: 24163212
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.
LVL 15

Expert Comment

ID: 24163540
Just had a look at the Resourse Hacker tool I've got on my machine:

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 :-)

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The object model of .Net can be overwhelming at times – so overwhelming that quite trivial tasks often take hours of research. In this case, the task at hand was to populate the datagrid from SQL Server database in Visual Studio 2008 Windows applica…
Many of us here at EE write code. Many of us write exceptional code; just as many of us write exception-prone code. As we all should know, exceptions are a mechanism for handling errors which are typically out of our control. From database errors, t…
Screencast - Getting to Know the Pipeline
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…
Suggested Courses

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question