You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- We want the scoped css bundle path to always point to the root path of the app, overriding the default base path unless it is not explicitly overriden
222
+
<!-- We want the scoped css bundle path to always point to the root path of the app, overriding the default base path unless it is not explicitly overridden
223
223
by the user. This is so that when you are developing a server-side application or in the future potentially an ASP.NET application using css isolation,
224
224
you don't have to make the urls in your files relative to "_content/$(PackageId).styles.css".
225
225
If the user chooses to override the base path explicitly, we place the bundle at the root of the defined base path, this allows Blazor WebAssembly applications to be hosted
<!-- We want the scoped css bundle path to always point to the root path of the app, overriding the default base path unless it is not explicitly overriden
221
+
<!-- We want the scoped css bundle path to always point to the root path of the app, overriding the default base path unless it is not explicitly overridden
222
222
by the user. This is so that when you are developing a server-side application or in the future potentially an ASP.NET application using css isolation,
223
223
you don't have to make the urls in your files relative to "_content/$(PackageId).styles.css".
224
224
If the user chooses to override the base path explicitly, we place the bundle at the root of the defined base path, this allows Blazor WebAssembly applications to be hosted
0 commit comments