-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 8 rc-2 support #2725
Comments
I feel like there's a larger question here. This repo hasn't seen a commit for 9 months and .NET 8 is a month away. @domaindrivendev, can you provide some insight into the near-term plans for Swashbuckle and also .NET 8? |
I was able to get the CLI to run successfully targeting However, I am now seeing an issue similar to @Berthelmaster when I target Error: It also seems to ignore the global.json
Error: Package "swashbuckle.aspnetcore.cli" failed to restore, due to Microsoft.DotNet.ToolPackage.ToolPackageException: The tool package could not be restored. Restore failed. Please advise on the availability of a new package with backwards compatibility. |
I'm getting a little bit worried, we scheduled to upgrade to dotnet 8 next month, anybody has heard from @domaindrivendev? @theonesuperdaveXTR @psiservices-dbrink what do you plan to do? We're considering migrating away from Swashbuckle :( |
Swashbuckle works just fine at runtime, having used it in many projects for years. If you cannot get its CLI to work, then you might go with that option. I did get version 6.5.0 of the CLI to work and generate both YAML and JSON files while my app was targeting You might also try the |
@Berthelmaster, I'm still evaluating the situation. The build had been broken for a bit and I just opened a PR to fix it late last week. It was the first good build since August and I hope it will trigger some activity. Are you looking at NSwag as an alternative? |
@psiservices-dbrink |
I encountered the same problem and used this workaround. Simply set the environment variable |
I have also hit an issue trying to run the CLI with the recently released .NET 8 SDK |
It looks like @domaindrivendev has abondoned Swashbuckle. I checked his LinkedIn profile to check if he has left Unsplash, but according to his profile he is still working there. I can imagine that focus shifts to another project, but it would be nice to have a statement from him, so either the community can take over or he may resume the development. |
By now 8.0.0 has landed and the problem persists.
Given the lack of other contributions on github, I hope he is alright. Given the lack of alternatives to swashbuckle, this is a rather big problem for the asp.net ecosystem :( |
The main alternative right now would be https://github.com/RicoSuter/NSwag |
ITNOA related to #2707 |
related to #2759 |
I have created a fork called DotSwashbuckle for .NET 8 and forward, it fixes some long lasting issues. |
Ahh too late, we already switched all our applications to Nswag 😅 |
We have a number of issues open that are related to adding support for .NET 8, which we plan to do in a future release in the near future. |
I'm going to close this in favour of #2792, as going through triaging the open issues I'm spotting a common theme and it's easier to manage one issue. Please track that issue for further updates. If this issue isn't resolved once we have added support for |
Hi!
We really appreciate your package, we're currently upgrading our stuff to dotnet rc2 and we get the following error:
Could it be possible to create a beta package that targets .NET 8?
We really appreciate it!
The text was updated successfully, but these errors were encountered: