RestSharp dependency issue

[andiras]

I am having issues trying to fix RestSharp dependency when adding SalesForceSharp to my project.

When you add SalesForceSharp reference to the project, it will include the RestSharp v105.0.1 dependency. I have other library projects in the solution using the newest RestSharp v106.6.10. When I run the project I get the "Could not load file or assembly 'RestSharp, Version=105.0.1.0, " error. Checking the bin folder I have the newest RestSharp v106.6.10.

I tried to add an assemblyBinding to the project's config file to redirect the versions but it won't work because RestSharp v105 doesn't have a publicKeyToken while newest v106.6 has a publicKeyToken.

Any chance to not include the RestSharp dependency when adding SalesForceSharp reference? Any other suggestion?

Thanks

[nerdybeast]

We are running into this issue as well with SalesforceSharp v0.7.4

[awakefield]

Also having the same issue - any suggestions? I guess i'll try pulling entire project down and re-reference restsharp - hate to maintain a custom project for this unless there is a better way? thx

[giacomelli]

Also having the same issue - any suggestions? I guess i'll try pulling entire project down and re-reference restsharp - hate to maintain a custom project for this unless there is a better way? thx

Please, fork this repository, make the changes and perform a pull request, then I will review it. 👍

[awakefield]

I guess that would have been the obvious thing to do from the start! I am using a binding assembly work around at the moment but when i get back to that I'll update and do a pull request - thanks for building this tool - very useful!

…

-Adriaan

________________________________ From: Diego Giacomelli <[email protected]> Sent: Wednesday, January 29, 2020 9:40 AM To: giacomelli/SalesforceSharp <[email protected]> Cc: awakefield <[email protected]>; Comment <[email protected]> Subject: Re: [giacomelli/SalesforceSharp] RestSharp dependency issue (#35) Also having the same issue - any suggestions? I guess i'll try pulling entire project down and re-reference restsharp - hate to maintain a custom project for this unless there is a better way? thx Please, fork this repository, make the changes and perform a pull request, then I will review it. 👍 — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#35?email_source=notifications&email_token=AEUDSQ46DDKVACAGUQNX4KLRAG5RJA5CNFSM4I2E6HKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKIC4II#issuecomment-579874337>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEUDSQ3MQSVKAE5FSZYQCP3RAG5RJANCNFSM4I2E6HKA>.

[nssidhu]

I guess that would have been the obvious thing to do from the start! I am using a binding assembly work around at the moment but when i get back to that I'll update and do a pull request - thanks for building this tool - very useful!
…
-Adriaan
________________________________ From: Diego Giacomelli [email protected] Sent: Wednesday, January 29, 2020 9:40 AM To: giacomelli/SalesforceSharp [email protected] Cc: awakefield [email protected]; Comment [email protected] Subject: Re: [giacomelli/SalesforceSharp] RestSharp dependency issue (#35) Also having the same issue - any suggestions? I guess i'll try pulling entire project down and re-reference restsharp - hate to maintain a custom project for this unless there is a better way? thx Please, fork this repository, make the changes and perform a pull request, then I will review it. 👍 — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#35?email_source=notifications&email_token=AEUDSQ46DDKVACAGUQNX4KLRAG5RJA5CNFSM4I2E6HKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKIC4II#issuecomment-579874337>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEUDSQ3MQSVKAE5FSZYQCP3RAG5RJANCNFSM4I2E6HKA.

Can we get the binding redirect setting ? since i don't have old RestSharp version i don't know the public token for it.

[Sharky99x]

I am running into the RestSharp, Version=105.0.1.0
I can see a fix and commit has been requested.

Any update as to when this will be fixed and published ?

[nerdybeast]

@Sharky99x probably safe to say this repo's dead, you may want to fork it and implement your own fix.

[Sharky99x]

@Sharky99x probably safe to say this repo's dead, you may want to fork it and implement your own fix.

Ok Thank you.