Chris Martinez

@HavenDV ... I hope so. I'm still championing my proposed more succinct flavor of: ```xml ``` .. but I'll take a win however I can get it

What @icnocop is really asking for is support for [§8.2.8](http://docs.oasis-open.org/odata/odata/v4.01/os/part1-protocol/odata-v4.01-os-part1-protocol.html#_Toc31358871) in the official OData specification, which doesn't appear to be supported at this level. More specifically, it's the inclusion of...

There have been many issues and discussions over the years. Admittedly, I was :trollface:ing through the issues and this seemed to be the most relevant. I was tempted to open...

sorry for the cross-post. @twmillett , @vishmittal just announced in dotnet/aspnet-api-versioning#677, official support is coming and is also here. pop on over for more details

@jineshpatel99 this is strange scenario and setup indeed. You're using API Versioning with API Explorer support, but only the intrinsic OData setup. OData 8 is not currently supported in API...

Quick update. API Versioning 6.0 is currently available in preview with support for .NET 6.0, OData 8.0, and the API Explorer extensions which can be used for OpenAPI. This bug...

I was able to reproduce the behavior using only .NET 4.5.2. No .NET Core and no multi-targeting. I'm using Visual Studio 2017 (15.3.5). ### Additional Discoveries * The issue only...

With the latest updates to Visual Studio and XUnit, I noticed there are a few twists to the conditions. The following outlines as much detail as I can with a...

I agree. No. I'm not aware of an issue being opened up against the VSTest team. Do you have a link where they track their issues? I think it's worth...

While there _could_ be benefits to targeting .NET 4.8 those are not being stated here. As long as ASP.NET Web API still targets .NET 4.5, the target should not be...