Basically when you create a component that has a dependency on another component you can specify a version number or number range that you are depending on.įor example, here is the Westwind.Data nuget which depends on Westwind.Utilities and depends on version 2.50 and later: However, when it comes to publishing NuGet packages I’ve had more than a little trouble getting my dependencies to come in with the proper version. Whether internal or external it’s a nice way to push components into applications. I update those libraries frequently and it’s made it super easy to get new versions out and distributed to existing users, as well for my own work. Personally I also use NuGet to distribute a host of Westwind libraries as part of the Westwind.Toolkit. While it’s not all unicorns and rainbows, NuGet has been one of the nicest additions to. And there are a bazillion third party components you can now get through NuGet. NuGet has become Microsoft’s main inclusion mechanism (and it looks to be come even more prominent in ASPvNext which eschews binary deployments for NuGet packages). NET, to make it easier to share and distributed shared components. NuGet is one of the best things that happened to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |