-
Notifications
You must be signed in to change notification settings - Fork 53
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
Adding new Model from EF Wizard will crash #104
Comments
Been struggling with the same issue since 2 days ago. |
@Seiakira I rolled back my nuget for EntityFramework6.Npgsql to 3.1.1 and was able to successfully add a new data model! Thank you for the suggestion! |
ps. going this route I had to add
into my projects web.config before I could retrieve data. |
Ugh, that issue butthurts me so much... EF EDM Wizard just closing it's windows silently after connection settings. And you know what's the problem? After copying the whole database structure to another server - all is working. So it's defenitely not the problem with EntityFramework6.Npgsql itself but between this and Data Connection in Visual Studio, probably it can't parse something. |
@roji
Pretty sure this is a duplicate of npgsql/npgsql#1445 But when I tried to comment on it I was told that was for NPGSQL not EntityFramework6.npgsql.
---Issue---
As I"m going through the steps to add a data model the wizard will disappear.
---Steps---
The wizard flashes the next screen and disappears. on that screen I can see the Entity Framework 6 Radio Button is selected (not of importance to the issue).
---End Of Issue---
---Notes---
I tried this several times last week and read several of the posts that are out there. This was right before the update to EntityFramework6.Npgsql v3.2.0. At one point I checked my dependencies and think I only had the Npgsql installed and needed the EntityFramework6.Npgsql. After I had dependencies installed I was able to create a model. That is as far as my testing went that day...Then there were the new releases for Npgsql and EntityFramework6.npgsql so I updated both of those. Then I tried to retrieve data through EF.
using (var dbContext = new 360Entities())
{
return (dbContext.servers.ToList());
}
This didn't work (separate issue) so I tried starting over with a new project. Therefore this is straight out of the box and I thought this should be working. Hopefully a solution is found soon.
Sincerely
Scott~
The text was updated successfully, but these errors were encountered: