ROPC: Fix/ mitigate EF docs

[Rick-Anderson]

Close https://github.com/dotnet/EntityFramework.Docs/issues/4788 when this is completed dotnet_EntityFramework_Docs

• [x] Connection Strings
• [x] Connection strings and models
• [x] Scaffolding (Reverse Engineering)
• [x] Configuration File Settings
• [x] EF Core tools reference (Package Manager Console) - EF Core
• [x] EF Core tools reference (.NET CLI) - EF Core
• [x] Multi-tenancy - EF Core
• [x] Azure Cosmos DB Provider - EF Core
• [x] What's New in EF Core 5.0
• [x] Entity Framework 6 SQL Server provider based on Microsoft.Data.SqlClient
• [x] Visual Studio Releases - EF6
• [x] Applying Migrations - EF Core
• [x] Port from EF6 to EF Core - Detailed Cases
• [x] Using migrate.exe - EF6
• [x] Database Providers - EF Core
• [x] Porting from EF6 to EF Core - Porting a Code-Based Model - EF
• [x] Tools & Extensions - EF Core
• [x] DbContext Lifetime, Configuration, and Initialization - EF Core
• [x] Enum Support - EF Designer - EF6
• [x] Code First Conventions - EF6
• [x] Interceptors - EF Core
• [x] Database First - EF6
• [x] What's New in EF Core 6.0
• [x] Code First to an Existing Database - EF6
• [x] Advanced Performance Topics
• [x] Entity Framework Designer Keyboard Shortcuts - EF6
• [x] Breaking changes in EF Core 7.0 (EF7) - EF Core
• [x] Databinding with WinForms - EF6
• [x] Databinding with WPF - EF6
• [x] The Entity Framework 6 provider model - EF6
• [x] Overview of Entity Framework Core - EF Core
• [x] Upgrading from previous versions to EF Core 2 - EF Core
• [x] Get Started with Windows Forms - EF Core
• [x] Dependency resolution - EF6
• [x] Porting from EF6 to EF Core - Behavior changes
• [ ] Porting from EF6 to EF Core - Porting an EDMX-Based Model - EF

For details see: SFI info in Teams

See CS Dashboard per email thread.

---

Associated WorkItem - 295456

[wadepickett]

@Rick-Anderson (cc @tdykstra), checking through the SFI Dashboards own linked spreadsheet for the repo tab for EF docs: Absolutely all items are now set to "fixed". Do you know who set all to fixed? Is that the case that they are all fixed?

Looking through the items in that spreadsheet for repo ef docs I am seeing some that do not look fixed, but maybe I am not interpreting the issue correctly:

For example:

Password issue flagged for this topic: https://github.com/dotnet/EntityFramework.Docs/blob/main//entity-framework/core/managing-schemas/migrations/applying.md " The following example applies migrations to a local SQL Server instance using the specified username and password.

.\efbundle.exe --connection 'Data Source=(local)\MSSQLSERVER;Initial Catalog=Blogging;User ID=myUsername;Password=myPassword' "

[Rick-Anderson]

Absolutely all items are now set to "fixed". Do you know who set all to fixed? Is that the case that they are all fixed?

I was under the wrong assumption that triaged meant fixed. So I'll change them to NA or "In Progress" as appropriate.

[Rick-Anderson]

Password issue flagged for this topic: https://github.com/dotnet/EntityFramework.Docs/blob/main//entity-framework/core/managing-schemas/migrations/applying.md " Create an issue for that (in our repo and the EF repo) link each issue and assign that to Tom for October.

[Rick-Anderson]

Fixed in https://github.com/dotnet/EntityFramework.Docs/pull/4849

[Rick-Anderson]

@wadepickett

@Rick-Anderson (cc @tdykstra), checking through the SFI Dashboards own linked spreadsheet for the repo tab for EF docs: Absolutely all items are now set to "fixed".

They're all fixed now