Windows 10: Visual studio 2017 and 2015 any conflict?

Hi all tech sifus and gurus, I plan to install Windows 10 Creators Update. After that, I am going to install Microsoft Visual Studio 2015 and 2017 editions.

Will Windows 10 Creators Update have issue with both visual studio?

Will there be any issue with the both visual studio when install? Will there be any coding issues because they are different editions. I am using it for vb.net programming.

:)

 

Windows WDK on Visual Studio 2017 Community

John you are correct, Windows WDK is not currently supported on Visual Studio 2017. Windows WDK RS1 and RS2 are both supported on Visual Studio 2015.

Please Note: There is no need to uninstall Visual Studio 2017, you can run Visual Studio 2015 and 2017 side by side

 

How to completely uninstall Visual Studio 2015?

I installed Visual Studio 2015 earlier when it came out. I installed different components and various plug-ins. Since Visual Studio 2017 has come out I would like to completely uninstall Visual Studio 2015 before installing Visual Studio 2017.

Because I installed various components, it can be doubtful whether all of them are getting uninstalled or not, I want to completely uninstall Visual Studio 2015 and all of it's components and plug-ins and start from fresh and download Visual Studio 2017.

Can someone please guide me on how to do this?

Operating System - Windows 10 Pro

System Architecture - 64-bit

 

Whats the purpose of having both editions installed? Im not sure it will allow you to install both versions anyway. If you try to install 2017 after 2015, it may make you either upgrade the installation or uninstall the older one.

 

I am afraid that issues will happen between both visual studio. I am actually using the 2015 for my assignment and uni work purposes. On the other hand, I am using the 2017 for self-learning purposes.

 

No, it won't. MS has designed Visual Studio to work very well with multiple versions installed.

The reason people do this is that there are often significant changes between versions and moving to a newer version may cause issues, although this is becoming less and less common.

One important thing, though, is that while MS has gone to great lengths to support multiple simultaneous versions of VS and the .NET framework, there are still a few components that get upgraded to the latest version that are shared between versions. (ie. you can only have one version of those components per computer).