Quantcast
Channel: Active questions tagged nuget-package - Stack Overflow
Viewing all articles
Browse latest Browse all 3067

Deploy demo and retail version of a .NET library via NuGet

$
0
0

I need to deploy a commercial .NET library via NuGet (most likely, it will be a local source used mainly in Microsoft Visual Studio). First my potential customer installs the NuGet package with the demo version of the library for evaluation. If the customer likes it and buys it, he/she will get the retail version of the library with full functionality unlocked. Obviously, the most natural way to obtain it for the customer is to update the existing NuGet package. What is the recommended way to do this?

As I understand the NuGet infrastructure, I should play with the package versions and suffixes for them. My first try was to use suffixes '-demo' and '-retail' for the NuGet package of the same version - for example, MyLib.1.0.0-demo.nupkg and MyLib.1.0.0-retail.nupkg. But both packages were classified as pre-release versions, which would not look good for the customer. Then I tried to remove the '-retail' suffix from the retail package, and this looked better - though I don't like that the demo version is still classified as pre-release.

Maybe, there other name/version schemes for this. If so, please, recommend.


Viewing all articles
Browse latest Browse all 3067

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>