-
Notifications
You must be signed in to change notification settings - Fork 2k
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
NuGet package incomplete #634
Comments
It looks like the last two packages were updated incorrectly (unless there's something I'm missing in the nuspec file). The most recent version that will work with the default MVC5 (and under) templates is https://www.nuget.org/packages/Bootstrap.Multiselect/0.9.10 - not sure if that helps at all. |
No problem, I currently use the latest version 0.9.13 and manually added. Will this get fixed on the next package release? |
Should we consider the nuget way not supported anymore and add it manually? |
OK, did not notice this. Could someone tell me the right way of setting up the NuGet package? Personally, I am not using it myself. |
It looks like you left out the top-level Content directory, which needs to be there in order for the path into the web project to work. If you want the Css and Less directories to be placed into the web project's Content folder, you need Content > Content Or, in other words, a second level Content directory. The top-level is just there to hold the assets to be copied over. I personally follow the Bootstrap project's lead, and place the CSS file directly in the web project's Content folder. So, the contents of the package file are Content > Content > mycssfile.css I use the NuGet Package Explorer, which should warn you if you just try to drop the files directly into the package (and offer to create the top level Content). |
@davidstutz If you like, I can fix the package for you. I imagine you'd have to add me as a admin to the package. It is worth noting that Microsoft/Outercurve really wants NuGet to be reserved for binary packages; the idea is that scripts/plugins like this should live in Bower, npm, etc. I personally don't agree with that, but you could make the argument that the NuGet package needs to be retired. |
@gradexpert Add a new issue. Your question has nothing to do with this issue. |
My bad i actually wanted to know something relevant here.. I have uninstalled version 0.9.13 since it did not add .css and .js files to my solution through nuget.. |
Look a little harder, then. The files are in the dist folder. |
yes i found them thanks :) |
Why such an easy bug to fix has not already been solved? This issue was opened 3 years ago! |
Current version will be available on NuGet after NuGet finishes indexing. |
I don't know if this is actually wanted, but the NuGet package for bootstrap-multiselect does not "install" itself inside a solution. So when I added it to my project the sources where correctly pulled in the packages folder but the sources (.css, .js) where not "installed" (placed in the respective folders) inside my project. This is not a major issue since I actually have the sources in the package folder, but this will mean that for each update that I will pull with NuGet, I will have to manually replace the source files in my project.
The text was updated successfully, but these errors were encountered: