Skip to content
This repository was archived by the owner on Dec 12, 2020. It is now read-only.

Conversation

@amis92
Copy link
Collaborator

@amis92 amis92 commented Apr 10, 2019

So, since the project right now is completely independent of Visual Studio version, I've upgraded Roslyn to v3.0 and targeted netstandard2.0, and the tool itself now targets netcoreapp2.1.

The only requirements are:

  • SDK-style csproj for DotNetCliTool to resolve and
  • .NET Core SDK 2.1+ to run it

Thanks to CodeGeneration.Roslyn not integrating with MSBuild now, the tool runs as a .NET Core app completely independent of all the other parts (VS, MSBuild, platform etc). The price is that we always use our own Roslyn version which we need to update manually.

Triggered by, and closes #124

@amis92 amis92 requested a review from AArnott April 10, 2019 21:11
@amis92
Copy link
Collaborator Author

amis92 commented Apr 10, 2019

Also, @AArnott - after it's merged, can you create a release? :)

Copy link
Owner

@AArnott AArnott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@amis92 amis92 merged commit 2e4498c into master Apr 18, 2019
@amis92 amis92 deleted the feature/netstandard2 branch April 18, 2019 16:24
@amis92 amis92 added this to the 0.6 milestone Jun 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Catching up the dotnet standard

3 participants