/CsprojToVs2017

Tooling for converting pre 2017 project to the new Visual Studio 2017 format.

Primary LanguageC#MIT LicenseMIT

Build status NuGet Version NuGet Downloads Global Tool NuGet Version Global Tool NuGet Downloads

Convert your old project files to the new 2017 format

With the introduction of Visual Studio 2017, Microsoft added some optimizations to how a project file can be set up. However, no tooling was made available that performed this conversion as it was not necessary to do since Visual Studio 2017 would work with the old format too.

This project converts an existing csproj to the new format, shortening the project file and using all the nice new features that are part of Visual Studio 2017.

What does it fix?

There are a number of things that VS2017 handles differently that are performed by this tool:

  1. Include files using a wildcard as opposed to specifying every single file
  2. A more succinct way of defining project references
  3. A more succinct way of handling NuGet package references
  4. Moving some of the attributes that used to be defined in AssemblyInfo.cs into the project file
  5. Defining the NuGet package definition as part of the project file

How it works

As a Net Core Global Tool

Assuming you have net core 2.1 installed you can run this on the command line: dotnet tool install Project2015To2017.Cli --global This will install the tool for you to use it anywhere you would like. You can then call the tool as shown in the examples below.

As a normal file download

Using the tool is simple, it is a simple command line utility that has a single argument being the project file, solution file or folder you would like to convert. When you give it a directory path, the tool will discover all csproj files nested in it.

Examples

Below examples are for the global tool, for the normal file just replace csproj-to-2017 with your executable.

csproj-to-2017 "D:\Path\To\My\TestProject.csproj"

Or

csproj-to-2017 "D:\Path\To\My\TestProject.sln"

Or

csproj-to-2017 "D:\Path\To\My\Directory"

After confirming this is an old style project file, it will start performing the conversion. When it has gathered all the data it needs it first creates a backup of the old files and puts them into a backup folder and then generates a new project file in the new format.

Flags

  • --dry-run will not update any files, just outputs all the messages
  • --no-backup will not create a backup folder
  • --assembly-info keep Assembly Info in a file
  • --target-frameworks specific target frameworks
  • --output-path will not create a subfolder with the target framework in the output path