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 previously posted a list of registry values that can be used to detect Visual Studio 2005 editions. I've started getting asked more often about how to detect Visual Studio 2008, so I decided to create a separate post with an equivalent list of registry values for the VS 2008 product family too.
Here is a list of the registry keys/values that can be used to detect each of the editions of Visual Studio 2008. In each case below, ProductDir is a REG_SZ value that contains the install root (which by default will be c:\Program Files\Microsoft Visual Studio 9.0).
If you do not care which edition is installed, you can use the following registry value to detect whether or not any edition of Visual Studio 2008 is installed:
9.0 is a REG_SZ value that specifies a fully qualified path to the Visual Studio 2008 root installation directory. By default, this value will be set to c:\Program Files\Microsoft Visual Studio 9.0, but will be different if the user has installed Visual Studio 2008 to a non-default path.
PingBack from http://myghillie.info/1969/12/31/how-to-determine-whether-a-vs-2008-product-is-installed-on-a-computer/
PingBack from http://msdnrss.thecoderblogs.com/2007/10/19/how-to-determine-whether-a-vs-2008-product-is-installed-on-a-computer/
PingBack from http://dougfinke.com/blog/?p=257
What about writing a script I can deploy on 30 machines and see what version/edition of Visual Studio is installed at each workstation?
If you feel like doing it, you can email it at massimiliano.polito at gmail . com, I'll be glad to test it :-)
Hi Massimiliano Polito - I'm sorry, but I don't have the time to create this type of script right now. It should be pretty straightforward for you to create something like this using the information in this blog post though. Please let me know if you run into any issues with any of the detection logic described in this post.