Note that there are some explanatory texts on larger screens.

plurals
  1. POIs nuget appropriate for daily development workflow?
    primarykey
    data
    text
    <p>I am looking at nuget for improving automatic handling of dependencies (both internal and third party) during development.</p> <p>A long as you develop through the CI Build Server, all is good:</p> <ol> <li>get latest source for A and B, where B depends on A</li> <li>fix bug in A</li> <li>build A</li> <li>check into source control</li> <li>CI Build Server initiated</li> <li>new nuget package is created and placed in corporate repository</li> <li>build B (which will get the updated A package)</li> <li>run B to verify that the bug in A was fixed n. repeat n times</li> </ol> <p>However, I'm wondering if it is possible to work locally as a single developer, without having to wait for the CI Build Server to produce a new package?</p> <p>Nuget has a feature Package Restore, which will download all dependencies automatically on build. You can also list the repository order that the Package Restore should look for packages. </p> <p>If the workflow could become:</p> <ol> <li>get latest source for A and B, where B depends on A</li> <li>fix bug in A</li> <li>build A</li> <li>(building creates a local nuget package)</li> <li>run B to test the (resolved) bug in A (should now use our local nuget package, not local repository)</li> <li>...repeat n times</li> <li>check into source control</li> <li>CI Build Server initiated</li> <li>new nuget package created in corporate repository</li> </ol> <p>Is this possible using Visual Studio, MSBuild, a CI Build Server and nuget? I'm especially interested in the making of local packages while developing locally.</p> <p>Note that I have native projects, although except the generation of nuget package post-build, this would be a workflow that I hope should work for both C# and C++ projects.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload