One project per solution to create nuget packages -
i have solution 10 projects, used distribute sdk installer in day.
to change in vsts added steps create package per project, every time make change, build triggered , ps script change version of nuspec files, in end packages pushed feed, if made change 1 project build pushes new version of every packages though there no changes in of them.
someone told me wrong, should not push new version if there no change in package , every package has created separately.
that makes sense, in case, have create 9 more builds in vsts, replace project references nuget dependencies, and, if ever need change 2 projects have modify one, commit change, open second project update nuget reference , make change, seems lot of work.
so question is, there best practice or recommendation flow in creating group of nuget packages?
wiki
Comments
Post a Comment