OpenSource library- publishing
Following the rules at https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/publish-nuget-package
Nr |
Recomandation |
AOP Roslyn |
1 |
DO publish stable packages and pre-release packages you want community feedback on to NuGet.org. |
Done |
2 |
CONSIDER publishing pre-release packages to a MyGet feed from a continuous integration build. |
No |
3 |
CONSIDER testing packages in your development environment using a local feed or MyGet. Check the package works then publish it to NuGet.org. |
Yes |
4 |
DO use a Microsoft account to sign in to NuGet. |
Yes |
5 |
DO enable two-factor authentication for accessing NuGet. |
Yes |
6 |
DO enable email notification when a package is published. |
Yes |
For 1: Done already. However, I do not like pre-release packages
For 2: Too much hassle for a single developer. Using instead NuGet
For 3: Yes , I have already a build.bat to do this
For 4: Yes.(NuGet allows only that now)
For 5 : Yes
For 6: Yes.
Leave a Reply