-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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 Data hub page taxonomy #19029
Comments
@BillWagner can you tag this for the .NET wave and assign to the .NET Data project? |
|
Hi, @Rick-Anderson. EF Core is listed and the legacy EF documentation will still exist. Rationale behind the platform-specific is thinking of "desktop platforms" (WPF, WinForms) verse. ASP.NET Core as the "web platform." The section may need a better name but the idea was if you are doing file->new (project type) that we have specific guidance for approaches to data with that project type. |
Some additional libraries that come to mind:
|
End-to-end scenarios “I want to…”
|
What about UWP? |
Hi @JeremyLikness - is this task to create a hub page or landing page, or both? |
Both, I think |
Addressing this effort in dotnet/EntityFramework.Docs #3833 |
Closing this as it was addressed in dotnet/EntityFramework.Docs#3833 |
A new .NET Data landing page will help .NET developers quickly navigate to the area of interest. Data spans multiple topics, so first it is important that the categories and topics are correct. Ultimately this may result in sub-category pages being created. Once the hierarchy and topics are approved, new issues will be created to track the categories and determine what documents can be linked to "as is", what documents will need to be updated and what new documents should be created.
Here is the draft outline (feedback welcome):
The text was updated successfully, but these errors were encountered: