Project status

[theaquamarine]

Hi,

Is this project still planned? The ability to easily interface with PaperCut from .NET would be really useful, and the current situation of getting an example file out of PaperCut's install location, tracking down a decade-old library, and then having to build something custom is quite a big step to get it going.

Would it be possible to get a version of ServerCommandProxy.cs added to the repo? That'd give clarity on the license applied to it, so people know whether or not they can build on it/redistribute it/etc, and it'd form a great starting point for more work on the project, whether that's creating a pre-built library (CookComputing.XmlRpc is on NuGet, so that'd be a simple enough move) or porting it to .NET Core as discussed in the readme.

I picked this repo because of the .NET focus, but most of my thoughts would apply equally to putting ServerCommandProxy.cs in the PaperCutExamples repo, if that's a preferable solution. It's the main example for .NET with PaperCut and I'm sure there are lots of projects based on it, so it seems like a good choice for a first step.

Thanks!

[alecthegeek]

The project is not dead, but is getting limited love from us a PaperCut Software because of lack of time.

The plan is

1. Document a development setup that uses ,NET Core and provides access to a stable XML-RPC library for C#
2. Document a development setup that uses ,NET Core and provides access to a stable XML-RPC library for Powershell.
   3, Upgrade serverproxy.cs with all the missing changes to the API.

It's also hard for us because we are not .NET developers. We write cross platform code in Java and Go, so trying to get .NET working with XML-RPC is harder than we would like. Any help would be appreciated.

I know it's a pain at the moment and it's something I am keen to fix over the next few months.

Once we have all that fixed then I will look at the best way to distribute the files and any licensing changes that need to take place.

Thanks for asking. I know you are reflecting the frustrations of a lot of folks in our developer community.

[alecthegeek]

So after I replied to your question I thought I would try .NET Core again (I'm holiday so I had some time) and this time it worked!

I've added some notes in the wiki

https://github.com/PaperCutSoftware/web-services-api-dot-net-core/wiki/XML-RPC-Lib-Notes

[theaquamarine]

Is this the sort of thing you're thinking of? This tree has:

• (a placeholder version of) ServerCommandProxy.cs packaged up as a .NET Standard library.
• The beginnings of a PowerShell module which uses this. The module's set up to run on PowerShell 5+.

Both are set up so dotnet build will build them etc, though currently the ServerCommandProxy placeholder will only produce a NotImplementedException - swapping it for the one from a PaperCut install folder fixes that.

Both are also set up to build on and upload artifacts from CI using Github Actions, running on Windows, Ubuntu, and macOS.