After Update Visual Studio 17.10.5. to 17.11.0 our .NET8 Blazor WASM Project can be build but it doesn't run anymore

Question

We have updated 3 Machines (W11,Windows SERVER 2022, independent from each other) from 17.10.5. to 17.11.0.

After that, the Project can still be build but after starting in we get this eroor within a second:

The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core.

The program '[28324] XERP.Server.exe' has exited with code 3221226505 (0xc0000409).

Then we tried to fix it (Deleting, Cleaning everything) , restarting PC,Updateting .NET 8.0.4 to 8.0.8. Check dump etc. But we didn't found the issue.

After a downgrade on 2 Machines. On 1 of them it is running again, but another stil has the issue.

Answer 1

Hello @Michael Haak,

Welcome to Microsoft Q&A forum.

If this issue only appears on this specific project, please kindly double check and manually remove the hidden .vs folder, bin and obj folders in your solution/project folder, then rebuild your project and rerun it.

Also consider, whether some NuGet packages/assemblies are used in this project but may be/may be not updated along with VS and cause some compatibility issues.

Kindly double check the version of the target framework. You can check your project target framework in .csproj file => <TargetFramework>net8.0</TargetFramework>. If you have other projects in your solution or using other projects outside of your project, try to confirm if they target a previous version of .NET Core. Try to install previous version of .NET Core if necessary(like .NET Core 3.1 from VS Installer > Modify > Individual components, .NET Core 2.2 from here: Download .NET Core 2.2).

Best Regards,

Tianyu

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

SOLVED!

Hi,

it was only in 1 procect and it was caused by .NET 8.0.400 and 8.0.401.

Everything runs fine if I install 8.0.304