Hello,

I'm not sure why previous topic has been removed since it was more general one istead of beta only.

SO: Scenario:

MSPControl provider which worked just fine for .NET Framework latest stable version is not working for latest stable .NET Core version.

Documentation for API:

does not contain aby updates regarding what has been changed. Can someone from ST propose solution how we can handle this situation?

Some time ago when legacy API stopped working for some release I could not wait for fix and created new provider which I've called SmarterMail8580 and now it makes me wonder: should I create new provider for each change which was introduced to SM API? Since there is no information in API documentation what has been changed I need to create each time provider stop working new provider for MSPControl and perform all debugging to find out what has been modified and implement those changes under new provider.

Seriously we need some discussion here because I really feel lack of interst from ST here.

Do you know why legacy API is great? Because it allows to make basic operations on domains, mailboxes, groups etc and don't need to be changed. If something NEEDED to be added to legacy API then it was introduced in new method (so we can call it some kind of API method versioning). IMHO 95% of API usage is basic operations performed by hosting control panels and since new API is also being used by SmarterMail Web GUI this makes it much much more complex for hosting control panel providers to keep up right? Previously legacy API was used only for API access, current API is used by web GUI so it will be changed waaaaaay more frequently.

Maybe having separate API section for basic operations on all items used by hosting control panels would solve this issue:

So this section would be some kind of legacy API upgrade to new connection method and authentication while keeping it stable form.

Any thoughts on that from community and ST?

Thanks