David Perfors
David Perfors
### Description On our project we have some three and four letter acronyms, that are part of a specification. These acronyms are used in code, but they will trigger S101....
Would it be possible to get ApiExplorer support for OData, so that supported query options are automatically displayed in Swagger? I know there are options like Asp.Versioning.OData.ApiExplorer that provide this...
Using .NET 6, OData 8 and the preview version of the library, I have some problems with generating correct swagger documentation for the `AllowedQueryOptions`. All the code is based on...
For a project I am working on we have to follow API design rules from the Dutch government. Unfortunately they insist on using the version in the URL, but only...
When using AspNetCore.OData 8.x I got a bit confused on how the different query options are supposed to work. And since there is no documentation for 8.x I thought I'd...
.NET 7 introduced the `UnreachableException`, which is basically meant to never been thrown. It is often used in switch statements where a default case is required by the compiler, but...
### Description This issue is similar to #5660, which was fixed some time ago. Because we have several attributes on the Program class (to suppress messages, to exclude code coverage)...
**Environment:** - Version: 5.6.7 - Branch: - [X] vs2019 - [ ] vs2017 - [ ] vs2015 - Installation/Running method: - [ ] Visual Studio Extension - [X] NuGet package...
**Description** In our web application we use `new JsonFormatter(null, renderMessage: true)` to format our messages to the console as JSON, including the RenderMessage. In ASP.NET Core 7 this resulted in...
### Describe the bug In a project where I use F# projects and C# projects I have the following code: ```csharp public class Test { public Guid Id { get;...