Timeline for One project per solution to create nuget packages
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 2, 2022 at 17:22 | comment | added | Josh Gust | I should add to this response that Project References within the solution should also be included in the artifact. Example: if A references B and A changed, my answer there will version both A and B. Even though B didn't change, it should be included because of A's dependency upon it. NuGet + dotnet transform project references into package dependencies, so the new version of A will automatically be looking for the new version of B. If you fail to publish it, you're in for some issues. | |
| Aug 26, 2022 at 3:17 | comment | added | Treker | Thank you for your thoughtful response. It certainly helped me, even all these years later! | |
| Jul 3, 2019 at 17:00 | review | First posts | |||
| Jul 3, 2019 at 18:27 | |||||
| Jul 3, 2019 at 16:55 | history | answered | Josh Gust | CC BY-SA 4.0 |