Oleg Deribas

@rvarna So if your issue is resolved, I guess, this could be closed?

To generate .Net client with NSwag you need OpenAPI definition file. For NSwag client generation it doesn't matter where that file comes from (azure function worker or anywhere else). So...

It seems that Microsoft has a recommended solution for this: https://github.com/Azure/azure-functions-openapi-extension/blob/main/docs/generic-cicd-pipeline-support.md which involves running PowerShell or bash script in CI/CD pipeline. I don't think they are using NSwag library in...

Both .NET Core 3.1 and .NET 5 are out of support already and .NET 8 is around the corner. So maybe drop support for old versions?

@m-demydiuk This reference is only setting minimal supported version of the package, but you always can use newer ones in your project if you reference the dependency directly of if...

@RicoSuter The 14.0.3 generated code is getting compiled without errors now but the logic of how `/GenerateBaseUrlProperty:false` flag works is different now. - Up to (and including) 14.0.0 it meant...

@MatthijsVollenbroek Which version of NSwag you are using? If it is v14 preview then it is `/assembly` argument which is not supported any more (See #4524)

@RicoSuter These are transitive references, so in order to update they need to be referenced directly. They are flagged as vulnerable by .Net 8 SDK as well. Here's output of...