You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading the to the beta version I receive the following error
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Message>An error has occurred.</Message>
<ExceptionMessage>No non-OData HTTP route registered.</ExceptionMessage>
<ExceptionType>System.InvalidOperationException</ExceptionType>
<StackTrace>
at System.Web.OData.Extensions.HttpConfigurationExtensions.GetNonODataRootContainer(HttpConfiguration configuration) at System.Web.OData.Extensions.HttpRequestMessageExtensions.GetRootContainer(HttpRequestMessage request, String routeName) at System.Web.OData.Extensions.HttpRequestMessageExtensions.CreateRequestScope(HttpRequestMessage request, String routeName) at System.Web.OData.Extensions.HttpRequestMessageExtensions.CreateRequestContainer(HttpRequestMessage request, String routeName) at System.Web.OData.Extensions.HttpRequestMessageExtensions.GetRequestContainer(HttpRequestMessage request) at System.Web.OData.Extensions.HttpRequestMessageExtensions.GetModel(HttpRequestMessage request) at System.Web.OData.ETagMessageHandler.<SendAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.HttpServer.<SendAsync>d__0.MoveNext()
</StackTrace>
</Error>
The text was updated successfully, but these errors were encountered:
By the way, I believe this will be fixed in Swashbuckle.OData 3.4. When it is released, I'll try to circle back and let you know, so you can double-check.
After upgrading the to the beta version I receive the following error
This XML file does not appear to have any style information associated with it. The document tree is shown below.
The text was updated successfully, but these errors were encountered: