C# Web Services Library - update?
I've been using the Github C# library for interacting with the AssetOperationHandlerService. It's now 5 years old and I'm wondering if there's any plan to support this further and release an update to this library. In particular the API for publishing an Asset has changed and the current library won't work with our version of Cascade 7.14.1. We don't support PHP on our web server so a .Net library is our only option.
Any development roadmap regarding web services for the .Net crowd?
Thanks.
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Tim on 18 Apr, 2016 03:57 PM
Hi,
Unfortunately we don't have any plans at the moment to update that particular library. When you have the chance, feel free to post an idea on our Idea Exchange so that others may vote/comment on it.
Let me know if you have any additional questions.
Thanks
2 Posted by Wing Ming Chan on 18 Apr, 2016 04:22 PM
Hi,
I just want to point out one thing: web service scripts can be run anywhere to communicate with your Cascade instance. That means that you can have your own personal web server (I have that in my own lab-top) that supports PHP and hence you can run PHP scripts to talk to your Cascade instance, without the support of your production web server. You can even use your personal web server to communicate with the production web server and the Cascade instance at the same time.
Wing
3 Posted by sander on 18 Apr, 2016 04:43 PM
Wing, interesting idea, but not practical with our application running in the production environment. I have taken a look at your php librabry and would like to take some time to explore it further. Tough to convince the server admins to support php at this time unfortuneately.
Thanks,
Simon
Tim closed this discussion on 18 Apr, 2016 07:49 PM.