Skip to content
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

[master] Update dependencies from dotnet/runtime dotnet/efcore #26788

Merged

Conversation

dotnet-maestro[bot]
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Oct 11, 2020

This pull request updates the following dependencies

From https://github.com/dotnet/efcore

  • Subscription: ccafa991-4408-48df-d45d-08d76e1d3434
  • Build: 20201026.2
  • Date Produced: 10/27/2020 12:09 AM
  • Commit: 3dc24353881e40f66718ad32472f6628955d80a9
  • Branch: refs/heads/main

From https://github.com/dotnet/runtime

  • Subscription: 68568747-40a2-4823-fae6-08d7f76e4602
  • Build: 20201025.3
  • Date Produced: 10/26/2020 5:56 AM
  • Commit: 693c1f05188330e270b01a6bce8ad22ab7b33f23
  • Branch: refs/heads/master

@dotnet-maestro dotnet-maestro bot requested a review from dougbu as a code owner October 11, 2020 10:20
@ghost ghost added area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework Type: Dependency Update 🔼 labels Oct 11, 2020
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Auto-approving dependency update.

@dotnet-maestro dotnet-maestro bot changed the title [master] Update dependencies from dotnet/efcore [master] Update dependencies from dotnet/efcore dotnet/runtime Oct 12, 2020
@halter73
Copy link
Member

halter73 commented Oct 12, 2020

@dotnet/aspnet-build It looks like we're going to update the default TFM to merge this dependency update.

RepoTasks.csproj(0,0): error NU1202: (NETCORE_ENGINEERING_TELEMETRY=Restore) Package Microsoft.Extensions.Internal.Transport 6.0.0-alpha.1.20512.3 is not compatible with net5.0 (.NETCoreApp,Version=v5.0). Package Microsoft.Extensions.Internal.Transport 6.0.0-alpha.1.20512.3 supports: net6.0 (.NETCoreApp,Version=v6.0)

@halter73
Copy link
Member

See #22737

@dotnet-maestro dotnet-maestro bot changed the title [master] Update dependencies from dotnet/efcore dotnet/runtime [master] Update dependencies from dotnet/runtime dotnet/efcore Oct 13, 2020
@TanayParikh TanayParikh added the blocked The work on this issue is blocked due to some dependency label Oct 13, 2020
@TanayParikh
Copy link
Contributor

Marking blocked on: #22737

@dougbu
Copy link
Member

dougbu commented Oct 13, 2020

Marking blocked on: #22737

@TanayParikh please work to get this PR going rather than handling #22737 separately.

@TanayParikh
Copy link
Contributor

Marking blocked on: #22737

@TanayParikh please work to get this PR going rather than handling #22737 separately.

Sounds good. Working on tackling #26767 right now. Any tips on resolving this? Just do a rollback on requisite packages?

@dotnet-maestro dotnet-maestro bot changed the title [master] Update dependencies from dotnet/runtime dotnet/efcore [master] Update dependencies from dotnet/efcore dotnet/runtime Oct 14, 2020
@dotnet-maestro dotnet-maestro bot changed the title [master] Update dependencies from dotnet/efcore dotnet/runtime [master] Update dependencies from dotnet/runtime dotnet/efcore Oct 14, 2020
@TanayParikh
Copy link
Contributor

.dotnet/sdk/6.0.100-alpha.1.20472.11/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.TargetFrameworkInference.targets(146,5): error NETSDK1045: (NETCORE_ENGINEERING_TELEMETRY=Restore) The current .NET SDK does not support targeting .NET Core 6.0.  Either target .NET Core 5.0 or lower, or use a version of the .NET SDK that supports .NET Core 6.0.

6.0.100-alpha.1.20472.11 should support .NET Core 6.0. Seeing if I missed something.

@dougbu
Copy link
Member

dougbu commented Oct 15, 2020

6.0.100-alpha.1.20472.11 should support .NET Core 6.0. Seeing if I missed something.

@dsplaisted @wli3 I don't see anything about .net6.0 in this version of the SDK. Is there a newer version including such support ❔

@TanayParikh if not, there may be a bug in our workaround at https://github.com/dotnet/aspnetcore/blob/master/eng/Workarounds.targets#L46-L56

Might also be as simple as changing $(NETCoreAppMaximumVersion) if you haven't already done that. See https://github.com/dotnet/aspnetcore/blob/master/eng/Workarounds.targets#L5

@TanayParikh
Copy link
Contributor

Might also be as simple as changing $(NETCoreAppMaximumVersion) if you haven't already done that. See https://github.com/dotnet/aspnetcore/blob/master/eng/Workarounds.targets#L5

Thanks, hadn't done that, updated. Build progressing further now.

@@ -3,7 +3,7 @@
<metadata>
$CommonMetadataElements$
<dependencies>
<group targetFramework=".net5.0">
<group targetFramework=".net6.0">
Copy link
Member

Choose a reason for hiding this comment

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

It's pretty easy to extend the properties passed into *.nuspec files. Should do that to avoid having to change this again (relatively soon).

@@ -281,7 +281,7 @@ public async Task Build_Hosted_Works()
Assert.FileDoesNotExist(result, buildOutputDirectory, "wwwroot", "_framework", "_bin", "blazorwasm.dll");

var staticWebAssets = Assert.FileExists(result, buildOutputDirectory, "blazorhosted.StaticWebAssets.xml");
Assert.FileContains(result, staticWebAssets, Path.Combine("net5.0", "wwwroot"));
Assert.FileContains(result, staticWebAssets, Path.Combine("net6.0", "wwwroot"));
Copy link
Member

Choose a reason for hiding this comment

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

My suggestion for test code is to compile https://github.com/dotnet/aspnetcore/blob/master/src/Framework/test/TestDataAttribute.cs into every test project and unconditionally include the bit at https://github.com/dotnet/aspnetcore/blob/master/src/Framework/test/Microsoft.AspNetCore.App.UnitTests.csproj#L19-L22. The code to read that attribute value is pretty simple but could also be centralized. Again, this will make it much easier to change next time around.

@captainsafia captainsafia self-assigned this Oct 15, 2020
@dotnet-maestro dotnet-maestro bot changed the title [master] Update dependencies from dotnet/runtime dotnet/efcore [master] Update dependencies from dotnet/efcore dotnet/runtime Oct 16, 2020
@dotnet-maestro dotnet-maestro bot changed the title [master] Update dependencies from dotnet/efcore dotnet/runtime [master] Update dependencies from dotnet/runtime dotnet/efcore Oct 16, 2020
@dougbu
Copy link
Member

dougbu commented Oct 25, 2020

Down to a couple of problems that may be specific to this update, only the first truly blocking:

  1. 6 template tests failing on Ubuntu Helix agents with
    [87.848s] [Templates.Test.GrpcTemplateTest] [Information] [ERROR] Unhandled exception. System.BadImageFormatException: An attempt was made to load a program with an incorrect format.
    [87.848s] [Templates.Test.GrpcTemplateTest] [Information] [ERROR]  (0x8007000B)
    
    Will look at a dump to determine the image that's considered invalid. Wondering if we're hitting issues using a Windows build of ASP.NET Core assemblies on non-Windows machines. All other tests are doing the same thing. Would mean the offending assembly is rarely used.
    See https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-aspnetcore-refs-pull-26788-merge-6cf5d5f3e7df4c5b81/ProjectTemplates.Tests--net6.0/console.8348081f.log?sv=2019-07-07 and e.g. https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-aspnetcore-refs-pull-26788-merge-6cf5d5f3e7df4c5b81/ProjectTemplates.Tests--net6.0/Templates.Test.GrpcTemplateTest_GrpcTemplate.log?sv=2019-07-07
  2. Numerous Microsoft.AspNetCore.Components.E2ETests tests failing in the non-Helix Windows quarantined run. Exception in that case is
    Microsoft.AspNetCore.Components.E2ETest.ServerExecutionTests.RemoteRendererBufferLimitTest.DispatchedEventsWillKeepBeingProcessed_ButUpdatedWillBeDelayedUntilARenderIsAcknowledged [FAIL]
      System.InvalidOperationException : Invalid state previous task not completed
      Stack Trace:
        /_/src/Components/Ignitor/src/BlazorClient.cs(100,0): at Ignitor.BlazorClient.PrepareForNextBatch(Nullable`1 timeout)
        /_/src/Components/Ignitor/src/BlazorClient.cs(240,0): at Ignitor.BlazorClient.WaitForRenderBatch(Nullable`1 timeout)
        /_/src/Components/Ignitor/src/BlazorClient.cs(185,0): at Ignitor.BlazorClient.ExpectRenderBatch(Func`1 action, Nullable`1 timeout)
        /_/src/Components/test/E2ETest/ServerExecutionTests/RemoteRendererBufferLimitTest.cs(33,0): at Microsoft.AspNetCore.Components.E2ETest.ServerExecutionTests.RemoteRendererBufferLimitTest.DispatchedEventsWillKeepBeingProcessed_ButUpdatedWillBeDelayedUntilARenderIsAcknowledged()
        --- End of stack trace from previous location ---
    
    I don't see anything obvious in the output but I'm not familiar with these tests. @javiercn @pranavkm @captainsafia, is this fairly normal for those quarantined tests ❔
    See https://dev.azure.com/dnceng/_apis/resources/Containers/5404509/Windows_Quarantined_Test_Logs?itemPath=Windows_Quarantined_Test_Logs%2FRelease%2FQuarantined%2FMicrosoft.AspNetCore.Components.E2ETests_net6.0_x64.log

@dougbu
Copy link
Member

dougbu commented Oct 26, 2020

Still unable to get clear information from the dumps.

Don't know if this is normal but I find the extra AspNet.hkr5gkn0cpk module odd:

> modules
000055A2003AB000 00222000 /datadisks/disk1/work/BC7809D9/w/A34B0924/e/Templates/BaseFolder/AspNet.hkr5gkn0cpk/bin/Debug/net6.0/AspNet.hkr5gkn0cpk
00007F8B2D550000 00462000 /usr/lib/x86_64-linux-gnu/libicui18n.so.55.1
00007F8B2D9B2000 01AB7000 /usr/lib/x86_64-linux-gnu/libicudata.so.55.1
00007F8B2F469000 00390000 /usr/lib/x86_64-linux-gnu/libicuuc.so.55.1
00007F8D84310000 00921E00 /datadisks/disk1/work/BC7809D9/w/A34B0924/e/.dotnet4760/shared/Microsoft.NETCore.App/6.0.0-alpha.1.20522.9/System.Private.CoreLib.dll
00007F8D84D90000 00038600 /datadisks/disk1/work/BC7809D9/w/A34B0924/e/.dotnet4760/shared/Microsoft.NETCore.App/6.0.0-alpha.1.20522.9/System.Runtime.dll
00007F8DF600D000 0000A000 /datadisks/disk1/work/BC7809D9/w/A34B0924/e/Templates/BaseFolder/AspNet.hkr5gkn0cpk/bin/Debug/net6.0/AspNet.hkr5gkn0cpk.dll

@dotnet-maestro dotnet-maestro bot changed the title [master] Update dependencies from dotnet/efcore dotnet/runtime [master] Update dependencies from dotnet/runtime dotnet/efcore Oct 26, 2020
@dotnet-maestro dotnet-maestro bot changed the title [master] Update dependencies from dotnet/runtime dotnet/efcore [master] Update dependencies from dotnet/efcore dotnet/runtime Oct 26, 2020
dotnet-maestro bot and others added 3 commits October 26, 2020 16:54
…026.1

Microsoft.EntityFrameworkCore.Tools , dotnet-ef , Microsoft.EntityFrameworkCore , Microsoft.EntityFrameworkCore.Design , Microsoft.EntityFrameworkCore.InMemory , Microsoft.EntityFrameworkCore.Relational , Microsoft.EntityFrameworkCore.Sqlite , Microsoft.EntityFrameworkCore.SqlServer
 From Version 6.0.0-alpha.1.20509.5 -> To Version 6.0.0-alpha.1.20526.1
…1025.3

System.ComponentModel.Annotations , System.Diagnostics.DiagnosticSource , System.Diagnostics.EventLog , System.DirectoryServices.Protocols , Microsoft.Extensions.Logging.Debug , Microsoft.Extensions.Logging.EventLog , Microsoft.Extensions.Logging.EventSource , Microsoft.Extensions.Logging.TraceSource , Microsoft.Extensions.Options , Microsoft.Extensions.Options.ConfigurationExtensions , Microsoft.Extensions.Options.DataAnnotations , Microsoft.Extensions.Primitives , Microsoft.Extensions.Logging.Console , Microsoft.Extensions.Logging.Configuration , Microsoft.Extensions.Logging.Abstractions , Microsoft.Extensions.Logging , Microsoft.Extensions.Caching.Abstractions , Microsoft.Extensions.Caching.Memory , Microsoft.Extensions.Configuration , Microsoft.Extensions.Configuration.Abstractions , Microsoft.Extensions.Configuration.Binder , Microsoft.Extensions.Configuration.CommandLine , Microsoft.Extensions.Configuration.EnvironmentVariables , Microsoft.Extensions.Configuration.FileExtensions , Microsoft.Extensions.Configuration.Ini , Microsoft.Extensions.Configuration.Json , Microsoft.Extensions.Configuration.UserSecrets , Microsoft.Extensions.Configuration.Xml , Microsoft.Extensions.DependencyInjection , Microsoft.Extensions.DependencyInjection.Abstractions , Microsoft.Extensions.DependencyModel , Microsoft.Extensions.FileProviders.Abstractions , Microsoft.Extensions.FileProviders.Composite , Microsoft.Extensions.FileProviders.Physical , Microsoft.Extensions.FileSystemGlobbing , Microsoft.Extensions.HostFactoryResolver.Sources , Microsoft.Extensions.Hosting , Microsoft.Extensions.Hosting.Abstractions , Microsoft.Extensions.Http , Microsoft.Extensions.Internal.Transport , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport , Microsoft.NETCore.Platforms , Microsoft.Win32.Registry , Microsoft.Win32.SystemEvents , Microsoft.NETCore.App.Internal , Microsoft.NETCore.App.Ref , System.Drawing.Common , System.Windows.Extensions , System.Threading.Channels , System.Text.Encodings.Web , System.IO.Pipelines , System.Net.Http.Json , System.Net.Http.WinHttpHandler , System.Net.WebSockets.WebSocketProtocol , System.Reflection.Metadata , System.Text.Json , System.Resources.Extensions , System.Runtime.CompilerServices.Unsafe , System.Security.AccessControl , System.Security.Cryptography.Cng , System.Security.Cryptography.Pkcs , System.Security.Cryptography.Xml , System.Security.Permissions , System.Security.Principal.Windows , System.ServiceProcess.ServiceController
 From Version 6.0.0-alpha.1.20507.4 -> To Version 6.0.0-alpha.1.20525.3
- make `$(CrossgenOutput)` property override-able
- use override in CI jobs that submit to other platforms
  - for now, leave the ARM64 Helix jobs alone (build on Ubuntu, run in Debian)

nits:
- correct condition for `$(GenerateCrossgenProfilingSymbols)`
- set `$(ASPNETCORE_TEST_LOG_DIR)` in every step of the Helix build jobs
@dougbu dougbu force-pushed the darc-master-76e24f4d-c90c-42ac-a1e5-411ae61ca37b branch from f0ca22e to 84abf5e Compare October 26, 2020 23:54
Copy link
Member

@dougbu dougbu left a comment

Choose a reason for hiding this comment

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

🤞 🤞

@@ -37,5 +37,10 @@ $env:BUILD_SOURCEBRANCH="local"
$env:BUILD_REPOSITORY_NAME="aspnetcore"
$env:SYSTEM_TEAMPROJECT="aspnetcore"

Write-Host -ForegroundColor Yellow "If running tests that need the shared Fx, run './build -pack -all' before this."
Write-Host -ForegroundColor Yellow "And if packing for a different platform, add '/p:CrossgenOutput=false'."
Copy link
Member

Choose a reason for hiding this comment

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

/fyi @HaoK @dotnet/aspnet-build

<MSBuild Projects="$(RepoRoot)eng\tools\GenerateFiles\GenerateFiles.csproj"
RemoveProperties="BaseIntermediateOutputPath;ExcludeRestorePackageImports"
Targets="GenerateDirectoryBuildFiles" />
</Target>
Copy link
Member

Choose a reason for hiding this comment

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

@dotnet/aspnet-build if you have a chance, please dummy-check my many manual changes in this PR. Big example here and in the new eng/tools/GenerateFiles/ project.


<!-- Produce crossgen profiling symbols (.ni.pdb or .map files). -->
<GenerateCrossgenProfilingSymbols>true</GenerateCrossgenProfilingSymbols>
<GenerateCrossgenProfilingSymbols Condition=" '$(CrossgenOutput)' == 'false' OR '$(TargetOsName)' == 'osx'">false</GenerateCrossgenProfilingSymbols>
<GenerateCrossgenProfilingSymbols Condition=" '$(CrossgenOutput)' != 'true' OR '$(TargetOsName)' == 'osx' ">false</GenerateCrossgenProfilingSymbols>
Copy link
Member

Choose a reason for hiding this comment

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

Mentioned this nit in a commit description. Nothing exists that I'm aware of to set $(CrossgenOutput) to false outside the Helix jobs. Checking for not-true makes more sense given how that property is set just above.

@dougbu
Copy link
Member

dougbu commented Oct 27, 2020

(BTW I was looking for a crossed toes emoji too but couldn't find one 😺)

…026.2

Microsoft.EntityFrameworkCore.Tools , dotnet-ef , Microsoft.EntityFrameworkCore , Microsoft.EntityFrameworkCore.Design , Microsoft.EntityFrameworkCore.InMemory , Microsoft.EntityFrameworkCore.Relational , Microsoft.EntityFrameworkCore.Sqlite , Microsoft.EntityFrameworkCore.SqlServer
 From Version 6.0.0-alpha.1.20509.5 -> To Version 6.0.0-alpha.1.20526.2
@dotnet-maestro dotnet-maestro bot changed the title [master] Update dependencies from dotnet/efcore dotnet/runtime [master] Update dependencies from dotnet/runtime dotnet/efcore Oct 27, 2020
@dotnet-maestro dotnet-maestro bot merged commit 219ecd6 into master Oct 27, 2020
@dotnet-maestro dotnet-maestro bot deleted the darc-master-76e24f4d-c90c-42ac-a1e5-411ae61ca37b branch October 27, 2020 07:04
@Pilchie
Copy link
Member

Pilchie commented Oct 27, 2020

Hurray!

dougbu pushed a commit that referenced this pull request Oct 31, 2020
… master

- [master] Update dependencies from dotnet/runtime dotnet/efcore (#26788)
    - 219ecd6
- when project template tests run test assets, need latest shared Fx bits
- hit `BadImageFormatException`s otherwise
    - test projects build against uploaded packages
    - those packages reference the 5.0.1 shared framework
    - the ASP.NET parts of the 5.0.1 shared Fx are `crossgen`ed to target Windows

- Use runtime and ref/ assemblies matching repo in Helix testing
    - add Directory.Build.*.in files based on project template test infrastructure
    - use files as import boundary where the project doesn't create its own Directory.Build.* files
    - ensure `dotnet-watch` tests also use the latest runtime and ref/ assemblies

- Extend Helix Directory.Build.* workarounds
    - generate Directory.Build.* files when restoring any projects
    - include generated files in Helix runs needing the latest runtime
    - copy generated files when testing `dotnet-watch` locally
    - include generated content in Microsoft.NET.Sdk.BlazorWebAssembly.IntegrationTests test assets
        - remove duplicate settings from existing Directory.Build.* files
    - ensure shared framework and targeting packs are laid out under .dotnet/ before test assets restore

- Disable `crossgen` when building for Helix runs
    - make `$(CrossgenOutput)` property override-able
    - use override in CI jobs that submit to other platforms
        - for now, leave the ARM64 Helix jobs alone (build on Ubuntu, run in Debian)
dougbu pushed a commit that referenced this pull request Nov 10, 2020
… master

- [master] Update dependencies from dotnet/runtime dotnet/efcore (#26788)
    - 219ecd6
- when project template tests run test assets, need latest shared Fx bits
- hit `BadImageFormatException`s otherwise
    - test projects build against uploaded packages
    - those packages reference the 5.0.1 shared framework
    - the ASP.NET parts of the 5.0.1 shared Fx are `crossgen`ed to target Windows

- Use runtime and ref/ assemblies matching repo in Helix testing
    - add Directory.Build.*.in files based on project template test infrastructure
    - use files as import boundary where the project doesn't create its own Directory.Build.* files
    - ensure `dotnet-watch` tests also use the latest runtime and ref/ assemblies

- Extend Helix Directory.Build.* workarounds
    - generate Directory.Build.* files when restoring any projects
    - include generated files in Helix runs needing the latest runtime
    - copy generated files when testing `dotnet-watch` locally
    - include generated content in Microsoft.NET.Sdk.BlazorWebAssembly.IntegrationTests test assets
        - remove duplicate settings from existing Directory.Build.* files
    - ensure shared framework and targeting packs are laid out under .dotnet/ before test assets restore

- Disable `crossgen` when building for Helix runs
    - make `$(CrossgenOutput)` property override-able
    - use override in CI jobs that submit to other platforms
        - for now, leave the ARM64 Helix jobs alone (build on Ubuntu, run in Debian)
dougbu added a commit that referenced this pull request Nov 10, 2020
* Move to 5.0.1 versions

* Move to GA .NET SDK
- required for some tests to pass

* Remove feeds that won't be needed after 5.0.0 is GA

* Cherry-pick `$(CrossgenOutput)` and Directory.Build.*.in changes from master
- [master] Update dependencies from dotnet/runtime dotnet/efcore (#26788)
    - 219ecd6
- when project template tests run test assets, need latest shared Fx bits
- hit `BadImageFormatException`s otherwise
    - test projects build against uploaded packages
    - those packages reference the 5.0.1 shared framework
    - the ASP.NET parts of the 5.0.1 shared Fx are `crossgen`ed to target Windows

- Use runtime and ref/ assemblies matching repo in Helix testing
    - add Directory.Build.*.in files based on project template test infrastructure
    - use files as import boundary where the project doesn't create its own Directory.Build.* files
    - ensure `dotnet-watch` tests also use the latest runtime and ref/ assemblies

- Extend Helix Directory.Build.* workarounds
    - generate Directory.Build.* files when restoring any projects
    - include generated files in Helix runs needing the latest runtime
    - copy generated files when testing `dotnet-watch` locally
    - include generated content in Microsoft.NET.Sdk.BlazorWebAssembly.IntegrationTests test assets
        - remove duplicate settings from existing Directory.Build.* files
    - ensure shared framework and targeting packs are laid out under .dotnet/ before test assets restore

- Disable `crossgen` when building for Helix runs
    - make `$(CrossgenOutput)` property override-able
    - use override in CI jobs that submit to other platforms
        - for now, leave the ARM64 Helix jobs alone (build on Ubuntu, run in Debian)

* Correct an `$(IsTestAssetProject)` setting
- affected projects are all test assets or provide test support
- without this, a number of the projects are incorrectly marked as shipping

* Baseline released 5.0.0 packages
- this is a complete rewrite of eng/Baseline.xml
  - based on the 5.0.0 MergedManifest.xml file

* Add 5.0.0 PackageOverrides.txt and PlatformManifest.txt files
- need consistent versions when servicing targeting packs

Co-authored-by: dotnet-maestro[bot] <42748379+dotnet-maestro[bot]@users.noreply.github.com>
dougbu pushed a commit to dougbu/razor-compiler that referenced this pull request Nov 17, 2021
…t/aspnetcore#26788)

[master] Update dependencies from dotnet/runtime dotnet/efcore


 - Update TFM net5.0 -> net6.0

 - Introduce $(TargetTFM)

 - TargetTfm -> DefaultNetCoreTargetFramework

 - Updated: NETCoreAppMaximumVersion

 - Apply suggestions from code review

Co-authored-by: Doug Bunting <[email protected]>

 - Fix version numbers used in Blazor WASM SDK

 - Address feedback from peer review

 - Fix check for platform version

 - Fix build config for dotnet-watch project

 - Update TFM net5.0 -> net6.0

 - Introduce $(TargetTFM)

 - TargetTfm -> DefaultNetCoreTargetFramework

 - Apply suggestions from code review

Co-authored-by: Doug Bunting <[email protected]>

 - Fix version numbers used in Blazor WASM SDK

 - Address feedback from peer review

 - Remove workaround in dotnet-watch tests

 - Testrunner to 5.0 and adding workarounds

 - Try props.in

 - net50

 - Fixup KnownFrameworkReference for integration tests

 - Resolve a few comments
- don't use repo-specific properties in shipping file
- pass `$(DefaultNetCoreTargetFramework)` into template files used in tests

 - Update src/Components/WebAssembly/Sdk/src/targets/Microsoft.NET.Sdk.BlazorWebAssembly.Current.targets

 - Update KnownFrameworkReference for template tests

 - Use DefaultNetcoreTFM

 - Undo change to props.in

 - Update src/ProjectTemplates/test/ProjectTemplates.Tests.csproj

 - Update GenerateTestProps.targets

- this is where `$(KnownAppHostPackOrFrameworkReferenceTfm)` is needed

 - Update src/ProjectTemplates/test/ProjectTemplates.Tests.csproj

- additional template input not needed here

 - Other file changes

 - Rename the one net5.0 directory in the repo

 - Fixup rebase remnants

 - Use runtime and ref/ assemblies matching repo in Helix testing
- add Directory.Build.*.in files based on project template test infrastructure
- use files as import boundary where the project doesn't create its own Directory.Build.* files
- ensure `dotnet-watch` tests also use the latest runtime and ref/ assemblies

 - Switch Directory.Build.*.in files in Helix content
- ensure item manipulation is done after base items exist

nit: Fix *.in exclusion

 - Update TFM workaround to reference 5.0 instead of 3.1 (dotnet/aspnetcore#26991)

 - Make some Directory.Build.*.in settings override-able
- that is, move some properties to Directory.Build.props.in

also
- fix `Condition`s that resulted in empty Directory.Build.targets
- separate Directory.Build.empty.in
- ensure RunTests project is _not_ affected by root Directory.Build.* files

 - Update SDK

 - Set `$(DefaultNetCoreTargetFramework)` in Helix root Directory.Build.props
= `dotnet-watch` tests otherwise fail with "The TargetFramework value '' was not recognized"

 - Extend Helix Directory.Build.* workarounds
- generate Directory.Build.* files when restoring any projects
- include generated files in Helix runs needing the latest runtime
- copy generated files when testing `dotnet-watch` locally
- include generated content in Microsoft.NET.Sdk.BlazorWebAssembly.IntegrationTests test assets
  - remove duplicate settings from existing Directory.Build.* files
- ensure shared framework and targeting packs are laid out under .dotnet/ before test assets restore

 - !fixup! Remove extra end tags

 - !fixup! Don't build GenerateFiles.csproj in desktop `msbuild`

 - !fixup! Arcade uses different test targets

 - Disable `crossgen` when building for Helix runs
- make `$(CrossgenOutput)` property override-able
- use override in CI jobs that submit to other platforms
  - for now, leave the ARM64 Helix jobs alone (build on Ubuntu, run in Debian)

nits:
- correct condition for `$(GenerateCrossgenProfilingSymbols)`
- set `$(ASPNETCORE_TEST_LOG_DIR)` in every step of the Helix build jobs

 - Ensure ReadRequest type can be loaded on server. Fixes dotnet/aspnetcore#26882 (dotnet/aspnetcore#26931)

 - Enable debugging when using embedded PDBs (dotnet/aspnetcore#27107)

* Fix debug using embedded PDBs.

* Check for either debugBuild or referenced PDBs

Co-authored-by: Thays <[email protected]>

 - Ensure Blazor JS files are up-to-date

 - Merge branch 'master' into darc-master-76e24f4d-c90c-42ac-a1e5-411ae61ca37b

Commit migrated from dotnet/aspnetcore@219ecd688012
dougbu added a commit to dougbu/razor-compiler that referenced this pull request Nov 17, 2021
* Move to 5.0.1 versions

* Move to GA .NET SDK
- required for some tests to pass

* Remove feeds that won't be needed after 5.0.0 is GA

* Cherry-pick `$(CrossgenOutput)` and Directory.Build.*.in changes from master
- [master] Update dependencies from dotnet/runtime dotnet/efcore (dotnet/aspnetcore#26788)
    - 219ecd688012
- when project template tests run test assets, need latest shared Fx bits
- hit `BadImageFormatException`s otherwise
    - test projects build against uploaded packages
    - those packages reference the 5.0.1 shared framework
    - the ASP.NET parts of the 5.0.1 shared Fx are `crossgen`ed to target Windows

- Use runtime and ref/ assemblies matching repo in Helix testing
    - add Directory.Build.*.in files based on project template test infrastructure
    - use files as import boundary where the project doesn't create its own Directory.Build.* files
    - ensure `dotnet-watch` tests also use the latest runtime and ref/ assemblies

- Extend Helix Directory.Build.* workarounds
    - generate Directory.Build.* files when restoring any projects
    - include generated files in Helix runs needing the latest runtime
    - copy generated files when testing `dotnet-watch` locally
    - include generated content in Microsoft.NET.Sdk.BlazorWebAssembly.IntegrationTests test assets
        - remove duplicate settings from existing Directory.Build.* files
    - ensure shared framework and targeting packs are laid out under .dotnet/ before test assets restore

- Disable `crossgen` when building for Helix runs
    - make `$(CrossgenOutput)` property override-able
    - use override in CI jobs that submit to other platforms
        - for now, leave the ARM64 Helix jobs alone (build on Ubuntu, run in Debian)

* Correct an `$(IsTestAssetProject)` setting
- affected projects are all test assets or provide test support
- without this, a number of the projects are incorrectly marked as shipping

* Baseline released 5.0.0 packages
- this is a complete rewrite of eng/Baseline.xml
  - based on the 5.0.0 MergedManifest.xml file

* Add 5.0.0 PackageOverrides.txt and PlatformManifest.txt files
- need consistent versions when servicing targeting packs

Co-authored-by: dotnet-maestro[bot] <42748379+dotnet-maestro[bot]@users.noreply.github.com>

Commit migrated from dotnet/aspnetcore@352ad1a9804a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework Type: Dependency Update 🔼
Projects
None yet
Development

Successfully merging this pull request may close these issues.