Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]MissingMethodException is thrown when invoking Azure search SDK #8955

Closed
angelwen1396 opened this issue Dec 2, 2019 · 6 comments
Closed
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Search Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@angelwen1396
Copy link

An exception is thrown when invoking Azure search SDK.
MissingMethodException: Method not found: 'Newtonsoft.Json.SerializationBinder Newtonsoft.Json.JsonSerializerSettings.get_Binder()'.

Steps to reproduce the behavior:
var client = new SearchIndexClient("service name", "index name", new SearchCredentials("service key name"));
var response = await client.Documents.SearchWithHttpMessagesAsync(term, searchParameters, customHeaders: headers);

It should provide the search result upon the term.

The dependencies versions are:
Microsoft.Azure.Search(3.0.4)
Microsoft.Rest.ClientRuntime.Azure(3.3.10)
Newtonsoft.json(11.0.2)

This method works when I downgrade the Newtonsoft.json to 10.0.1. But currently due to the new feature development, I need to upgrade Newtonsoft.json from 10.0.1 to higher version like 11.0.2 or higher. Then this exception was thrown.
If upgrading the version of Microsoft.Azure.Search to higher version, lot of code changes need to be made due to build failures and I am not sure if this issue can be resolved.
Is there anything I can do to get over it before making big code changes?

@triage-new-issues triage-new-issues bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 2, 2019
@AlexGhiondea AlexGhiondea added customer-reported Issues that are reported by GitHub users external to the Azure organization. Search Service Attention Workflow: This issue is responsible by Azure service team. labels Dec 3, 2019
@triage-new-issues triage-new-issues bot removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 3, 2019
@ghost
Copy link

ghost commented Dec 3, 2019

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc

1 similar comment
@ghost
Copy link

ghost commented Dec 3, 2019

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc

@AlexGhiondea
Copy link
Contributor

@brjohnstmsft could you take a look at this? Have you seen this before?

@brjohnstmsft brjohnstmsft self-assigned this Dec 4, 2019
@brjohnstmsft
Copy link
Member

@angelwen1396 This is a known issue that was fixed in version 5.0.0 back in April 2018. You will need to upgrade to at least that version, but I strongly recommend you upgrade to the latest version.

We have provided a comprehensive set of guides to upgrading code that calls the .NET SDK. It should require minimal effort on your part, and the benefit is that you will get the latest features and bug fixes. We generally do not update old SDK versions unless a critical security issue is found.

@brjohnstmsft
Copy link
Member

Closing this issue since we do not plan to backport this fix to old SDK versions. @angelwen1396 If you have trouble upgrading to the new version, feel free to ask questions on Stack Overflow and tag them with azure-cognitive-search. Engineers from our team are automatically assigned to answer such questions.

@ghost
Copy link

ghost commented Dec 18, 2019

Thanks for working with Microsoft on GitHub! Tell us how you feel about your experience using the reactions on this comment.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Search Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants