papercutsoftware / web-services-api-dot-net-core Goto Github PK

Is your feature request related to a problem? Please describe.
If I want to manage PaperCut MF/NG from PowersShell I have to build and install DLLs manunally

Describe the solution you'd like
It like a single module that is easy to install and gives me easy access to the features of the
PaperCut MF/NG web services API

Describe alternatives you've considered
It's possible to call server-command from PowerShell, but it's very slow, only works on the application server and requires elevated privilege.

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!

I wanted to make some suggestions on things we could deliver. Hopefully that will give us some focus

1. Make it easy to use the PaperCut NG/MG web services API from Powershell and .NET languages (e.g. C#) by replacing, or updating, the current .NET Framework tools (Cook Computing XML-RPC lib and serverproxy.cs)

2. Provide some easy to use Powershell commands to install any required libraries etc

3. Track any changes PaperCut may make to the web services API.

If people can agree on these goals then we can start to create some tasks and move forward.