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

Opening EDMX in designer causes hang in VS2019 #726

Closed
kimjohnson opened this issue Mar 15, 2019 · 3 comments
Closed

Opening EDMX in designer causes hang in VS2019 #726

kimjohnson opened this issue Mar 15, 2019 · 3 comments

Comments

@kimjohnson
Copy link

Visual Studio Enterprise 2019 Preview, Version 16.0.0 Preview 4.2
Windows 10 Pro - Version 1803, Build 17134.648

Create a new .NET project (tried console, class library, WPF and web app). Target .NET 4.7.2 (also tried 4.5, 4.7). Add new item - data - ADO.NET Entity Data Model - EF Designer from Database - SQL Server - EF 6.x - select only 1 table - finish. The designer opens but causes VS to hang.

Alternately, open a project with an existing small EDMX file. Try to open the EDMX in the designer - VS hangs.

Also noticed that the Entity Data Model Browser and EDM Mapping Details windows are not available from View - Other Windows menu.

Tried - Repaired VS install. Also ensured that EF 6 Tools installed.

@roblarky
Copy link

roblarky commented Jun 5, 2019

I have a similar issue. I can open the EDMX and the designer shows, but the Model Browser tab/panel shows, though nothing inside it is rendered. It just shows whatever was in that area as though it's not painting. For example, click Solution Explorer tab then back to Model Browser tab and the Model Browser's contents are still the contents that were shown in the Solution Explorer. Clicking in the Model Browser has no reaction, right or left.

I've repaired, uninstalled and reinstalled EF 6 Tools, still the same problem. It's only on this machine, though; I have two other systems using the same code base and the Model Browser works fine. But the system with the issue is a brand new build, only installed VS 2019. The others are older and have had previous versions of VS installed. The solution in question was created in VS2017, which both of the other systems have installed.

@corylangston
Copy link

If you installed .NET 4.8 on your machine you should check out this solution

@ajcvickers
Copy link
Contributor

Duplicate of #788

@ajcvickers ajcvickers marked this as a duplicate of #788 Jun 26, 2019
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

4 participants