In Visual Studio, when you add the Angular.js NuGet package, it adds a ton of angular javascript files. I've always just added the direct reference to angular.js (local or via google URL) to my projects and it always works fine.
What's the reason for using the NuGet version of Angular.js?
With Nuget it's easier to get all dependences (if they exists) and monitor updates when they comes out and install them.
But in case of Angular.js Nuget still just copy some js files in your project. So if you don't plan to follow updates and you know all dependences you can just copy your files.
Related
I have a .NET Core console app and a .NET Standard library. The app consumes the library via a nuget source in RELEASE, and a project reference in DEBUG, via a Condition on each ItemGroup.
This is working great locally, as I can make changes and test both the library and the app in parallel. When the sources get committed (obviously the library before the app), the library gets published, and the app consumes the published package.
Now, this app is also one piece of a docker-compose, and I want to be able to debug while running in Docker. This is perfectly supported with Visual Studio, but it also means my app is built against the library package available in my nuget source, not a locally-compiled and debuggable one.
I do have clues as to how to work around this, but would like to know if I'm just not either missing something, or trying to reinvent the wheel (though I really like new wheels).
I could copy the library's sources and project as part of the Dockerfile, and make sure it respects the Condition within my app's csproj. This sounds patchy.
I could have a local folder within the app sources where I copy the freshly built library's .nupkg, which would be copied via Dockerfile before dotnet restore, and also mentioned in the Nuget.Config, but ignored in .gitignore.
I'm about to try #2. Is there a simpler approach?
Thanks.
So I have Umbraco v6 currently setup via a release download and split into a class library and a website. I need to upgrade to v7 at some point and have some question on how I should setup.
What are the pros/cons of setting up through Nuget vs Downloading source and creating project?
Devin
The pro of using nuget is that you don't have to build the project from scratch. If you have a need and/or desire to understand how umbraco is built, by all means pull down the source code, but if you just want to use umbraco, and customized it thru the hooks it provides, then the nuget packages will be easier.
I've done both (though not with the latest version), and using nuget is far easier and quicker to get going.
Related to: Package an ASP.NET MVC application with Nuget
I'm trying to get a mode where I can edit an MVC project and package it easily.
As often suggested it is wise to replace a namespace using NuGet pre-processor functionality.
This would mean that I would have to edit my source files and add the pp extensions to each pre-processed source file.
Are there any tips and tricks to make this less labourious?
There is such a tool, that did almost exactly what I wanted. It's on Codeplex so I could participate in the development, yay!
https://nugetpackager.codeplex.com/
It has a common-line interface too, so I can script my updates.
I am working with nuget and find it excellent with my MVC4 project. I use it for all my external dependencies.
I have run in to one small problem with it. For example, installing the jQuery package, it places the jQuery files in to the Scripts folder. My preference is that it places the javascript files in to a libraries folder within scripts. So instead of
Scripts/jquery-1.8.3.js
I want to place it in
Scripts/libraries/jquery-1.8.3.js
Yes I can manually move it but then I lose the features of nuget. Any way that I can direct where a package places the files like this?
This is not supported yet
dupe of
NuGet scripts to different directory
, nuget codeplex issue is here http://nuget.codeplex.com/workitem/1914
Is there a fast way to move all the images and CSS from plug-ins' (like CKEditor or TinyMCE) folder to corresponding folders in the ASP.NET MVC projects' folders?
Maybe there are "out-of-the-box" or automated solutions Or the only way is to edit all the paths to the new ones?
NuGet is a Visual Studio extension that makes it easy to add, remove, and update libraries and tools in Visual Studio projects that use the .NET Framework.
When you use NuGet to install a package, it copies the library files to your solution and automatically updates your project (add references, change config files, etc). If you remove a package, NuGet reverses whatever changes it made so that no clutter is left.
You can install new packages using the package manager console.
TinyMCE Package
CKEditor Package