-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Add net461 TFM to netstandard2.0 projects #25094
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
|
current issue:
ClientSample always targeted |
dougbu
left a comment
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.
In addition, suggest adding $(DefaultNetFxTargetFramework) to more of the integration and functional test projects that exercise the updated projects.
| <IsShippingPackage>false</IsShippingPackage> | ||
|
|
||
| <TargetFramework>netstandard2.0</TargetFramework> | ||
| <TargetFrameworks>$(DefaultNetFxTargetFramework);netstandard2.0</TargetFrameworks> |
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.
Not sure whether adding a .NET Framework assembly for analyzers is useful. @pranavkm❔
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.
Yeah, I don't think this should be necessary. The ns2.0 version works in VS and CLI, so unless something's broken there, I wouldn't change these.
| <PropertyGroup> | ||
| <Description>ASP.NET Core design time hosting infrastructure for the Razor view engine.</Description> | ||
| <TargetFramework>netstandard2.0</TargetFramework> | ||
| <TargetFrameworks>$(DefaultNetFxTargetFramework);netstandard2.0</TargetFrameworks> |
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.
Changes w/in the Razor SDK probably aren't useful. @NTaylorMullen❔
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.
Yup. These extensions are packaged in the SDK. Unless we are shipping the netfx versions for some reason, I'd avoid this change
| <PackageId>$(MSBuildProjectName)</PackageId> | ||
| <PackageTags>Build Tasks;MSBuild;Swagger;OpenAPI;code generation;Web API client;service reference</PackageTags> | ||
| <TargetFrameworks>netstandard2.0</TargetFrameworks> | ||
| <TargetFrameworks>$(DefaultNetFxTargetFramework);netstandard2.0</TargetFrameworks> |
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.
Revert changes in this file. The project creates an msbuild task that's always loaded from the netstandard2.0 assembly.
pranavkm
left a comment
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.
What's the benefit of this change?
| <IsShippingPackage>false</IsShippingPackage> | ||
|
|
||
| <TargetFramework>netstandard2.0</TargetFramework> | ||
| <TargetFrameworks>$(DefaultNetFxTargetFramework);netstandard2.0</TargetFrameworks> |
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.
Yeah, I don't think this should be necessary. The ns2.0 version works in VS and CLI, so unless something's broken there, I wouldn't change these.
| <PropertyGroup> | ||
| <Description>Helpers for writing tests for Roslyn analyzers.</Description> | ||
| <TargetFramework>netstandard2.0</TargetFramework> | ||
| <TargetFrameworks>$(DefaultNetFxTargetFramework);netstandard2.0</TargetFrameworks> |
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.
Same thing. This is a test only project, so unless something requires it, I wouldn't cross-compile it.
|
|
||
| <PropertyGroup> | ||
| <TargetFramework>netstandard2.0</TargetFramework> | ||
| <TargetFrameworks>$(DefaultNetFxTargetFramework);netstandard2.0</TargetFrameworks> |
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 leave testassets be (unless something requires it to be cross-compiled)
| <PropertyGroup> | ||
| <Description>ASP.NET Core design time hosting infrastructure for the Razor view engine.</Description> | ||
| <TargetFramework>netstandard2.0</TargetFramework> | ||
| <TargetFrameworks>$(DefaultNetFxTargetFramework);netstandard2.0</TargetFrameworks> |
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.
Yup. These extensions are packaged in the SDK. Unless we are shipping the netfx versions for some reason, I'd avoid this change
| <DefineConstants Condition="'$(GenerateBaselines)'=='true'">$(DefineConstants);GENERATE_BASELINES</DefineConstants> | ||
| <DefineConstants>$(DefineConstants);__RemoveThisBitTo__GENERATE_BASELINES</DefineConstants> | ||
| <TargetFrameworks>netstandard2.0;net461</TargetFrameworks> | ||
| <TargetFrameworks>$(DefaultNetFxTargetFramework);netstandard2.0;net461</TargetFrameworks> |
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.
Can you remove the net461 from this?
|
|
||
| <PropertyGroup> | ||
| <TargetFrameworks>netstandard2.0;net461</TargetFrameworks> | ||
| <TargetFrameworks>$(DefaultNetFxTargetFramework);netstandard2.0;net461</TargetFrameworks> |
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.
net461 appears twice here
We have a requirement (expressed in #22853) to better-support customers using .NET Framework i.e. to avoid relying on |
|
Source build failures:
|
|
@dotnet/aspnet-build I believe this is now ready for review |
| <SystemCommandlineExperimentalPackageVersion>0.3.0-alpha.19317.1</SystemCommandlineExperimentalPackageVersion> | ||
| <SystemComponentModelPackageVersion>4.3.0</SystemComponentModelPackageVersion> | ||
| <SystemNetHttpPackageVersion>4.3.2</SystemNetHttpPackageVersion> | ||
| <SystemNetHttpPackageVersion>4.3.4</SystemNetHttpPackageVersion> |
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 bumped this up to the latest
|
From the issue:
@dougbu |
dougbu
left a comment
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.
Small cleanup needed but otherwise looks good
src/Razor/Microsoft.AspNetCore.Razor.Language/src/Microsoft.AspNetCore.Razor.Language.csproj
Outdated
Show resolved
Hide resolved
...rs/Manifest.MSBuildTask/src/Microsoft.Extensions.FileProviders.Embedded.Manifest.Task.csproj
Outdated
Show resolved
Hide resolved
|
Test failures are all the Chrome thing - @dougbu @BrennanConroy @captainsafia do we have an issue tracking that yet? |
|
No issue yet. Probably going to have to port the change to all branches affected. (maybe 2.1+) |
src/Configuration.KeyPerFile/test/Microsoft.Extensions.Configuration.KeyPerFile.Tests.csproj
Outdated
Show resolved
Hide resolved
|
Selenium failures 😢 will rebase |
f84a60d to
3c547e2
Compare
/fyi @wtgodbe doing the |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
Approved for RC1 - thanks @wtgodbe ! |
Resolves #22853
Adds net461 to all netstandard2.0 projects, except analyzers, tests, test assets, and Razor SDK projects