I want to install Visual Studio 2005 on my machine which already has Visual Studio 2010?
Please help me out.
Bharat
It can easily be done -- My other laptop has VS 2005, 2008, and 2010 all on the same drive. The two versions shouldn't interfere with each other. Visual Studio even has a "version selector" that gets registered as the handler for project and solution files, and IIRC it should launch the correct version of VS for whatever project you're in at the time. But even if it doesn't, you can always right-click and "Open with...".
Related
Got a big problem with the Visual Studio 2017 Installer Projects Extension for Visual Studio 2017 Professional. I added a Visual Studio Installer Setup project to a solution and set it up the way it's basically supposed to be done (Primary Output in the Application Folder and an icon in the Desktop Folder is all that was needed). Then I right-clicked on the Setup project, clicked "Build" and then I get this:
Please wait while Windows configures Microsoft Visual Studio Professional 2013.
And then it stalls indefinitely. I have to close Visual Studio in Task Manager to stop everything. What's more, I'm Visual Studio Professional 2017, not 2013. I used to have Visual Studio 2013 Ultimate, but I uninstalled it. What could possibly be causing the confusion?
It appears that you have also got Visual Studio 2013 installed, and that there is as conflict between 2013 and 2017 because that message is a Windows Installer repair of VS 2013. Something is happening during your build that requires the VS 2013 installation to be repaired. The Windows Event Log (Application) will have an MsiInstaller log entry saying which component appears to be broken. If you post that information there may be a clue to the problem. If you (for example) have manually removed anything that may belong to the VS 2013 installed product then that would cause the same kind of problem.
You have this similar problem:
Rebuilding Visual Studio Installer project, launches Visual Studio 2013 seetup
Visual Studio 2015 msi build initiates another installation
When you say it stalls indefinitely, I would expect it to ask for the Visual Studio 2013 install image so that it can repair it. If you go to Programs&Features and manually repair VS 2013 it might fix the problem.
I also had Visual Studio 2013 installed as mentioned by #PhilDW.
Navigating to Event Viewer → Windows Logs → Application I found loads of warnings:
Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu', component '{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed. The resource 'C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\' does not exist.
The key here being that the folder C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\ did not exist thanks to an answer in the first link provided by #PhilDW.
Created the missing final folder URTInstallPath_GAC in the path mentioned and the installers now build really fast whereas before they used to take forever (sometimes literally!).
I recently started a new job, and got a machine with Visual Studio 2013 Proffesional installed. This would be great, except the colleague that I'm working with is using Visual Studio 2010. As far as I know, there is no way to work on the same project (or solution), without having quite a lot of issues, is this correct?
And if so, is it still possible to download Visual Studio 2010 (from a reliable source)? I cannot seem to find it anywhere in my MSDN subscriber downloads. All I can find is a stuff like service packs, tools, etc. Did they terminate the support of it?
You work on visual studio 2013 but there are option to select which version of visual studio you want select 2010 and run your project.
You should be able to open Visual Studio 2013 solutions in 2010, if you install Visual Studio 2010 SP1. There is a possibility that some project types won't be supported, but the solution should open.
I installed them in this order:
Install SQL Server 2012 SP1 x64
Visual Studio 2010
This is the proper order that other developers recommended and as i did.
The problem is, if SQL Server 2012 installed on the system, VS2010 shortcuts are not show up.
How can I fix this?
Note: OS is Windows 8.
This is a bug.
A workaround is to navigate to C:\ProgramData\Microsoft\Windows\Start
Menu\Programs\Microsoft Visual Studio 2010, right-click on the
shortcut called Microsoft Visual Studio 2010, and select Pin to Start.
After this, there will be two shortcuts targeting devenv (one titled
Microsoft SQL Server Data Tools and one titled Microsoft Visual Studio
2010)
Refer: http://connect.microsoft.com/VisualStudio/feedback/details/730276/after-installing-sql-server-2012-on-my-windows-8-pc-visual-studio-2010-shortcuts-disappeared
As the OP stated. I too installed SQL before VS. I always do. So I was baffled when i could not find my VS2010 shortcut.
It turns out that the icon is mis-named. If you open (or check the properties) of the icon in the Visual Studio 2010 start menu folder called "Sql Server Data Tools". You may find it is actually the VS 2010 IDE.
Workaround provided by
http://connect.microsoft.com/VisualStudio/feedback/details/730276/after-installing-sql-server-2012-on-my-windows-8-pc-visual-studio-2010-shortcuts-disappeared
Edit the shortcut start target. For instance. I made mine not display the splash page.
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /nosplash
Then repin it to the start menu (right click).
Installing Visual Studio 2010 SP1 seems to fix this as well, its available to download from here http://www.microsoft.com/en-us/download/details.aspx?id=23691 If you run devenv.exe it should prompt you to do this also.
I have a newly built Windows 8 VM with VS 2012 Premium running on it, when I try open any sln file I get the following modal pop up error
Visual Studio 2010 Shell
Invalid license data. Reinstall is required.
I can open the sln's if I open up VS and then do project open, this is really annoying, any ideas how I fix it?
*Note I have done a VS repair and it didn't solve it...and I never had any VS RC release on the machine, all new build with s/w downloaded from the MSDN
Cheers
I encountered the same exact error when I created a solution with a full version of Visual Studio 2012 Professional on one machine and then tried to open the solution file with a copy of Visual Studio 2012 Express on a different machine. I got the error when double-clicking the solution file, but not when loading the solution into an already opened instance.
I fixed the error by opening the solution file (.sln) with notepad and changing the line that says Visual Studio 2012 to say Visual Studio Express 2012 for Windows Desktop.
After that, I was able to double-click to open the solution file on the machine that has Express installed.
I'm using VS 2013. I fixed this by right clicking the .sln and setting the Open With parameter to visual studio 2013 and not VS version selector or VS 2010.
I have faced the same problem. When I set the system Date and Time to the current Date and Time, The Problem solved by itself.
It looks like the .sln extension is owned by "Visual Studio 2010 Shell" a minimal version of Visual Studio that ships with products like SQL Server and Office to provide support for add-in development without any other features. Since this is a minimal version, it's unable to load any project type that ships with Visual Studio Express, Professional or above.
The same may happen when you have Visual Studio Express installed next to a full version of Visual Studio.
This may happen when you install an older version of Office or SQL Server after having installed Visual Studio. The old installer will hijack the extension.
To repair this problem:
use the "Open With" option of Windows and select the "Visual Studio Version Selector" as your default action.
Or open the "Default Programs" option in Windows, look up the .sln extension and make sure it uses the "Visual Studio Version Selector" as default:
Or locate Visual Studio 2012 in the Programs and Features window of Windows and chose "Change", the Visual Studio installer will pop up, chose "Repair" to have it repair the file associations and any other problems that may arise by installing Visual Studio versions in reverse order (it may for example mess up the MsBuild directory as well).
Remember that when Visual Studio 2010 was released, it could not yet know what Visual Studio 2012 would change, as such, it's best to install versions of Visual Studio in the order they were released. This may sometimes prove difficult, as other products may install Visual Studio versions without you knowing.
can i install and use, visual studio 2008 and visual studio 2010 on the same windows xp/vista
have visual studio 2008 installed and working
wnat to install visual studio 2010 and use with 2008,
some solutions on 08 and some on 10..
any problems possible?
Yes, you can!
Can't add anything else, honestly! :)
Well, I personally have 2005, 2008 and 2010 installed on the same workstation, for various needs and projects. Works without any problem!
No problems at all running both Visual Studio 2008 and 2010 side-by-side. My development box is currently set up this way.
Solutions will automatically open in the version of Visual Studio that they were created in. You can manually choose to open them in a newer version, but you will need to update them. A wizard will automatically appear that guides you through the process.
Opening a solution saved with a newer version of VS in an older version is not a supported scenario.
But there is a workaround: simply open the *.sln file in a text editor (like Notepad) and decrement the version number by 1. You'll have to do the same thing for each of the project files.
I had the same problem with converting a Visual Studio 2008 project to 2010, which made the program could not compile at all with every measure i took.. then I installed Visual Studio 2008 again and it turns out they can be installed in the same computer and work, but you need to open visual basic 2008 manually if you want to develop a project there..
You shouldn't have any problems unless you try to develop for Windows Phone 7, which you can't currently, and may never be able to, do in Windows XP.