-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add support for .NET 6.0 #197
Comments
You are absolutely right and we've already done some work to support .NET 6. In fact, PR #194 does exactly that. Unfortunately we've ran into an issue with DACFX (see microsoft/DacFx#33) which doesn't seem to work on .NET 6 due to some breaking changes. Since that isn't open source there isn't really a lot I can do about that, except making sure that those that can make a difference are aware of the issue. |
Hi! I'm also following the case. What about to release preview/beta version with .net6 supporting depending on preview DacFx-version? |
I have a preview version in the works in #194 that will add support for .NET 6. Just waiting for a review. |
Is it going to publish a preview version on nuget once the PR is merged? |
That's the idea yes. |
I have just uploaded version 2.0.0-beta.1 to NuGet and should be available shortly, which includes support for .NET 6. |
@jmezach I am using the |
@alexmg Thanks for trying it out and the positive feedback. Much appreciated. From what I understand the DacFx team is planning to release before the end of the year, so hopefully soon. |
@jmezach, I am also using the 2.0.0-beta.1 package with the .NET 6.0 SDK and works great! Thank you! Is there a timeframe for the non-beta version to be released? |
See my previous comment. Still waiting for a stable release of DacFx. |
@jmezach mentioned in #165 (comment) that once .NET 6.0 has a go-live license (supported in production), support could be added to this SDK as well.
6.0.0-rc1 was released on Sept 14th and has one: https://devblogs.microsoft.com/dotnet/announcing-net-6-release-candidate-1/
The text was updated successfully, but these errors were encountered: