Is nuget suitable for a daily development workflow?

I am considering nuget to improve the automatic handling of dependencies (both internal and third parties) during development.

For a long time, when you are developing through the CI Build Server, everything is fine:

  • get the last source for A and B, where B depends on A
  • Fix error in A
  • build a
  • check source control
  • Started CI Server
  • a new nuget package is created and placed in the corporate repository
  • build B (which will receive updated package A)
  • run B to make sure that error has been fixed; repeat n times

However, I wonder if it is possible to work locally as a single developer without waiting for the CI Build Server to create a new package?

Nuget Package Restore, . , .

:

  • A B, B A
  • A
  • A
  • ( nuget)
  • B, () ( nuget, )
  • ... n
  • CI
  • nuget,

Visual Studio, MSBuild, CI Build Server nuget? .

, , , nuget- post-build, , , , #, ++.

+4
2

, , , - , , . ! , /, , .

DLL , , , .

, nuget.

(MSBuild), . , . , .

, , , ( ).

, , , , ( ).

, , .

  • , ( ) .
  • , VS, nuget.
  • . , , , . .

  • , .
  • ( ) , .

  • nuget :
    • , VS ( ). , "" , , , , !
    • nuget , , .

  • ( , ) nuspec ! (oh ClickOnce , ..)
  • , 2 , 500 +.
  • , , , nuget ( ).
  • , MSBuild . , , . . ( 500 , ).

à la Maven, nuget , , .

+3

. NuGet "packages" , TFS. , . , NuGet, , , , NuGet.

( NuGet libs) , NuGet libs , NuGet . , NuGet .

+2

All Articles