Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

visual studio 2022 support

See original GitHub issue

Before submitting

This repo is for Npgsql ADO.NET issues only. Entity Framework issues belong in Npgsql.EntityFrameworkCore.PostgreSQL for EF Core, or EntityFramework6.Npgsql for EF 6.x.

Steps to reproduce

run visual studio 2022

The issue

extension not installed for visual studio 2022

Exception message:
Stack trace:

Further technical details

Npgsql version: PostgreSQL version: Operating system:

Other details about my project setup:

Issue Analytics

State:
Created 2 years ago
Comments:8 (3 by maintainers)

Top GitHub Comments

3reactions

rojicommented, Oct 27, 2021

The Visual Studio extension has been discontinued - there are no plans to release a new version.

0reactions

MassimilianoCarosicommented, Apr 6, 2022

I have a project with a edmx file

So we are talking about EF 6 DB first here - yes?

The most future proof way would probably mean moving to EF Core and scaffolding a DbContext (https://medium.com/@RobertKhou/getting-started-with-entity-framework-core-postgresql-c6fa09681624 and https://docs.microsoft.com/en-us/shows/On-NET/Migrating-EDMX-projects-to-Entity-Framework-Core might help too), but most people I know who are still using EF6 are somehow stuck with it, so this probably won’t help you a lot. Am I right?

If you can’t or don’t want to move to EF Core I don’t see much of an alternative to keeping an old Visual Studio instance around somewhere in order to update your EF6 model.

Yes, EF Core is in the road map. I needed something more quick to face the contingency. Thank you.