* Remove LinkerWorkaround.xml
The workaround file is no longer needed, now that the underlying bugs are fixed in the dotnet/runtime libraries.
Fix#23262
* Also remove LinkerWorkaround from Components/WebAssembly
- use SignalR.Npm.FunctionalTests.npmproj to get non-stable version
- not Microsoft.AspNetCore.DeveloperCertificates.XPlat.csproj (avoid C# and F# projects)
- add `_GetPackageVersionInfo` target to all `*.npmproj` projects
- make `_GetPackageVersionInfo` target work when `yarn` is not installed
- switch codesign-xplat.yml to use `dotnet msbuild`
- above change also fixes Code-sign jobs but they're slightly faster using `dotnet msbuild`
* Add guard check for cleared closest DOM element
* Update src/Components/Web.JS/src/Rendering/BrowserRenderer.ts
Co-authored-by: Steve Sanderson <SteveSandersonMS@users.noreply.github.com>
Co-authored-by: Steve Sanderson <SteveSandersonMS@users.noreply.github.com>
[master] Update dependencies from dotnet/arcade
- Updates:
- Microsoft.DotNet.Arcade.Sdk: from 5.0.0-beta.20374.1 to 5.0.0-beta.20403.5
- Microsoft.DotNet.Helix.Sdk: from 5.0.0-beta.20374.1 to 5.0.0-beta.20403.5
* Quarantine falky test ServerEventTest.EventDuringBatchRendering_CanTriggerDOMEvents
Blazor's E2E testing uses a much shorter timeout after a test failure. This test run had several test failures, but most of these appear to be the result of
an incredibly short timeot. This PR quarantines the one test that appears to be a genuine failure and also increases the timeout duration for after test failure.
* Quarantine ServerExecutionTests.ServerGlobalizationTest.CanSetCultureAndParseCultureSensitiveNumbersAndDates
[master] Update dependencies from dotnet/efcore dotnet/runtime
- Updates:
- System.ComponentModel.Annotations: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Diagnostics.DiagnosticSource: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Diagnostics.EventLog: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Logging: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Logging.Abstractions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Logging.Configuration: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Logging.Console: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Logging.Debug: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Logging.EventLog: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Logging.EventSource: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Logging.TraceSource: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Options: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Options.ConfigurationExtensions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Options.DataAnnotations: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Primitives: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Internal.Transport: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Http: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Hosting: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Caching.Abstractions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Caching.Memory: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Configuration: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Configuration.Abstractions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Configuration.Binder: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Configuration.CommandLine: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Configuration.EnvironmentVariables: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Configuration.FileExtensions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Configuration.Ini: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Configuration.Json: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Configuration.UserSecrets: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Configuration.Xml: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.DependencyInjection: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.DependencyInjection.Abstractions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.DependencyModel: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.FileProviders.Abstractions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.FileProviders.Composite: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.FileProviders.Physical: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.FileSystemGlobbing: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.HostFactoryResolver.Sources: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Extensions.Hosting.Abstractions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.NETCore.App.Runtime.win-x64: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.NETCore.Platforms: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Win32.Registry: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.Win32.SystemEvents: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.NETCore.App.Internal: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Microsoft.NETCore.App.Ref: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Drawing.Common: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Text.Encodings.Web: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Text.Json: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Threading.Channels: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Windows.Extensions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.ServiceProcess.ServiceController: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Security.Principal.Windows: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.IO.Pipelines: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Net.Http.Json: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Net.Http.WinHttpHandler: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Net.WebSockets.WebSocketProtocol: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Reflection.Metadata: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Resources.Extensions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Runtime.CompilerServices.Unsafe: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Security.AccessControl: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Security.Cryptography.Cng: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Security.Cryptography.Pkcs: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Security.Cryptography.Xml: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- System.Security.Permissions: from 5.0.0-rc.1.20404.16 to 5.0.0-rc.1.20406.11
- Updates:
- Microsoft.EntityFrameworkCore.Tools: from 5.0.0-rc.1.20405.3 to 5.0.0-rc.1.20406.4
- Microsoft.EntityFrameworkCore.SqlServer: from 5.0.0-rc.1.20405.3 to 5.0.0-rc.1.20406.4
- dotnet-ef: from 5.0.0-rc.1.20405.3 to 5.0.0-rc.1.20406.4
- Microsoft.EntityFrameworkCore: from 5.0.0-rc.1.20405.3 to 5.0.0-rc.1.20406.4
- Microsoft.EntityFrameworkCore.Relational: from 5.0.0-rc.1.20405.3 to 5.0.0-rc.1.20406.4
- Microsoft.EntityFrameworkCore.Sqlite: from 5.0.0-rc.1.20405.3 to 5.0.0-rc.1.20406.4
- Microsoft.EntityFrameworkCore.InMemory: from 5.0.0-rc.1.20405.3 to 5.0.0-rc.1.20406.4
* Put back InternalCalls
* Removing .NET profiling calls
* Remove JS side profiling
Co-authored-by: Steve Sanderson <SteveSandersonMS@users.noreply.github.com>
* Turn on nullability annotations for public types in M.A.Hosting
* Turn on nullability annotations for Microsoft.AspNetCore and
Microsoft.AspNetCore.Server.Abstractions
Contributes to https://github.com/dotnet/aspnetcore/issues/5680
- #20818, fix e.g. references to Microsoft.Web.Xdt.Extensions in our packages
- make `@(Reference)` items much more broadly applicable
- emit an error when `@(ProjectReference)` is used instead of `@(Reference)`
- then get rid of the errors (!!)
- rename a couple of projects to match their assembly names
- then regenerate the `@(ProjectReferenceProvider)` items
- switch intersection approach from Exclude / Exclude to Copy / Update / Copy
Projects of particular interest:
- src/DefaultBuilder/src/Microsoft.AspNetCore.csproj
- honouring metadata left e.g. Microsoft.AspNetCore.Components.WebAssembly.DevServer package unchanged
- removed redundant metadata after that confirmation
- src/Razor/tools/Microsoft.AspNetCore.Razor.Internal.Transport/
- content of this package unchanged but metadata avoids extra work
- add a comment about the extra work
- src/SiteExtensions/LoggingAggregate/src/Microsoft.AspNetCore.AzureAppServices.SiteExtension/
- success! removes Microsoft.Web.Xdt.Extensions dependency from the package
- src/SiteExtensions/Runtime/Microsoft.AspNetCore.Runtime.SiteExtension.pkgproj
- add a `Condition` to avoid an ordering issue I hit here
- src/Tools/Extensions.ApiDescription.Server/src/
- avoid errors the new build ordering and timing caused
Separately, up the timeout in the `<DownloadFile />` task
- hit repeated timeouts downloading dotnet-runtime-5.0.0-rc.1.20370.4-win-x64.zip
nits:
- remove dupe `@(Reference)` item in Microsoft.AspNetCore.Components.WebAssembly.DevServer.csproj
- remove useless `%(ProjectReference.IsImplicitlyDefined)` metadata as well as its misspellings
- remove extra spaces from ProjectReferences.props
- clean up a few comments in ResolveReferences.targets
* !fixup! Correct other references to renamed projects
Using the full gc sometimes leads to an infinite recursion resulting
in a browser freeze. This was noted as part of running Blazor's benchmarks.
This is being addressed in rc1, in the meanwhile this reverts the behavior to 3.2 defaults.
Browser freezes when using a Blazor WASM application.
Yes. Full GC on is new to WASM on .NET Core
Low. Off by default is the behavior we had in 3.2.
Pranav K
Eric Erhardt
Doug Bunting
Safia Abdalla
David Fowler
Matt Mitchell
dotnet-maestro[bot]
github-actions[bot]
Kahbazi
Adam Sitnik
Justin Kotalik
Steve Sanderson
Mackinnon Buck
Roman Marusyk
Stephen Halter
Artak
msftbot[bot]
JC Aguilera
witskeeper
juanam
Ryan Brandenburg
WuYafeng
Tanay Parikh
SQL-MisterMagoo