Improve creating the nupkg file#121
Conversation
Create the NuGet package simply like this: > dotnet pack --configuration Release src/Mongo2Go/Mongo2Go.csproj
|
Excellent! The old nuget.exe was very inconvenient. v3.1.3 is coming this evening! 👍 |
|
I first cleaned the |
|
Glad to hear it worked. Also, good job on deprecating version 3.1.2 on NuGet. 👍🏻 Next step is considering building and publishing the package on a continuous integration system such as GitHub Actions. 😉 |
|
No, sorry. It did not worked. The final zip file does not contain the MongoDb binaries. The nuget.exe adds the |
|
What version of the .NET SDK are you using? I'm on version 5.0.202 (running on macOS 10.15.7). Here's what I did:
I hope this helps. |
|
Your commitment is awesome! 👍 Summary of the issue: After 10h working and kids, I tried to create the package after midnight. |
|
Regarding your Github Actions workflow: It looks to me like you put a bigger amount of time into this. There is definitely a lot of stuff in there (build matrix, tests, publish a tag) that would make Mongo2Go more fun, too. If I invite you to the project as a maintainer, could it be possible for you to set this up again here?! 😇NUGET_API_KEY is already added as a repo secret! 😉 |
I did put quite a lot of time into it, indeed. 😄
Sure, I can help you setting this up. Eventually, all you'll have to do to publish a new version is add an annotated tag and push that tag. |

By specifying everything in the csproj file it becomes easy to create the nupkg file with this command:
Key differences:
netstandard2.1directory.DS_StorenorREADME.mdnorMongo2Go.deps.jsonfilesHere's a before/after screenshot of the analysis of the NuGet package with NuGetPackageExplorer:
