I have a software application called appTranslator that I have used for many years to manage language translations. It comes with a appTranslatorTESetup (Translator Edition) that i give our translators.
Today I supplied the download link to a user and he was not able to install it. The software was compiled in 2007 so I am assuming it was using the Visual C++ Redistributable 2005.
I looked at the official Microsoft page here. I can see:
Visual Studio 2015, 2017 and 2019
Visual Studio 2013
Visual Studio 2012
Visual Studio 2010
Visual Studio 2008 SP1
Concerning version 2008 it states:
Visual Studio 2008 reached end of support on April 10, 2018. To aid the discovery of the latest downloads, the links are retained currently, but may be removed in the future.
After another search I came up with:
Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update
Is this considered the latest official available edition?
I can confirm that the link I provided is the latest 2005 redist download.
And when my user installed it they were able to run appTranslatorTE.
It may be worth keeping a copy of these redist downloads for legacy app support.
As of 16-04-2022 the link is valid:
I do have some VS2005 Redist downloads on my DropBox folder in some languages:
Not sure of the est way to make these available for all as an alternative download.
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 recently got a copy of Microsoft Test Professional 2013, where previously I used Visual Studio 2012. I'm unable to run any projects within Visual Studio 2013 - Shell Integrated, which comes with Test Professional 2013.
The development team have upgraded to Visual Studio 2013 with no issues and we have tried changing the project versions.
I have checked that I have the correct .net framework and mvc installed.
Should I be able to open the projects and if so what might be going wrong?
I have some compatibility problems with vs 2010 file opened in vs 2013, i have read that maybe i can solve it activating the option "upgrade project automaticcaly" but i can't find it. Where i can find this option in Visual Studio 2013 Express?
EDIT
I can't launch the project ,i have tried in VS2010 Express , VS2012 Express , VS2013 Express... It seems so strange, it's an official demo of kinect sdk.
EDIT
Suddenly it starts work on visual studio 2010
It's not a project upgrade issue but the sounds of that error message - VS2013 Express doesn't support the project type you are trying to open.
The following page describes the s/w requirements for use that project
Kinect or Windows SDK
Specifically the s/w dev requirements are:
Visual Studio 2010, or Visual Studio 2012. The free Express editions can be downloaded from Microsoft Visual Studio 2010 Express or Microsoft Visual Studio 2012 Express.
.NET Framework 4 (installed with Visual Studio 2010), or .NET Framework 4.5 (installed with Visual Studio 2012).
There are a lot of other requirements also listed on that page.
I would suggest you download VS2012 Express (its free) and work from there.
I recently installed Visual Studio 2010 Premium at my work computer. I'm evaluating the installation of the VS2010 SP1 Beta to adjust many little problems that I've noted in using VS2010.
But I don't know if the SP1 Beta is rollbackable or if If'll have to reinstall all the VS2010 when the final SP1 will arrive to us.
Could anyone advise me about the opportunity to do this?
thanks a lot
rob
From Scott Hanselman's blog:
•If you install VS2010 SP1 beta, don't
uninstall it if you can avoid it.
Rather, wait for SP1 final which will
upgrade your beta cleanly and leave
you in the best state.
This is a copy from the readme file at http://go.microsoft.com/fwlink/?LinkId=207141 :
2.2. Uninstalling
2.2.1. On computers that have earlier versions of Visual Studio
2.2.1.1. Uninstalling Visual Studio 2010 SP1 Beta removes features in
Visual Studio Tools for Office and
Visual Studio Tools for SharePoint
Uninstalling Visual Studio 2010 SP1
Beta removes the Visual Studio Tools
for Office (VSTO) Design Time and some
features of Visual Studio Tools for
SharePoint. The Office and Sharepoint
features in Visual Studio 2010 SP1
Beta are major upgrades and have
different product guids than those in
the Visual Studio 2010 original
release. Therefore, when SP1 Beta is
removed, the features are removed, and
the Visual Studio 2010
original-release versions must be
reinstalled.
To resolve this issue:
In Windows Control Panel, click
Uninstall a program. In the list of
programs, right-click Microsoft Visual
Studio 2010 and then click
Uninstall/Change. In the Maintenance
Mode dialog box, click Next and then
click Add or Remove Features. Select
the following features. Microsoft
Office Developer Tools (x86) or (x64)
for Office development. Microsoft
SharePoint Developer Tools for
SharePoint development. Click Update.
2.2.1.2. Uninstalling Visual Studio 2010 SP1 Beta may not donwload all
required packages
When Visual Studio 2010 SP1 Beta is
uninstalled by using Add/Remove
Programs in the Control Panel, a
prompt for source may be displayed.
To avoid this, run setup.exe from the
original location, and uninstall by
using Setup Maintenence Mode.
To resolve this issue:
Navigate to the original installation
location for Visual Studio 2010 SP1
Beta . Run setup.exe. Select Remove.
Update
Regarding your comment below, yes, I installed VS 2010 SP1 Beta, here are the problems I got:
I couldn't install Visual Studio SDK - Fixed - I found there was newer version for VS2010SP1Beta that I didn't realize at first.
I could not install Phone Developer SDK - Fixed as unrelated - I contacted #ScottGU and they said this is test scenario, I downloaded again and it worked as a charm
Few issues about Resharper or so (can't remember exactly, but minor for sure) - Fixed - I just got a recent build of Resharper.
If this leads to the question "Should I install it?", I'd say, if you need any of the new features in it (see http://msdn.microsoft.com/en-us/library/gg442059.aspx for listing), then just install it. It's OK. If not, wait for RTM.
BTW,
If you want to discuss your specific SP1 issues instead of uninstall, no problem in that as well :)