Alek Davis

Sorry, I deleted my previous reply because I noticed something that I had not pay attention to, but I'm not sure if it is critical for this particular issue. Anyway,...

@nblumhardt I'm sorry, are you saying that we should not be using `Serilog.Expressions`? We don't really need expressions when writing to the log file, but our primary output is to...

@nblumhardt Sweet. I changed it and it works as expected. Many thanks.

I did a bit more research and switched the call from `GetJsonAsync()` to `GetStringAsync()` then deserializing the string (I validated that it contained "[]") via `JsonConvert` and it worked fine:...

Also, I tried calling the `GetJsonAsync` method that returns a `dynamic` object and it caused the same exception. So, I suspect that the strongly typed `GetJsonAsync` calls the dynamic `GetJsonAsync`...

@EWSoftware I see a few dozen schemas in the Properties window, but I'm not sure how this would help. The warning comes from the root element: ```xml ``` What schema...

They are there. So, why are the warning there? 

Ah, I see. Thanks for the info. So should these be defined is a custom namespace to make the error list clean?

I am using additional packages to address various issues (e.g. using enum names instead of numeric values, etc): Swashbuckle.AspNetCore {6.8.1} Swashbuckle.AspNetCore.Annotations {6.8.1} Swashbuckle.AspNetCore.Filters {8.0.2} Swashbuckle.AspNetCore.Newtonsoft {6.8.1} Unchase.Swashbuckle.AspNetCore.Extensions {2.7.1}

Here is my full Swagger setup logic: ```cs public static class ServiceCollectionSwaggerExtensions { /// /// Initializes Swagger configuration. /// /// /// Exposed application services. /// /// /// Logger. /// ///...