Open PhilpD opened 9 months ago
Targeting .Net8
@arnaudleclerc We are experiencing the same issue on .NET 7.0.15
We are using Blazor WASM (client only - not server side)
Thanks for letting me know. I'll take a look at it this week.
@arnaudleclerc We are experiencing the same issue on .NET 7.0.15
We are using Blazor WASM (client only - not server side)
Same issue here on a blazor server side project migrated from .net 7 to .net 8 with all the libraries updated. Even the sample project has the same issue, both referencing the AzureMapsControl.Components or adding the last nuget package
@arnaudleclerc Thank you for taking the time. Did you manage to find the issue?
Sorry, I am currently lacking time to investigate this issue. I will do my best to look at it soon.
Locking the version to 1.13.0 solved the issue for us but ideally the missing resource get re-added to the latest package(s).
I cannot identify the issue, but I suppose it has something to do with the Github actions packing the nuget package. The same process works locally, maybe something changed on the dotnet pack command, but I didn't have time to look deeper yet.
Luckilly enough, this works fine locally. If I create the nuget package on my machine, this also includes the static web assets as expected.
I created and published a version 1.14.1 based on the main branch and published it using a release configuration. This should unblock you until I find more time to investigate the github actions. Can you please try out this version and let me know if this works for you ?
The js files are coming through with 1.14.1 thanks
1.14.0 Missing azure-maps-control.js & azure-maps-control.min.js files form nuget package. In the previous version 1.13.0 these could be found in the staticwebassets directory.
To Reproduce
hope this helps Regards Duncan