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

Cannot install these using the client side library manager instead of using the nuget packages. #162

Open
AraHaan opened this issue Apr 9, 2023 · 2 comments
Milestone

Comments

@AraHaan
Copy link

AraHaan commented Apr 9, 2023

The following can be installed using the client side library manager:

image

However, as you can see, the 2 scripts that are not selected cannot which is sad, and I feel like they should be able to be installed that way as well (instead of as nuget packages) as an option.

@AraHaan
Copy link
Author

AraHaan commented Apr 9, 2023

Also, I think that this package should outright depend on the fact that they really should be getting those other packages using that client-side library manager over the nuget package versions of them due to various reasons.

  1. They could always decide to stop shipping nuget packages of their libraries and only ship to npm / the domains that the client-side library manager can install from.
  2. They could sometimes ship security fixes to those places much faster than to nuget.org.

Because of those reasons I think it would be great to actually remove the dependance packages of the package versions of jquery and the jquery validation packages in favor of that feature, if the developer wants to use the package versions of those then that is on them and not on the aspnet team.

@AraHaan
Copy link
Author

AraHaan commented Apr 9, 2023

Looks like I looked in the wrong place to find the unobtrusive scripts from the client-side library manager, but will still modify the nuget package version though to let them know that it is recommended to use that manager over the packages.

AraHaan added a commit to AraHaan/jquery-validation-unobtrusive that referenced this issue Apr 9, 2023
This helps resolve aspnet#162 and other issues that users may face when they want to use the client-side library manager feature in Visual Studio.
@mkArtakMSFT mkArtakMSFT added this to the Backlog milestone Nov 9, 2023
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

Successfully merging a pull request may close this issue.

2 participants