What’s New in Visual Studio 2017 + VS Code


Track: NET321

Presenter: Adam Cogan

There are a couple of presenters who’s talks you pretty much always want to catch. They’re the type of presenters that are truly engaging and create talks that make you think wow, that was quick. Adam is one of those presenters. The video above is not actually the one recorded at Ignite. For some reason, the official channel 9 version is currently available.

Never the less Adam is invariably given the opportunity to introduce us to what’s new in Visual Studio, he has done so for 16 years, and this year was no different. Since Ignite 2017 was just a couple of weeks before the official launch of Visual Studio 2017 it meant there was plenty of new stuff to get excited about.

One of the most notable things about the session was Adam’s method of protecting himself from “bugs” during the demos… he didn’t do live demos, they were either pre-recorded and talked to or they were powerpoint screen grabs. That being said I don’t think it took anything away from the experience. He still communicated everything he needed to and I don’t think he would have added anything extra if he’d been typing the commands manually. The best part was that he was able to be 100% certain that what he wanted to happen would happen.

I’ve used Visual Studio 2017 for a month now and can say that so far I’ve not been disappointed, it doesn’t feel unfamiliar. Everything I use is where I would normally find it and they’ve really done some fantastic work to keep the process of writing and refactoring code smooth. The new VS 2017 debugger introduces a much cleaner exception dialogue. All the stuff I normally ignore is gone…reducing cognitive load.

The new null reference dialogue is also super helpful, but only works in .NET 4.6.2, disappointing.

Of all the things that Adam showed the item I most want to sink my teeth into is Live Tests, which provides super useful feedback on which parts of your code base are covered by tests and which are not. In addition, you get live feedback as you modify your code in regards to what additional unit tests are going to be needed or which tests have just been fixed or broken by changes.

From this…

into this…

without clicking run tests…magic!

After watching this version of the video I’m really intrigued to know why the Ignite video was pulled. The only bit I noticed that was missing was the bit in regards to Raygun plugging into CodeLens…but that seems like a rather innocuous reason to pull the video, plus it was just edited out of the SSW version. The mystery lives on.








Leave a Reply

Your email address will not be published. Required fields are marked *