asked on MS visual studio 2005 not opening after installing office 2013
Recently I installed Microsoft Office 2013 on my laptop. I first did a complete uninstall of the existing Office 2010 installation using a hotfix from Mircosoft.
After this installation I realized that Microsoft Visual Studio 2005 no longer starts. I need this to develop Reporting Services reports as our RS server is still running on SQL 2005. I tried doing a repair, but when I look up the vs_install.msi file it tells me the location is unavailable. This version of VS came installed with the SQL Server installation on my laptop. It's the Premier Partner edition.
Anyone have any idea how I can get this to work again without having to re-install half my laptop?
Thanks.
After this installation I realized that Microsoft Visual Studio 2005 no longer starts. I need this to develop Reporting Services reports as our RS server is still running on SQL 2005. I tried doing a repair, but when I look up the vs_install.msi file it tells me the location is unavailable. This version of VS came installed with the SQL Server installation on my laptop. It's the Premier Partner edition.
Anyone have any idea how I can get this to work again without having to re-install half my laptop?
Thanks.
Microsoft OfficeMicrosoft DevelopmentMicrosoft SQL Server 2005
Last Comment
Koen Van Wielink
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks Sara, will give that a whirl.
ASKER
Hi Sara,
Was not able to get any more error messages to find out where things go wrong, but eventually I managed to get things going again by installing VS2005 SP1 from the MSDN site. Initially it didn't seem to work, but I think a restart and registry clean up did the trick afterwards.
Thanks!
Was not able to get any more error messages to find out where things go wrong, but eventually I managed to get things going again by installing VS2005 SP1 from the MSDN site. Initially it didn't seem to work, but I think a restart and registry clean up did the trick afterwards.
Thanks!