Update branding to 6.0.0 Alpha1 - #24983
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/fyi This PR needs more work to get the tests passing |
e7bd316 to
32776fa
Compare
| Files="@(_BuildOutput)" | ||
| FrameworkOnlyPackages="@(AspNetCoreAppReference)" | ||
| SharedFrameworkTargetFramework="net$(AspNetCoreMajorVersion).$(AspNetCoreMinorVersion)" /> | ||
| SharedFrameworkTargetFramework="net5.0" /> |
There was a problem hiding this comment.
Use of $(AspNetCoreMajorVersion) or $(AspNetCoreMajorMinorVersion) was only occasionally correct. Since the concepts aren't related, we shouldn't change this back in the future
b789b64 to
09a4145
Compare
|
Internal build https://dev.azure.com/dnceng/internal/_build/results?buildId=778919 should help confirm changes in site extensions build |
d463b74 to
8e3917f
Compare
|
🆙📅 though I doubt tests will work without further changes. I'm building locally to see if I can get more information about template failures in previous builds. Suspect we have additional places where TFMs get mixed up with package versions. Worst case, we might need a runtime update containing dotnet/runtime#40950. I triggered that (daily) subscription just in case. |
|
@pranavkm I seem to remember you looking at test failures like and that you resolved them. Any idea why I'm seeing them in the gRPC interop tests e.g. https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-aspnetcore-refs-pull-24983-merge-c76e36077044499e8d/InteropTests--net5.0/console.74b37675.log?sv=2019-02-02&se=2020-09-09T20%3A09%3A24Z&sr=c&sp=rl&sig=89ThpfLWPzA57TSNhBUDUXyo5Zl7VM%2FE5dV4aEzYBKI%3D❔ |
|
@HaoK I'm seeing gRPC test failures on other platforms that seem to indicate the newly-built 6.0.0-ci copy of Microsoft.AspNetCore.App.Runtime was installed to the wrong location. What needs to change❔ |
|
The versions haven't been updated yet? https://github.com/dotnet/aspnetcore/blob/master/eng/targets/Helix.targets#L120 I think we use MicrosoftNETCoreAppRuntimeVersion |
We should be able to rebrand independent of the dotnet/runtime repo. Helix.targets and the scripts used on the Helix agents should not use /fyi the same messed up install location for the new Microsoft.AspNetCore.App.Runtime bits is hurting the project template tests too e.g. https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-aspnetcore-refs-pull-24983-merge-56d6b0427e38425e94/ProjectTemplates.Tests--net5.0/console.2800c965.log?sv=2019-02-02&se=2020-09-09T20%3A09%3A23Z&sr=c&sp=rl&sig=fJ7Q1BIJ1qJNSQxW8J2SP801r31rmo3kHfbakOY0szw%3D On Windows, the project template downstream errors are usually "failed to run EF migrations" due to an inability to load the Microsoft.AspNetCore.Diagnostics.Abstractions.dll assembly that Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.dll needs. The gRPC downstream errors are thrown |
|
Right both GRPC and templates depend on the aspnet runtime, that currently use that version, i think if you just replace that with whatever the aspnet specific version is, things shoudl work |
8e3917f to
869eaaa
Compare
|
@HaoK please have a look @ the last commit |
Now the second-to-last commit |
|
New test internal build is https://dev.azure.com/dnceng/internal/_build/results?buildId=781173 Previous one didn't uncover any issues in the packages but I'd like to double-check |
|
Azure Pipelines successfully started running 2 pipeline(s). |
ddb8325 to
97c47c3
Compare
d5c5d23 to
b58af16
Compare
b58af16 to
7b42067
Compare
|
/fyi @mmitche this probably needs another iteration but is much closer than it was. |
7b42067 to
6fdf569
Compare
6fdf569 to
da9a43e
Compare
- without this, generated assemblies are unusable in aspnetcore after that brands to 6.0.0 - in other words, this is needed for dotnet/aspnetcore#24983 to test correctly
- hold the TFM back at `net5.0` - correct `TargetFrameworkVersion` in FrameworkList.xml; don't use `$(AspNetCoreMajorMinorVersion)` - move `$(DefaultNetCoreTargetFramework)` to eng/Versions.props - avoid repeating value in AfterSolutionBuild.targets and Directory.Build.props files - add new versions to `TemplatePackageInstaller` - update project template test scripts
- basically, remove test assumptions that branding == target TFM - `TestData` will need another update once 6.0.0.0 assembly versions arrive from dotnet/runtime
- allow sharedFx assemblies in Microsoft.AspNetCore.Components.WebAssembly.DevServer package - see #26448 about reducing this baggage later in 6.0
da9a43e to
d357dfa
Compare
- without this, generated assemblies are unusable in aspnetcore after that brands to 6.0.0 - in other words, this is needed for dotnet/aspnetcore#24983 to test correctly
|
PR is green. Only aspnetcore-quarantined-pr tests failed in last validation runs. Failures in https://dev.azure.com/dnceng/public/_build/results?buildId=848137 look very similar to those in https://dev.azure.com/dnceng/public/_build/results?buildId=848129 (the last rolling build of the master branch), including the Helix Linux and Windows timeouts. IOW there's no new failures in this PR compared to the existing master branch. |
* Upgrade to a 6.0 SDK - without this, generated assemblies are unusable in aspnetcore after that brands to 6.0.0 - in other words, this is needed for dotnet/aspnetcore#24983 to test correctly * Check for `IOException` instead of missing `NetworkException` - `NetworkException` unavailable in shared framework or a shipping package * Update .NET SDK version used in Helix tests - eliminate need to change the .NET SDK version in two files - `$(DotNetCliVersion)` must be set explicitly - Helix SDK does not pick up .NET SDK version from our global.json - fortunately, `$(NETCoreSdkVersion)` is available in helix.proj
| <FrameworkListRootAttributes Include="Name" Value="$(AspNetCoreAppFrameworkBrandName)" /> | ||
| <FrameworkListRootAttributes Include="TargetFrameworkIdentifier" Value="$(NETCoreAppFrameworkIdentifier)" /> | ||
| <FrameworkListRootAttributes Include="TargetFrameworkVersion" Value="$(AspNetCoreMajorMinorVersion)" /> | ||
| <FrameworkListRootAttributes Include="TargetFrameworkVersion" Value="$(DefaultNetCoreTargetFramework.Substring(3))" /> |
There was a problem hiding this comment.
This doesn't look resilient. Granted we probably won't change the format netX.Y to something else, I guess I'm okay with it.
| </PropertyGroup> | ||
|
|
||
| <ItemGroup> | ||
| <FrameworkReference Include="Microsoft.AspNetCore.App" /> |
There was a problem hiding this comment.
Why did this reference change? I'm not too sure about the changes in this file but as long as @pranavkm signs off it should be fine.
There was a problem hiding this comment.
Probably putting an error above that indicating that we expect "netN" so that we catch this location if something changes.
There was a problem hiding this comment.
The whole project changed because we have a mess of conflicts because this project attempted to use AspNetCore bits from the SDK as well as reference projects elsewhere in the repo. @pranavkm signed off on doing this in Teams.
#26448 is about trimming the package correctly at some point in the 6.0 train but only if this project doesn't move elsewhere.
net5.0@(SuppressBaselineReference)itemsConditionattributes to make remainder easy to find