If you are installing a single machine with both SQL Server Developer or Enterprise Edition as well as Visual Studio 2010, you may encounter an unusual issue with recognition of the Visual Studio 2010 Service Pack (SP1): http://samirvaidya.blogspot.com/2012/06/visual-studio-sdk-you-must-have.html
This actually occurs in the scenario where you install SQL Server 2012 with SQL Server Data Tools after you have already installed Visual Studio 2010 with SP1. Since SQL Server Data Tools is its own version of the Visual Studio 2010 IDE, it removes the registry flag that indicates that SP1 for Visual Studio 2010 was installed successfully.
Therefore, when you later attempt to install a program that has a Visual Studio 2010 SP1 dependency (such as the Visual Studio 2010 SP1 SDK), you will get a failure upon installation!!
So, if you want to avoid this error message, you can either install SQL Server 2012 before installing Visual Studio 2010 with SP1 or use the registry hack that I provided in the article above to work around this problem.
This actually occurs in the scenario where you install SQL Server 2012 with SQL Server Data Tools after you have already installed Visual Studio 2010 with SP1. Since SQL Server Data Tools is its own version of the Visual Studio 2010 IDE, it removes the registry flag that indicates that SP1 for Visual Studio 2010 was installed successfully.
Therefore, when you later attempt to install a program that has a Visual Studio 2010 SP1 dependency (such as the Visual Studio 2010 SP1 SDK), you will get a failure upon installation!!
So, if you want to avoid this error message, you can either install SQL Server 2012 before installing Visual Studio 2010 with SP1 or use the registry hack that I provided in the article above to work around this problem.
which one has to install first,whether Visual Studio 2012 or SQL Server 2012??
ReplyDeleteThis only affects Visual Studio 2010 installations. If you are using Visual Studio 2012, you will not be affected.
ReplyDelete