Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Because of bitset problem in vs2010, i will also install vs2008 which doesn’t have that bug. But as i remember, in my old experiences, there were a few conflicts in windows sdk. I don’t exactly remember but how can i fix these conflicts ? Or is there any conflict ?
The issue you might be referring to would be the Windows SDK config tool shipped with Windows SDK for Visual Studio 2008 had a serious bug in that it would fail to properly set the SDK version in the registry.
You can read about the issue here:
http://blogs.msdn.com/b/windowssdk/archive/2008/03/01/integrating-windows-sdk-and-vs-with-new-sdk-configuration-tool.aspx
As mentioned in the post there are various solutions to ensure that you’re building against the correct SDK version.
I personally have Visual Studio 2008, 2010 and 2012 RC1 installed with no issues thus far.
One minor gripe I had when I installed Visual Studio 2008 on top of 2010 was that it changed all of my file associations to point to 2008 instead of 2010. To fix this, you can open 2010 and go to Tools->Settings->Environment->General and press “Restore File Associations”.
Hope this helps!