We are large users of NuGet, we have 25-30 packages that we provide on a network resource.
We would like to be able to test new packages before they are created and released in consuming applications. Ideally, this can be done using something similar to a Maven snapshot and having a specific development package (for example, a snapshot function ).
Has anyone else come up with, ideally, non-hacks, a way to do this?
Our preferred method is to generate package assemblies and then manually overwrite the assemblies in the packages / directory, that is, replace the actual project references, but this does not seem particularly clean.
Update:
We use the CI assembly server, which creates assemblies for each commit and has a manually-defined NuGet assembly that works with specially marked versions of the code base. We donβt want to create a NuGet build for each commit, but we would like to test a likely candidate in the wild before we start building the NuGet package manually.
source
share