Skip to content
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

1.14.0 Missing azure-maps-control.js & azure-maps-control.min.js files #84

Open
PhilpD opened this issue Jan 30, 2024 · 9 comments
Open

Comments

@PhilpD
Copy link

PhilpD commented Jan 30, 2024

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

  1. Create new Blazor Web App
  2. NuGet add AzureMapsControl.Components 1.14.0

hope this helps
Regards Duncan

@PhilpD
Copy link
Author

PhilpD commented Jan 30, 2024

Targeting .Net8

@ikappas
Copy link

ikappas commented Feb 1, 2024

@arnaudleclerc We are experiencing the same issue on .NET 7.0.15

We are using Blazor WASM (client only - not server side)

@arnaudleclerc
Copy link
Owner

Thanks for letting me know. I'll take a look at it this week.

@marco-manfroni
Copy link

@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

@ikappas
Copy link

ikappas commented Feb 13, 2024

@arnaudleclerc Thank you for taking the time. Did you manage to find the issue?

@arnaudleclerc
Copy link
Owner

Sorry, I am currently lacking time to investigate this issue. I will do my best to look at it soon.

@latusekpiotr
Copy link

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).

@arnaudleclerc
Copy link
Owner

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 ?

@PhilpD
Copy link
Author

PhilpD commented Mar 4, 2024

The js files are coming through with 1.14.1 thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants