Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Are Data Sources supported? #1188

Open
MisinformedDNA opened this issue Oct 22, 2021 · 5 comments
Open

Are Data Sources supported? #1188

MisinformedDNA opened this issue Oct 22, 2021 · 5 comments
Assignees
@adegeo
Labels
dotnet-desktop/svc Pri1 High priority, do before Pri2 and Pri3 product-question Product usage related questions [org][type][category] winforms/subsvc

Comments

@MisinformedDNA
Copy link

Are Data Sources supported in .NET Core/.NET 5+? These steps don't say anything about them, but this article calls out some unsupported features in .NET Core.

The features described in this article apply to .NET Framework Windows Forms and WPF development. The features are not supported for .NET Core development, for both WPF and Windows Forms.

Is that article only referring to "Adding new data sources"? Or are data sources completely unsupported in .NET Core?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Oct 22, 2021
@PRMerger4 PRMerger4 added dotnet-desktop/svc winforms/subsvc Pri1 High priority, do before Pri2 and Pri3 labels Oct 22, 2021
@adegeo adegeo added waiting-on-feedback Waiting for feedback from SMEs before they can be merged product-question Product usage related questions [org][type][category] labels Oct 25, 2021
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Oct 25, 2021
@adegeo
Copy link
Contributor

adegeo commented Oct 25, 2021 •
edited
Loading

I believe the data sources are supported, but the wizard/designers aren't. Testing in VS 2022 points you to https://docs.microsoft.com/en-us/ef/core/get-started/wpf It would be interesting to see what the upgrade assistant does with those data source configs in a .net framework project moving to .net

@OliaG @predavid perhaps you can clarify?

@adegeo
Copy link
Contributor

adegeo commented Feb 7, 2022

Sent an email...

@adegeo
Copy link
Contributor

adegeo commented Feb 19, 2022

Whoops. I realized that this was for winforms not WPF. I'll send an email to the correct audience! 😿

@RussKie
Copy link
Member

RussKie commented Feb 21, 2022

@MisinformedDNA please checkout the latest post from @KlausLoeffelmann that discussed databinding in .NET 6 and beyond: https://devblogs.microsoft.com/dotnet/databinding-with-the-oop-windows-forms-designer/.

@adegeo adegeo self-assigned this Feb 22, 2022
@adegeo
Copy link
Contributor

adegeo commented Feb 22, 2022

This issue will be used to track updating the migration article

@adegeo adegeo removed the waiting-on-feedback Waiting for feedback from SMEs before they can be merged label Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adegeo adegeo

Labels
dotnet-desktop/svc Pri1 High priority, do before Pri2 and Pri3 product-question Product usage related questions [org][type][category] winforms/subsvc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@MisinformedDNA @RussKie @dotnet-bot @PRMerger4 @adegeo