.NET May 2025 Update - .NET 9.0.5 and .NET 8.0.16 #9885
Comments
|
That link to 9.0.5 release notes is broken. |
The link is live now. Thank you for your patience! |
|
The 9.0.5.md notable change section has the phrase ".NET 9.0.4 release carries security fixes and non-security fixes." - and is mentioning CVE-2025-26682 which is from the 9.0.4 release |
|
Hi dotnet format whitespace --verify-no-changes --verbosity diagnostic
========================== Starting Command Output ===========================
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a\_temp\0a0b64ad-06be-4bf5-a936-16ee200968a8.cmd""
The dotnet runtime version is '8.0.16'.
The dotnet CLI version is '8.0.409'.
Using MSBuild.exe located in 'C:\hostedtoolcache\windows/dotnet\sdk\8.0.409\'.
Formatting code files in workspace 'D:\a\1\s\xxx.sln'.
Loading workspace.
Unhandled exception: System.Exception: The build host could not be found at 'C:\hostedtoolcache\windows\dotnet\sdk\8.0.409\DotnetTools\dotnet-format\BuildHost-net472\Microsoft.CodeAnalysis.Workspaces.MSBuild.BuildHost.exe'
at Microsoft.CodeAnalysis.MSBuild.BuildHostProcessManager.AssertBuildHostExists(String buildHostPath)
at Microsoft.CodeAnalysis.MSBuild.BuildHostProcessManager.GetDotNetFrameworkBuildHostPath()
at Microsoft.CodeAnalysis.MSBuild.BuildHostProcessManager.CreateDotNetFrameworkBuildHostStartInfo()
at Microsoft.CodeAnalysis.MSBuild.BuildHostProcessManager.GetBuildHostAsync(BuildHostProcessKind buildHostKind, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.BuildHostProcessManager.GetBuildHostWithFallbackAsync(BuildHostProcessKind buildHostKind, String projectOrSolutionFilePath, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.Worker.LoadProjectFileInfosAsync(String projectPath, DiagnosticReportingOptions reportingOptions, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.Worker.LoadProjectInfosFromPathAsync(String projectPath, DiagnosticReportingOptions reportingOptions, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.Worker.LoadAsync(CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.LoadSolutionInfoAsync(String solutionFilePath, IProgress`1 progress, ILogger msbuildLogger, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.LoadSolutionInfoAsync(String solutionFilePath, IProgress`1 progress, ILogger msbuildLogger, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildWorkspace.OpenSolutionAsync(String solutionFilePath, ILogger msbuildLogger, IProgress`1 progress, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.Tools.Workspaces.MSBuildWorkspaceLoader.LoadAsync(String solutionOrProjectPath, WorkspaceType workspaceType, String binaryLogPath, Boolean logWorkspaceWarnings, ILogger logger, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.Tools.CodeFormatter.OpenMSBuildWorkspaceAsync(String solutionOrProjectPath, WorkspaceType workspaceType, Boolean noRestore, Boolean requiresSemantics, String binaryLogPath, Boolean logWorkspaceWarnings, ILogger logger, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.Tools.CodeFormatter.FormatWorkspaceAsync(FormatOptions formatOptions, ILogger logger, CancellationToken cancellationToken, String binaryLogPath)
at Microsoft.CodeAnalysis.Tools.FormatCommandCommon.FormatAsync(FormatOptions formatOptions, ILogger`1 logger, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.Tools.Commands.FormatWhitespaceCommand.FormatWhitespaceHandler.InvokeAsync(ParseResult parseResult, CancellationToken cancellationToken)
at System.CommandLine.Invocation.InvocationPipeline.InvokeAsync(ParseResult parseResult, CancellationToken cancellationToken)
Similar to dotnet/sdk#45290 |
|
In Azure Pipelines using Setting fixed SDK version to I can provide |
After digging a bit and disabling Temporarily reverted to 9.0.203 in all builds. |
|
KO for now for Rocky Linux 9, cannot resolve dotnet-runtime-deps for 8.0.16 (max available 8.0.15) but dotnet-runtime-8.0 is already to 8.0.16. The workaround is to use the dotnet-sdk to be able to install 8.0.15 |
In addition to a binlog could you upload a compiler log. That will let us reproduce the problem very quickly. If you use Report a Problem in Visual Studio that will give you a place where you can share these files confidentially.
|
Confirmed. We are also facing this issue. Our builds have been broken since 2025-05-13 17:11:59 GMT-04:00. |
|
@jscarle did the |
|
@alfeg if you create a VS feedback issue can you post the link here? That way I don't have to wait for it to be routed, I can just grab it immediately. |
Hello @srudenkoyb will you be able to send the logs to me at [email protected] |
|
@jscarle if you're able to submit a compiler log it should allow us to root cause this very quickly. |
|
@jaredpar https://developercommunity.visualstudio.com/t/CS8785:-Generator-RazorSourceGenerator/10904192 Attaching here for reference. Issue includes msbuild.binlog and msbuild.complog. If anyone needs to do this in GitHub Actions: - name: Build app
env:
_RazorSourceGeneratorDebug: true
DOTNET_GENERATOR_DIAGNOSTICS: 1
run: dotnet build YourProject.csproj --binaryLogger
- name: Upload build log
uses: actions/upload-artifact@v4
with:
name: msbuild.binlog
path: ${{ github.workspace }}/msbuild.binlog
- name: Generate compiler log
run: |
dotnet tool install -g complog
complog create ${{ github.workspace }}/msbuild.binlog
- name: Upload compiler log
uses: actions/upload-artifact@v4
with:
name: msbuild.complog
path: ${{ github.workspace }}/msbuild.complog
|
|
@alfeg, @srudenkoyb, @jscarle: Thanks for the logs. We've traced it to a very precise loop error that will be fixed in dotnet/razor#11861. We expect to publish a toolset package you can use to work around the error in the next couple of days, with permanent fix in the next version. Thanks for the prompt reporting! |
|
Typo? edit: looks fixed now! |
|
I think it's a typo on https://github.com/dotnet/core/releases/tag/v9.0.5 because 9.0.4 already links to 9.0.105. @rbhanda @victorisr? |
|
To work around the razor issue before new SDK version is released, you can temporarily reference razor toolset package: You need to add the nuget feed, e.g., like this to a <?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<clear />
<add key="nuget" value="https://api.nuget.org/v3/index.json" />
<add key="dotnet-tools" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json" />
</packageSources>
</configuration>And then you can install the toolset package with the fix in your project file or Directory.Build.props: <ItemGroup>
<PackageReference Include="Microsoft.Net.Compilers.Razor.Toolset" Version="9.0.0-preview.25264.2">
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
<PrivateAssets>all</PrivateAssets>
</PackageReference>
</ItemGroup> |
|
I have same issue with 8.0.x Explicitly using last version before march as a temporary work-around solves the problem: |
|
@michal2612 which issue are you referring to? The one I fixed yesterday would not be affecting 8.0.xxx, as the code is only in 9.0.3xx; could you open a separate issue for your specific problem so we don't all get confused on what is broken and what is not? @jscarle @alfeg @srudenkoyb, I've broken the razor issue out into dotnet/razor#11863 for specific tracking. |
|
The 9.0.5 release seems to have invalid hashes in the releases.json, as described here: |
.NET May 2025 Update
Release Notes
Status
(Linux)
(Windows)
Issues
Please report any issues you find either by responding to this issue, creating a new issue or creating a new issue in one of the following repos:
Known Issues
The text was updated successfully, but these errors were encountered: