Update Unsupported Legacy API Version

[tpperlman]

Hi Folks,

We're using this .NET implementation for our SalesForce integration and just received this email from SF:

You are receiving this email because you’re an admin of an org that is actively using the legacy API endpoints. Versions 21.0 through 30.0 of the Salesforce Platform SOAP, Bulk, and REST APIs are currently unsupported and you need to take action before May 2023.

Is there a particular API version that this library is using? If it is set for retirement, will there be an updated library to use?

--Phil

[marknadig]

@tpperlman , I've not seen a lot of activity on this project. You might have better luck going through Salesforce support to see where this library stands. I believe it is the 'official' package for SF and .net
https://developer.salesforce.com/blogs/developer-relations/2014/01/announcing-the-salesforce-toolkits-for-net

(appreciate if you circle back with any new news from SF)

[marknadig]

Doing my own research, seems maintainer (Wade) left SF January '21 https://www.wadewegner.com/2021/01/mahalo-a-aloha-salesforce/

[tpperlman]

Thank you for the research. Not good news for anyone who has implemented this library, unless someone at SF is going to pick up the torch. It may be a non-issue at the moment if it is using an API version > v30.

[garethm79]

I'm just implementing something using it, you can specify the API version in the AuthenticationClient and ForceClient constructors. In the current release the version defaults to v36.0. I'm very new to using SF, but I suspect that the API is backwards compatible except for features deprecated or changed on the platform itself.

I'd suggest upgrading to the latest release (which is still several years old of course) and then change the API version to something supported and then test your functionality. If you are using a standard system then it will probably work. I have specified v56.0 for mine and and can add/list the built-in objects ok.

[kvansaders]

@wadewegner ,
Any advice on how to get this library picked up again by Salesforce, or at least handed over as a community project? I'd hate for this to reach a point of no return with updates, since it's still pretty robust.