-
Notifications
You must be signed in to change notification settings - Fork 55
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
Latest VS 2022 preview is breaking bolero with _ResolveCssScopes not found #317
Comments
Ah, it seems the internal target name has changed for the generation of CSS scopes... This will indeed have to be addressed before the release of .NET 8. Meanwhile, as a workaround, if you're not using CSS scopes for your own components then you can just comment out this target. |
Thanks. I was able to build but the app does not run with net 8.0 and aspnet 8.0 preview bits. Looks like more fundamental changes are needed. I see the following exception at startup (even before enabling wasm threads):
|
I am using dotnet version 8.0.100-rc.1.23463.5 on Linux and I am still getting a similar error: |
Yes, sorry, I've taken some time to release the next version of Bolero. It should be out by the end of the week. |
This has now finally been released in v0.23. |
I would like to try .Net 8 and blazor web assembly multi-threading so am using VS 2022 preview.
The issue is here:
I will appreciate any suggestions you might have for a quick fix. Likely this will have to be addressed anyway, in time.
Below is my VS 2022 configuration:
The text was updated successfully, but these errors were encountered: