Ferry Meidianto | /* Living in .NET World */

Jan/15

5

Installing Visual Studio 2012 after Visual Studio 2013

Although it’s recommended that we install Visual Studio versions in the order in which they were released (for example, install Visual Studio 2012 before we install Visual Studio 2013) as mentioned in http://msdn.microsoft.com/en-us/library/ms246609.aspx, there is possibility that we have installed Visual Studio 2013 before we know that we need to install Visual Studio 2012.

It happened to me last month. I actually more than happy to have Visual Studio 2013 only in my computer as I can also use it to open Visual Studio 2012 projects. But in the end I need to install Visual Studio 2012 because one of my teams are using Visual Studio 2012 and I don’t want any incompatibilities or project upgrades affect them.

If you have to install Visual Studio 2012 after Visual Studio 2013 for any reason, don’t worry, it can be installed without any issue.

I have been using this configuration almost a month and there is no issue at all. I mostly use them to do ASP.NET projects (and related, such as class library, etc) and I’m sure there is no issue with other project types too.

VS2013VS2012

· ·

5 comments

  • Zemmy Indrapatih · September 30, 2015 at 4:41 pm

    Yep.. You are right. I have install VS2012 after VS2013 and they work perfectly.

    Thank you for your information.

  • Mohan · September 20, 2016 at 7:18 pm

    I installed VS 2013 after installing 2015. Everything works perfectly. 🙂 Happy Coding…

  • Roberto · December 1, 2016 at 2:04 am

    What about Visual Studio 2015? Do you think it’s possible?

  • Admin comment by Ferry Meidianto · December 1, 2016 at 7:46 am

    It works on VS 2015 as well

  • Admin comment by Ferry Meidianto · December 1, 2016 at 7:48 am

    Yes, it’s. Glad that it works ok in your machine as well.

Leave a Reply

<<

>>

Theme Design by devolux.nh2.me

Disclaimer

All postings/content on this blog are provided "AS IS" with no warranties, and confer no rights. All entries in this blog are my opinion and don't necessarily reflect the opinion of my employer or sponsors. The content on this site is licensed under a Creative Commons Attribution By license.
To top