c# - NuGet Packages, Active Development and References -
we have 1 solution contains of our shared assemblies. referencing these assemblies based on relative path (../../../../../sharedsolution/bin). nice create nuget package (or few based on various dependencies) reference these assemblies can update , don't have worry having exact same directory structure else on team , other benefits of nuget.
however, let's when i'm working in projectasolution, realize need make change or add shared class sharedsolution. in projectasolution if have referenced assemblies sharedsolution nuget package, i want test changes sharedsolution before committing them, way copy assemblies sharedsolution bin projectasolution's packages folder?
since editing classes in sharedsolution, i'm beginning think nuget might not right way share these assemblies.
another possible solution add projects sharedsolution links of projectsolutions need reference them. better alternative?
is there better way share these assemblies relative path? is there easy way test changes made on dev machine nuget package?
you can build pre-release package. developers set nuget use pre-release packages see them, else still using latest stable.
a explanation , how-to can found on nuget pre-release package page.
to address questions raised in comment:
you can build nuget packages locally, based on .nuspec file next .nupkg file in packages folder. can use nuget package explorer in gui.
to distribute them, can store pre-release packages on network folder. developer interested in pre-release package can add network folder nuget sources , can use visual studio-integrated nuget usual. or can copy them .nupkg file.
Comments
Post a Comment