Dienstag, 29. Mai 2012 12:18
Hello all, (and apolgies if this in the wrong forum),
We currently build all of our software with visual studio 2008, and we ship our software package with vcredist installers. We obtained these long ago, these are the ones for visual studio 2008.
We are now planning on building our software with a mixture of visual studio 2008 and visual studio 2010. The apps built with vc2010 complain about not finding 'msvcr100.dll', whereas the ones build with vc2008 do not. This problem is solved by packaging msvcr100.dll in with the install package (as out install app needs to see it), and we package the new (vs2010 version) vcredist.
My question is, when we ship our software package, built with a mixture of vs2008 and vs2010, do we need to package both the 2008 and 2010 versions of vcredist, or just the 2010 one?
Another question, since the user is likely running the install prior to installing the 2010 vcredist (our install installs it for them), we have to have the msvcr100.dll in the installation folder (so the install app can see it). Are we missing something, is there a better way then to explicitally include msvcr100.dll in this folder?
Thank you for your time.
Edit: To answer my own first question, Programs built with Vs2008 require the vcredist for 2008 on XP but not on Win7 (i imagine they are already present on Win7). Programs built with Vs2010 require the vcredist for 2010 on all systems.
Installing vcredist for 2010 does not give you support for programs built with Vs2008, so both vcredists are required.
vcredist for 2010 requires Windows installer v3.1 which is available in XP-sp3 onwards. There is a redistributable that can be used to install v3.1 on previous OS's (seems funny though that we have to install a redistributable to install a redistributable!).
Still require an answer to my second question though ...
- Verschoben Cindy Meister MVPMVP Dienstag, 29. Mai 2012 16:48 not VSTO-technology related (From:Visual Studio Tools for Office)
Dienstag, 29. Mai 2012 13:08deploying to private folder all dlls required for your custom install app is the best way, imho. Of course you can always try to use available frameworks for deploying software, like msi or installshield (or any other that are free).
Dienstag, 29. Mai 2012 20:58ModeratorVisit http://social.msdn.microsoft.com/Forums/en/vcgeneral/threads for help in redistributing Visual C++ files.
The following is signature, not part of post
Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.
Visual C++ MVP