If you have an ASP.NET Core project that was working fine and you upgrade to Visual Studio 2017, you're bound to hit the Duplicate Content compile error. This will affect you regardless of which framework you use and affects both .NET Framework and .NET Core projects, even if you haven't upgraded to .NET Core 2.0.

In this post, I explain why it happens, why the change has been made, …

Microsoft has just released a round of major updates to the .NET stack. Visual Studio 2017 gets its biggest update yet. C# gets its first update to C# 7.1 as part of the faster release cadence enabled by Roslyn. The new open source frameworks .NET Core and ASP.NET Core both get their 2.0 releases and .NET Standard 2.0 has arrived to unify everything.

Over the last 16 hours I've been …

Every update I've applied to Visual Studio 2017 has broken Git again. Until 15.1 (26403.0), the solution was to delete Visual Studio's version of Git and let it pick up the version installed in Windows. I documented this in my post on troubleshooting the Visual Studio 2017 upgrade.

The problem manifests itself when you …

Go To Definition in Visual Studio 2017 has been bugging me for a while now. When I try to Go To Definition on some types, VS2017 pops up with an error "Cannot navigate to the symbol under the caret". Today, I decided it was time to try and figure it out.

This is not the first time this has happened and there are lots of people who experienced a similar error on VS2015. …

Visual Studio 2017 is now available, download it here. I've been converting my projects over to VS2017 and wanted to share my favorite features of the new IDE.

My favorites are Go To All, move type to matching file, string splitting, and coding conventions via EditorConfig. Other notable mentions are the overhauled Find All …

While upgrading several projects to Visual Studio 2017 I was caught out by three gotchas: I was unable to push changes to remote Git repositories, I had ASP.NET Core applications failing under both Kestrel and IIS Express, and I had ASP.NET Core projects that stopped working under Visual Studio 2015.

This post documents these three issues and provides the solutions I used to work …