As a software developer I can manage the C# CmdMessenger client through NuGet so that I don't have to manually deal with the repository dependency in my development environment.
Hello @thijse, i have been using 3.6 for so many years and I discovered a bug recently so that I want to update to 4.2 - i had CmdMessenger always included in my projects repository which obviously is not great.
First thing i expected was that there would be a NuGet package available. It's so convenient for adding it to your projects dependencies.
Let's publish the C# client as package - that will be great. I am happy to provide a github workflow to do that during release automatically.
As a software developer I can manage the C# CmdMessenger client through NuGet so that I don't have to manually deal with the repository dependency in my development environment.
Hello @thijse, i have been using 3.6 for so many years and I discovered a bug recently so that I want to update to 4.2 - i had CmdMessenger always included in my projects repository which obviously is not great.
First thing i expected was that there would be a NuGet package available. It's so convenient for adding it to your projects dependencies.
Let's publish the C# client as package - that will be great. I am happy to provide a github workflow to do that during release automatically.
Related issue: #34