Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
I have previously posted a few items about deploying the Visual C++ 8.0 runtime redistributable packages as a prerequisite for other setup packages:
Since then, I have started to get more in-depth questions about how the Visual Studio 2005 SP1 version of the VC runtime files affects application building and deployment. Most of these questions have been specific to how the VC runtime files themselves manage forward and backwards compatiblity and I don't have very much knowledge about how this works behind the scenes.
Fortunately, Nikola Dudar, a program manager on the VC team, recently sent me some really helpful links with more information about how Visual Studio 2005 SP1 impacts application development and deplopyment scenarios when the application in question depends on the VC runtime files. If you are a developer building and deploying applications that use the VC 8.0 runtime files, and you are evaluating Visual Studio 2005 SP1 for your development environment, I strongly encourage you to review the content in both of these links in order to better understand the ramifications of putting SP1 on your build machine: