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.

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

Create really simple samples for different platforms and providers #2137

Open
8 of 13 tasks
ajcvickers opened this issue Feb 24, 2020 · 9 comments
Open
8 of 13 tasks

Create really simple samples for different platforms and providers #2137

ajcvickers opened this issue Feb 24, 2020 · 9 comments

Comments

@ajcvickers
Copy link
Member

ajcvickers commented Feb 24, 2020

For two reasons:

For the second point, we should also update the issue template.

Matrix:

  • Platforms
    • Console
    • Blazor
    • ASP.NET Core
    • Windows Forms
    • WPF
    • UWP/WinUI
    • Xamarin
  • Database providers
    • SQL Server
    • SQLite
    • In-memory
    • Cosmos
    • Npgsql
    • MySQL

(There is a lot of overlap here with other issues; we can de-dupe or not as appropriate as we make progress based on whether we also need more complex examples and also for creating the docs that reference the samples.)

@ajcvickers ajcvickers self-assigned this Feb 24, 2020
@ajcvickers ajcvickers added this to the 5.0.0 milestone Feb 24, 2020
@ajcvickers
Copy link
Member Author

@dotnet/efcore Please add any providers and platforms I missed that you think are important. Also, please comment if you think some combination is not relevant/not important.

@AndriySvyryd
Copy link
Member

To avoid combinations explosion consider creating a single project for all providers and use comments or preprocessor directives to allow easy switching.

And note that model building can be conditional, e.g.

if (context.Database.IsSqlServer())
{
}

Also don't do anything for the in-memory provider as we shouldn't encourage it to be used in this way.

@ajcvickers
Copy link
Member Author

Also don't do anything for the in-memory provider as we shouldn't encourage it to be used in this way.

What if people are reporting bugs that only repro on the in-memory provider?

@AndriySvyryd
Copy link
Member

What if people are reporting bugs that only repro on the in-memory provider?

Exactly what we are trying to avoid dealing with.

@ajcvickers
Copy link
Member Author

@AndriySvyryd Not convinced. ;-)

@AndriySvyryd
Copy link
Member

Just trying to save you time

@JohnGalt1717
Copy link

read the review comments on this... from the team that can't be bothered to do it for themselves and respect paying customers.... surreal. You should be in a panic to get this actually done and working and ready for your customers... instead you're nit picking?

@AndriySvyryd
Copy link
Member

@JohnGalt1717 You can also use https://github.com/smitpatel/EFSampleApp before a more comprehensive solution is available

@JohnGalt1717
Copy link

I was just told that one would NEVER be available in another ticket that I just closed because I'm not going to put all of this effort in when the team at Microsoft (richest business in the world, paid $200,000 or so by my company a year) won't put effort in to get this setup in a comprehensive way and is copying and pasting code that sets up an empty Context and nothing else as if that somehow shortens the curve to replicate the endless bugs in EF Core 3.1 that didn't exist in EF Core 2.2

@ajcvickers ajcvickers modified the milestones: 5.0.0, Backlog Dec 16, 2020
ajcvickers added a commit that referenced this issue Aug 4, 2022
ajcvickers added a commit that referenced this issue Aug 4, 2022
ajcvickers added a commit that referenced this issue Aug 4, 2022
@ajcvickers ajcvickers removed their assignment Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants