First, in addition to installing VS 2017 you also need to install VS 2010 on the same machine with your VS 2008.
This ensures that the appropriate MSBuild scripts that enable targeting VS 2008 are installed (they only ship with VS 2010).
It’s kind of a big secret since your colleagues won’t know how you suddenly increased your productivity so much! Once the cat is out of the bag, everyone could be using VS 2017 around the office — our whole team here in Redmond agrees that’s a good thing (and…
we’re not biased at all) PS: What you’ll notice is that everyone in the team will see the same upgrade prompt the first time they load the project in VS 2017.
To wrap things up, here it is – the link to download Visual Studio 2017.
Downloads for earlier versions of Visual Studio are available on my.
There are many reasons why you may want to use Visual Studio 2017 in your day-to-day job.
Just to name a few: If these cover your reasons for not using VS 2017, I’m going to let you in on a little secret: you can start using Visual Studio 2017 today without having to change your toolset version (i.e. Well, it’s not really a secret that Visual Studio supports native multi-targeting and round-tripping.
Diagnostic Tools support for apps running on One Core devices, including Holo Lens and IOT, has been added in Update 3.When the upgrade completes, you will get an upgrade log report.If there are any errors or warnings for any of your projects, you should review the log carefully and make sure that you acknowledge the changes presented and follow up on any action items listed there.Because you chose not to upgrade your project, VS 2017 doesn’t make changes to your project or solution.So the fact that you’re using VS 2017 in your day-to-day work might as well be your little secret – the rest of your team will continue to use the older version without any clue that you’ve upgraded.Since you want to stay with the older compiler and libraries version, you should decline by hitting the “Cancel” button – you can always upgrade later too if you choose to experiment with the latest C toolset.Now every time you build in VS 2017, the binaries that get generated are fully compatible with the ones you were previously building in your older version, e.g. That’s because behind the scenes, VS 2017 delegates the build to the same C compiler and consumes the same libraries that your older IDE ships with.Using these features means that you will be taking advantage of the latest IDE features in VS 2017 without also taking advantage of the latest advances in the C compiler, libraries and build tools (e.g. Disclaimer: there are IDE features that also depend on the latest toolset capabilities and they will be incompatible with older toolsets: e.g.type information will be missing in the Memory Profiler, and the refactoring operation “Convert to Raw string literals” will generate C 11-compliant code, making it not compile with VS 2012 compilers and older.This is a subscription-based site, but anyone can create a free Dev Essentials subscription.Please see the Dev Essentials page for more information.