Open Bitfiddler opened 3 years ago
I think the process of adding releases as NuGet packages can be split into two main steps:
Creating nuget.org account and doing manual releases (building on local machines and then sending the built package into nuget.org account via web interface or CLI) https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package
Creating a GitHub workflow script that builds the project on GitHub server and publishes it automatically or on click https://github.com/marketplace/actions/publish-nuget
The first step could be made by anyone, but looking for future step 2, the ideal option would be if maintainer of this repository creates nuget.org account, because step 2 will require to set Nuget API Key into this project secrets.
@roelvandersteen @WillemJann what do you think?
Unfortunately I have to say that this project is no longer maintained by us. Therefore, don't expect a new release, a PR review, or any other activity on this repository. This library was mainly for internal use. We currently don't have time and priority to continue work on PerfectXL-EPPlus.
The good news: the code is open source. Feel free to fork and continue coding on your own initiative :) Everyone is free to release and publish new versions (project is licensed under LGPL).
Just wondering if creating a NuGet package for future releases in at all on the horizon?
Would love to use your library instead of EPPlus, but managing libraries manually is a bit retro for the projects I'm working on these days and I can't seem to find any existing PerfectXL nuget package.
I know this is not a small ask, but if you can automate it, it would make your library much more popular (if you consider that a good thing).