-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
.NET 8.0.203 Doesnt compile non .xaml files to the xml namespace "clr-namespace" #21299
Comments
Can you test with the latest nightly build? |
Hi @mrajkovicpta. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
Duplicate of #21170 |
Issue was not resolved with nightly build, instead it was solved by updating visual studio (Im guessing this was because it forced a workload update) |
Description
When compiling any project in blazor hybrid with the default setup will fail with the error:
The file will look like the following
despite the code completion finding all symbols in the [ProjectNamespace] namespace, when compiling these wont be included for some reason.
Changing
local:Routes
to any xaml file will allow it to compile but as the type isnt a blazor page inside a blazor web view the app will load with nothing displayed and an exception.Compiling with the new sdk also gives this warning which is not displayed when compiling with earlier versions but it could just be compiler noise
Last working version to my knowledge
Steps to Reproduce
1, Create new blazor hybrid app via dotnet new maui-blazor
2. Attempt to run
Link to public reproduction project repository
No response
Version with bug
8.0.3 GA
Is this a regression from previous behavior?
Yes, this used to work in .NET MAUI
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
Not applicable
Did you find any workaround?
Reverting sdk to 8.101 (a later one might work but I have not tried)
Relevant log output
No response
The text was updated successfully, but these errors were encountered: