My system is having VS 2015 and windows 7 Enterprise.
I have some solution file, which was created in vs 2008.
After opening in vs 2008, there are some upgraded log from vs 2015.
a lot of errors needs to be resolved to make build successed.
Is it ok to install visual studio 2008 over visual studio 2015 ?
this link Can I install two different versions of Visual Studio on the same computer? does not tell if it is ok to install lower version over higher version.
It's possible, but with a bit of risk that some features of the newer VS will break. I have no experience with these two combined, but in the past things got broken for me after installing vs2005 after vs2008 or vs2010. A re-install of the newer version would be needed if this happens.
Generally, it is ok. You can have many different visual studios installed on your machine.
Related
I am currently using Visual Studio 2015 for programming ASP.NET Core applications. I have the following questions regarding installing Visual Studio 2017:
What is considered to be best practice and/or cleanest method?
Should I install Visual Studio 2017 beside Visual Studio 2015?
Should I first uninstall Visual Studio 2015 and all .NET Core dependencies and then install Visual Studio 2017?
Are there any tools that would ensure a clean uninstall of Visual Studio 2015?
From page Visual Studio 2017 Platform Targeting and Compatibility
Compatibility with Previous Releases Installation
You can install and use Visual Studio 2017 alongside previous versions of Visual Studio, including Visual Studio 2015, Visual Studio 2013, and Visua Studio 2012.
So yes. you can install them without any problem.
VS 2013, VS 2015, and VS 2017 all work well side-by-side. VS 2012 can be a little dodgy on Windows 10, but should also work side-by-side. In theory VS 2010 should also work side-by-side with those, but I've run into quirks in the past with them interfering with one-another.
Projects should round-trip between 2015 and 2017 generally, although there are some one-way upgrade scenarios.
Note that if you really just need the older compiler toolset for some reason, you can also install VS 2017 and select the optional component Microsoft.VisualStudio.Component.VC.140 which installs the older v140 compiler which you can still use with the VS 2017 IDE. That said, there's not a lot of reason to do this since the VS 2015 & VS 2017 C++ standard libraries are binary compatible so you can mix them in a project.
See this blog post for information on VS 2017.
It sounds like you have done some projects in 2015 already, so you will probably want to keep it.
Once you open a project in a new version, it will try to upgrade the project and then you can't go back.
However, if you have multiple versions installed at the same time, when you try to open a project, say, from Windows Explorer, it will open it with the "Visual Studio Version Checker" and will look at the project file and determine which version to open it in.
Bottom line, if you have the hard drive space, there is no reason to not install them alongside each other.
In the past, it was recommended to install them in sequential order if you are installing multiple versions, but it doesn't sound like this is an issue for you and I don't know if that is even a problem anymore as it has been several versions since I have had to deal with that.
Good luck!
Personally, I would keep both - there have been multiple times through the years where you have compatibility issues and NEED to have the prior version(s). I've also had old project that will not upgrade and I've gone back and reinstalled old VS versions.
If you have no reason to keep VS2015 in your computer I would suggest uninstalling it.
I uninstalled VS2015 after installing VS2017 and later noticing that I was still using an old taskbar shortcut to VS2015.
So I was inadvertently still using VS2015.
Maybe some special cases require keeping older versions of VS along side the new version, but for the rest of us, I say, uninstall!
VS 2015 is the last version that is supported by Installshield LE.
If you have a need for building installers in the future, it will be useful to have VS 2015
1,2,3. Visual Studio 2017 has more features over 2015 and it contains 2015's current features so you don't need 2015 alongside 2017. Just stick with 2017. And I don't think you will have any problems while opening 2013 and 2015 projects with Visual Studio 2017.
Uninstall Tool is a good tool to use. It cleanses all the leftover files and registry entries after running the original uninstallation wizard and even tells you how many files will be cleaned after the required reboot.
For people continuing to read this, I have Visual Studio Professional 2008 (For Windows Embedded 6.5), 2010, 2015, 2017 and they all work even if open at the same time.
Edit: As stated in other answers, they need to be installed from oldest version to newest.
I have installed Visual Studio 2013 Pro and then I wanted to install Windows Phone 8 SDK. But it installed Express Edition of VS 2012. Now if I delete VS 2013, what happens with my VS 2012? Can I delete it, because I don't have enough memory for it? Can you help me, please!
They are independent, you can uninstal one without influencing the other.
You can install this version of Visual Studio on a computer that already has an earlier version installed.
but
If you uninstall a version of Visual Studio on a computer that has more than one version installed, the file associations for Visual Studio are removed for all versions.
More information : http://msdn.microsoft.com/en-us/library/ms246609.aspx
I cam across this question here on SE:
Can Visual Studio 2012 be installed side-by-side w/ Visual Studio 2010?
According to one comment with a good amount of upvotes, having 2010 and 2012 installed at the same time can present issues. I then came across this MSDN page about 2013:
http://msdn.microsoft.com/en-us/library/hh266747.aspx
If you use Visual Studio 2013 together with Visual Studio 2012 or Visual Studio 2010 SP1, you can [blah blah]
That suggests that 2013 can be safely installed along with VS2012. Can anyone confirm?
Take a look at Brian Harry´s Blog post announcing Visual Studio 2013.
VS 2013 can be installed side by side with previous versions of Visual Studio or, if you have a VS 2013 pre-release, it can be installed straight over top of the pre-release. TFS 2013 cannot be installed side by side but can also be installed over top of either a previous version (TFS 2012 or TFS 2010) or a pre-release.
Looks like you can, yes.
You can install this version of Visual Studio on a computer that
already has an earlier version installed.
http://msdn.microsoft.com/en-us/library/ms246609%28v=vs.120%29.aspx
Only issue I can see is during uninstallation, where the file associations may get lost.
I was having two installation on my computer. Really no problems.
From personal experience, I've come across multiple issues with using Visual Studio 2012 and prior, while a VS2013 installation exists on a machine.
Some of the issues include built executables failing to launch (double clicking .exe does nothing, but debugging them in VS launches them), and inability to compile solutions that mix C# and C++ projects.
I would avoid 2013 until these issues are resolved, as just having it installed on a machine breaks older code, even if you don't use VS2013.
There are some minor (compatibility) issues between using both VS2010 and VS2012 on the same Solution, but simply having VS2012 installed on your machine won't effect anything in VS2010.
There may be compatibility issues with 2013 Community edition. I had VS 2012 Ultimate and VS 2013 Express installed and working without any issue, but as soon as I installed VS 2013 Community, my VS 2012 Ultimate install has been behaving unusually. When I first open VS 2012 U, there is a really long load time. When I perform some action (open a file, select a menu option, anything actually) I have to minimize and maximize VS 2012 U for the screen to refresh. I am still trying to figure it out myself - so if anyone has a solution, please share.
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.
I recently installed Visual Studio Professional 2010 Beta 1 and noticed that most of the install directories were independent of "shared" directories (I have Visual Studio C++ 2008 Express installed and didn't notice any conflicts). If I install the full version (non-beta/trialware), of VS 2008 TS, will it conflict at all with the VS 2010 Beta 1 install ? I probably should have installed VS 2008 TS first...
Thanks
Though the reverse would probably be the better choice, I've done exactly as you've described and have not run into problems on that machine yet. Both installations seem to run fine independent of each other.