-
Notifications
You must be signed in to change notification settings - Fork 1
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
ship blazor app package in spfx cdn app folder #6
Comments
using the webpart properties to inform the url of blazorapp folder until figure out how to package blazor assets to appcatalog with the same folder structure |
found out that needs to compile and package the blazor app with a custom webpack loader, like |
using file-loader as webpackloader |
opened the issue I am trying to deploy files to a subfolder in ClientSideAssets but is not working.
|
Answer: The folder "ClientSideAssets" in the SPPKG is not the actual representation of the folder that is uploaded to the App Catalog. Instead, the ClientSideAssets.xml.rels points to a list of files within the SPPKG and these files always get uploaded as a flat list to ClientSideAssets/ in the App Catalog. The ClientSideAssets/ folder that's inside the package is just for organization/debugging. Given the first issue, there's not a way to actually upload anything into a subfolder in ClientSideAssets/. So, my recommendation here (for now) would be to instead, separately deploy the Blazor app to a CDN and then reference the CDN from your web part code when loading the Blazor app. You would probably want to also add versioning on the CDN (i.e. https://somecdn.com/v1.1.0/blazorapp1/...). The team has been exploring Blazor, but we don't have an officially recommended support path for it yet. Since this is a feature you are interested in SPFx having support for, I'd also recommend filing a UserVoice ticket. |
Currently the blazor app is hosted in SiteAssets library.
Change to ship the blazor app within the spfx solution package
The text was updated successfully, but these errors were encountered: