Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Visual Studio 2017

See original GitHub issue

On March 7 is Visual Studio 2017 launched . One of the big news is that csproj file will be greatly simplified and supports multi-targets.

Additionally, Microsoft now recommend that we should use .NET standard for packages. In this case, we should replace the .NET Framework 4.6 with .NET 1.3 Standard

Today we have two separate projects, one for .NET 4.0 and .NET 4.6. I recommend that we replace these with a single project in VS2017-format that multi-target to net4.0 and netstandard1.3 (the same as .NET 4.6).

Open questions

When do AppVeyor support Visual Studio 2017?
Is it possible to open the new csproj-file in older Visual Studio (probably not).
- If not possible to open in older Visual Studio, is it a problem?
  - If it is a problem, how long should we wait for all devs to update to Visual Studio 2017?
Should we maybe have a separate csproj file in the old format to make it possible for users of old Visual Studio to compile? It is enough that there is a project file only for .NET 4.6 (or .NET 4.0). The downside is that the environment becomes more complicated when we have to make sure to keep this project file up to-date when we do not use it.