Publishing inklecate as a dotnet tool would have a lot of benefits:
It is easier to publish than uploading a Github release with dotnet pack and dotnet nuget push
Incrementing the version number can be annoying to remember. But the repo already uses tags, so a tool linke MinVer would version the package automatically based on the closest tag
It is easier to install for cli users with dotnet tool install
It is easier for update for cli users with dotnet tool update
This worked great on my machine (Win10). I also pushed the package to a private GitLab package repository and install the package in a linux dotnet container and it worked!
Use Case
In my particular use case, I wanted to setup a pipeline to compile my inks into json whenever I push. The problem is installing inklecate in linux is kinda a pain. I noticed that we were using .Net Core 3 so I wondered how hard it would be to convert this to a dotnet tool. Then I could use a dotnet linux container (mcr.microsoft.com/dotnet/sdk) and:
Publishing inklecate as a dotnet tool would have a lot of benefits:
dotnet pack
anddotnet nuget push
dotnet tool install
dotnet tool update
Testing
Here is how I tested this change:
This worked great on my machine (Win10). I also pushed the package to a private GitLab package repository and install the package in a linux dotnet container and it worked!
Use Case
In my particular use case, I wanted to setup a pipeline to compile my inks into json whenever I push. The problem is installing inklecate in linux is kinda a pain. I noticed that we were using .Net Core 3 so I wondered how hard it would be to convert this to a dotnet tool. Then I could use a dotnet linux container (
mcr.microsoft.com/dotnet/sdk
) and:Next Steps
This is just how I would go about fleshing out the pipeline:
Further reading