The path 'XXXXXXX\Shared\MainLayout.razor.css' would result in a file outside of the app bundle and cannot be used like Issue #406 #27994
Labels
area-blazor
Blazor Hybrid / Desktop, BlazorWebView
s/needs-info
Issue needs more info from the author
t/bug
Something isn't working
Description
I'm working on a Maui Blazoer hybrid app with JetBrain Rider when I switch to MacCatalyst from another platform and then this
I want to start, I get the errors below. I then have to recreate the entire project and it works again. What is interesting is
that these are parts of the shared project that were created by the template.
Perhaps it is also important that I work under MacOs in the current version on an M2 chip
this is my project path: "../../../../../../../../../Volumes/Temp/DemoMaui/Apps/Demo.Maui/Demo.Maui.Shared"
app.css: The path "../../../../../../../../../Volumes/Temp/DemoMaui/Apps/Demo.Maui/Demo.Maui.Shared/wwwroot/app.css" would lead to a file outside the app bundle and cannot be used.
MainLayout.razor: The path "../../../../../../../../../Volumes/Temp/DemoMaui/Apps/Demo.Maui/Demo.Maui.Shared/Layout/MainLayout.razor" would result in a file outside the app bundle and cannot be used.
Home.razor: The path "../../../../../../../../../Volumes/Temp/DemoMaui/Apps/Demo.Maui/Demo.Maui.Shared/Pages/Home.razor" would lead to a file outside the app bundle and cannot be used.
Routes.razor: The path "../../../../../../../../../Volumes/Temp/DemoMaui/Apps/Demo.Maui/Demo.Maui.Shared/Routes.razor" would lead to a file outside the app bundle and cannot be used.
_Imports.razor: The path "../../../../../../../../../Volumes/Temp/DemoMaui/Apps/Demo.Maui/Demo.Maui.Shared/_Imports.razor" would result in a file outside the app bundle and cannot be used.
Steps to Reproduce
No response
Link to public reproduction project repository
No response
Version with bug
9.0.40 SR4
Is this a regression from previous behavior?
Yes, this used to work in .NET MAUI
Last version that worked well
Unknown/Other
Affected platforms
macOS
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
The text was updated successfully, but these errors were encountered: