Effective development workflow with Nuget?

Question

Nuget is a great tool, but it seems to complicate the overall process of iteratively modifying libraries and hosting at the same time.

For example, in an application, if we have an application and 5 Nuget packages, and we want to start changing the three Nuget packages. There seem to be limited effective options.

Scenario 1: Download 4 copies of Visual Studio (one for the application and one for each package), change the packages, wait for the packages to be created, updated, host changed, build, rinse and repeat.

Scenario 2: In the main application, rip out the Nuget dependencies and add the proj and iteration files efficiently. However, after you are satisfied with the packages, you need to restore the / proj solution files (Nuget recovery, etc.).

What are we missing here? In an open source world, this is very convenient.

Answer 1

NuGet is a good tool for version libraries that can be developed, tested, and released as isolated packages. If you can consider them as a product, with feature requests, bug fixes, and a work plan, NuGet will support the release of new versions for use by systems.

, , . , , NuGet . .

, , ; .