After hours of successful work with Blazor Studo, I now permanently receive the error "dotnet watch msbuild: [Error] MSBuild error while processing the file ‘...\lagdb-test-2025\Server\LagdbTest2025.Server.csproj’ with the message: Lines could not be written to the file ‘obj\Debug\net9.0.NETCoreApp,Version=v9.0.AssemblyAttributes.cs’. Access to the path “C:\Users\ralfa\Source\repos\lagdb-test-2025\Server\obj\Debug\net9.0.NETCoreApp,Version=v9.0.AssemblyAttributes.cs” is denied. .
Deleting the directory, booting, deactivating OneDrive etc. has no effect.
I forgot: Blazor Studio 1.47.3; dotnet-sdks 9.0.102 [C:\Program Files\dotnet\sdk]
9.0.203 [C:\Program Files\dotnet\sdk]
9.0.300 [C:\Program Files\dotnet\sdk]
Windows 11 with all updates
I'm lost: I copied the app to a new directory; this leads to new errors: C:\Program Files\dotnet\sdk\9.0.300\Sdks\Microsoft.NET.Sdk.StaticWebAssets\targets\Microsoft.NET.Sdk.StaticWebAssets.Compression.targets(247,5): error MSB4018: Unerwarteter Fehler bei der ApplyCompressionNegotiation-Aufgabe.
After hours of working without problems..
During this time I installed no updates...
Unfortunately we see this problem for the first time. Have you made any changes to your system recently? Does installing an older version of Radzen Blazor Studio make any difference?
After two hours of copying, deleting, ending dotnet tasks und rebooting it suddenly works. I have not the slightest idea what happend. The strange ways of Microsoft software
Such errors mean there is a hung process that keeps a lock on the reported file. Usually a system restart solves the problem as it kills the hung process.
msbuild: [Error] MSBuild error while processing the file ‘...\lagdb-test-2025\Server\LagdbTest2025.Server.csproj’ with the message: Lines could not be written to the file ‘obj\Debug\net9.0.NETCoreApp,Version=v9.0.AssemblyAttributes.cs’. Access to the path “C:\Users\ralfa\Source\repos\lagdb-test-2025\Server\obj\Debug\net9.0.NETCoreApp,Version=v9.0.AssemblyAttributes.cs” is denied. .