-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.Net 6 support. #3627
Comments
Are there plans to support Minimal API (as swagger does) |
Working on .NET 6 support (PR open) and minimal APIs... hopefully i can release a new version in the next days. |
When will this be ready? The WithName and WithTags etc is not working in the latest package. Does not affect the schema. app.MapGet("/person", () => {
return new Person("Scott", 42);
})
.WithName("GetPerson")
.WithTags("Person"); |
@RobertSundstrom Couldnt find the WithTags extension method (?) |
Support for .NET 6 and minimal API is released btw. |
@RicoSuter Do you mean that you cannot find it? It should be there. https://docs.microsoft.com/en-us/aspnet/core/fundamentals/minimal-apis?view=aspnetcore-6.0 OK. When will there be a new package? 🙂 |
@RicoSuter When will this change be released? So I can set the tags that control what clients will be generated? Right now, we just have a "default" group in Swagger UI. |
@RobertSundstrom hopefully tomorrow as we need to first fix the release pipelines. |
@RicoSuter Did you get the pipelines fixed? |
@RicoSuter Thank you, I have noticed that the changes have been published. 😊 |
Any update on when this might get published, we have a few developers on Apple Silicon and would like to use the .Net6 Runtime to build. no other .net SDKs are supported on M1 macs Thanks |
@8BitAron what version have you tried? |
@lahma on the M1 mac, we have .net6 sdk installed, on our intel macs we have 3.1 and 6 sdks and pass in the |
Try with the latest release and pass |
Any time line on this? |
NSwag supports .NET 6 - closing this issue. |
For people who have the same problem, I used the worked around: Not optimal but it now builds |
I can run the project in VS 2022 just fine and everything works.
Except when I tried to build for my release with:
dotnet publish C:\project.csproj --runtime win-x64 --configuration Release --self-contained false
I get the flowing error:
``
error NU1605: error NU1605: Detected package downgrade: System.IO.FileSystem.Primitives from 4.3.0 to 4.0.1. Reference the package directly from the project to select a different version.
From:
NSwag.Generation 13.13.2 -> Newtonsoft.Json 9.0.1 -> System.Xml.ReaderWriter 4.0.11 -> System.IO.FileSystem 4.0.1 -> runtime.win.System.IO.FileSystem 4.3.0 -> System.IO.FileSystem.Primitives (>= 4.3.0)
NSwag.Generation 13.13.2 -> Newtonsoft.Json 9.0.1 -> System.Xml.ReaderWriter 4.0.11 -> System.IO.FileSystem.Primitives (>= 4.0.1)
error NU1605: Detected package downgrade: System.Text.Encoding.Extensions from 4.3.0 to 4.0.11.
From:
NSwag.Generation 13.13.2 -> Newtonsoft.Json 9.0.1 -> System.Xml.ReaderWriter 4.0.11 -> System.IO.FileSystem 4.0.1 -> runtime.win.System.IO.FileSystem 4.3.0 -> System.Text.Encoding.Extensions (>= 4.3.0)
NSwag.Generation 13.13.2 -> Newtonsoft.Json 9.0.1 -> System.Text.Encoding.Extensions (>= 4.0.11)
``
Will this be resolved by the time .Net 6 is released or should I not use NSwag in .Net 6
The text was updated successfully, but these errors were encountered: