-
Notifications
You must be signed in to change notification settings - Fork 161
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
Microsoft.AspNet.OData NuGet Package Upgrade Causing delay in the Functionality #1264
Comments
@Akhil4025 you will need to provide more detail than this. Can you repro the issue, maybe create a small sample that reproduces the slowdown? |
@Akhil4025 could you share more information about the affected scenarios? Like @julealgon mentioned, a small sample that reproduces the issue would be great. |
Below is the code from .js file which is calling the Server side API. var userNotificationFlag = { return $http({ method: 'POST', url: ApiUrl + 'Users', data: userNotificationFlag }).then(function (data) { Below is the Server Side API which is being called [HttpPost] The delay is happening when the control is trying to reach from .js code to .net code that I have mentioned above. This is how our sever side code is being configured WebApiConfig.cs: Global.asax.cs: |
And I tried to pass --> $rootScope.userID as the data alone after Odata upgrade Instead of **var userNotificationFlag = { "userID": $rootScope.userID, "subscribeToNotificationFlag": value, };** and I observed that API call is quick as it was before the upgrade of Odata package. I'm not sure how the parameters are causing the issue after Odata upgrade. |
Hi,
I have upgraded Microsoft.AspNet.OData NuGet Package in our application from 7.5.14 to 7.7.5 and since then it is causing delay in few of the Api calls in the application. Before upgrade everything works fine without causing any delay. The scenario is same when I upgrade the same package to 7.6.0 and above versions.
Please advise if anyone knows the root cause of this behavior.
The text was updated successfully, but these errors were encountered: