Force.com-Toolkit-for-NET
Force.com-Toolkit-for-NET copied to clipboard
The Force.com Toolkits for .NET provides an easy way for .NET developers to interact with the Force.com & Chatter REST APIs using native libraries.
I am getting the following error: > ForceException: Binary data included but file attachment information is missing. If providing rich JSON/XML input in multipart REST, make sure to include Content-Type...
Fixed spelling error "Lighting" to "Lightning" in readme file.
return initial response message if can't parse response error, otherwise it's not possible to understand cause of error https://github.com/wadewegner/Force.com-Toolkit-for-NET/pull/378
This addresses portions of [pull request 268](https://github.com/wadewegner/Force.com-Toolkit-for-NET/pull/268) which were not implemented yet and also would resolve [issue 372](https://github.com/wadewegner/Force.com-Toolkit-for-NET/issues/372)
When using UpdateAsync, and passing an object with a datefield set to null or nothing, the json for that fields does not get sent up to salesforce. How do we...
Simple readme change to the examples. Thank you for your work on this client! I did sign the CLA.
I am new to using this package and I am receiving an error when using DescribeLayoutAsync. I am getting back records with the QueryAsync. Thank you in advance for any...
I clicked on this link and received a 404 error You can see a demonstration of this in the following sample application: https://github.com/developerforce/Force.com-Toolkit-for-NET/tree/master/samples/WebServerOAuthFlow
It would be useful if we could access `signature` and `issued_at` parameters after getting a token. I also add a method to revoke current access token. Might solve issue #45.
Looks like ForceException had a field for a status code but it was never being filled even though it was often being created due to non-success status codes. This PR...