search

mwpowellhtx / BumpAssemblyVersions

A flexible way of Bumping Assembly Versions with a rich set of instructions how to do so.
GNU General Public License v3.0
4 stars 0 forks source link

Added development tips section #8

Closed Germs2004 closed 3 years ago

Germs2004 commented 3 years ago

Since I had no prior experience with NuGet development, I had a hard time figuring out how to get started with debugging this project. These tips should assist others who are interested in getting involved in this project. Feel free to modify as you prefer.

mwpowellhtx commented 3 years ago

@Germs2004 Bottom line for you, hopefully it was at least a learning experience for you then, since as far as I am concerned, package delivery plumbing is pretty much the norm in terms of inner/outer loop engagement. I'll review the notes, but scanning them initially, much of what is mentioned, I think, is unnecessary. If we elaborate anything, I think it should be a --help switch in the publish.cmd file, which I use to deploy the package for internal verification, and . Everything else should be automatically plumbed considering the NuGet.Config in strategic src and usage areas. Nothing else should be required there IMO.

mwpowellhtx commented 3 years ago

...and then, possibly could add a relative path to the usage NuGet.Config that directs a package source to the inner loop assembly package itself. Which if I haven't added such a configuration to the usage area, perhaps would make sense to do so.

mwpowellhtx commented 3 years ago

Closing this one. I appreciate the feedback.