-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Cap project tools to netcoreapp2.2 and block creating new package #3057
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Max project tools TFM will be netcoreapp2.2
@@ -38,8 +38,8 @@ Copyright (c) .NET Foundation. All rights reserved. | |||
</PropertyGroup> | |||
|
|||
<PropertyGroup Condition="'$(DotnetCliToolTargetFramework)' == '' And '$(BundledNETCoreAppTargetFrameworkVersion)' != ''"> | |||
<!-- Set the TFM used to restore .NET CLI tools to match the version of .NET Core bundled in the CLI --> | |||
<DotnetCliToolTargetFramework>netcoreapp$(BundledNETCoreAppTargetFrameworkVersion)</DotnetCliToolTargetFramework> | |||
<!-- To move away from project tools. The highest available project tools TFM is netcoreapp2.2 --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The full spec is not available to public yet
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say this:
Maximum supported target framework for DotnetCliProjectTools is .NET Core 2.2
pending remove --fx-version when run, but that change should be in CLI repo |
@@ -38,8 +38,8 @@ Copyright (c) .NET Foundation. All rights reserved. | |||
</PropertyGroup> | |||
|
|||
<PropertyGroup Condition="'$(DotnetCliToolTargetFramework)' == '' And '$(BundledNETCoreAppTargetFrameworkVersion)' != ''"> | |||
<!-- Set the TFM used to restore .NET CLI tools to match the version of .NET Core bundled in the CLI --> | |||
<DotnetCliToolTargetFramework>netcoreapp$(BundledNETCoreAppTargetFrameworkVersion)</DotnetCliToolTargetFramework> | |||
<!-- To move away from project tools. The highest available project tools TFM is netcoreapp2.2 --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say this:
Maximum supported target framework for DotnetCliProjectTools is .NET Core 2.2
src/Tests/Microsoft.NET.Pack.Tests/GivenThatWeWantToPackAProjectTool.cs
Outdated
Show resolved
Hide resolved
src/Tests/Microsoft.NET.Pack.Tests/GivenThatWeWantToPackAProjectTool.cs
Outdated
Show resolved
Hide resolved
src/Tests/Microsoft.NET.Pack.Tests/GivenThatWeWantToPackAProjectTool.cs
Outdated
Show resolved
Hide resolved
...osoft.NET.Restore.Tests/GivenThatWeWantToRestoreAndGenerateDepsjsonDotNetCliToolReference.cs
Outdated
Show resolved
Hide resolved
} | ||
|
||
[Fact] | ||
public void It_can_restore_with_netcoreapp2_2() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dsplaisted I find the previous test restoring aspnet scaffolding is too slow, download too much, and may cause fullframework leg's time out. So I changed it to restore a sample project tool and only asset restore's TFM
….5 (#3057) - Microsoft.DotNet.Cli.Runtime - 5.0.100-alpha1.19503.5
2 work are separate commits