After stepping away from this project for a few weeks, I returned to discover that my primary local development environment no longer works correctly to build the project as I last left it.
(For various reasons, my environment has been migrated to the latest .NET Core tooling, which is now using MSBuild instead of the project.json format. This is an inevitable change, and so I'm prolonging it no further.)
So, let's make it official!
Migrate all Tug projects to the new MSBuild .csproj project format and replace the global.json file with an MSBuild solution file. In doing so we're upgrading the minimum required .NET Core tooling to the latest .NET Core SDK, as of this writing, this is RC4 or more specifically 1.0.0-rc4-004771 with the .NET Core Current runtime, namely 1.1.
Note, we're targeting the Current release (1.1.x) versus the LTS release (1.0.x) of .NET Core.
I expect this will be the last pre-release version of the SDK toolset before the final release on March 7. In my testing and experience, this RC4 release has already shown to be stable enough to be usable.
ebekker
commented
7 years ago
After stepping away from this project for a few weeks, I returned to discover that my primary local development environment no longer works correctly to build the project as I last left it.
(For various reasons, my environment has been migrated to the latest .NET Core tooling, which is now using MSBuild instead of the project.json format. This is an inevitable change, and so I'm prolonging it no further.)
So, let's make it official!
Migrate all Tug projects to the new MSBuild
.csprojproject format and replace the global.json file with an MSBuild solution file. In doing so we're upgrading the minimum required .NET Core tooling to the latest .NET Core SDK, as of this writing, this is RC4 or more specifically1.0.0-rc4-004771with the .NET Core Current runtime, namely 1.1.Note, we're targeting the Current release (1.1.x) versus the LTS release (1.0.x) of .NET Core.
I expect this will be the last pre-release version of the SDK toolset before the final release on March 7. In my testing and experience, this RC4 release has already shown to be stable enough to be usable.