Error on opening Designer (lqml)

[FlorianDahn]

Hey community,

today, i'm comming into some curious issue. I used the Designer inside of VS 2019 and it worked just fine.
Later the day I updated VS2019 to the current version of 16.11.5 (Before I was on 16.11.4)

Since then, the Designer will not open anymore. Sometimes it just opened the text/xml editor.

On the first try when using "Open with", just to be sure, im getting the message: (roughly translated) An element with the same key has been added already.

Nothing happens. It just openes that same "Open with" dialog. Second try doesn't do anything.

I updated the LinqtoSql Tools Pro to latest version and it doesn't helped. I want to just mention, that during installation it will remove the old version, so another unistall will not be necessary, hopefully.

Thank you!
Warm regards
Florian dahn

PS: I started the Entity Developer UI and directly after starting it crashed. I reported it by mail. Maybe it helps.
PS2: I also installed 2 windows 10 updates today (KB5006670 and KB5005539), I will uninstall both now and let you know.

[FlorianDahn]

UPDATE: I uninstalled the first Windows 10 Update KB5006670 and Now everything (the Designer in VS2019 and the extern Entity Designer) is working again as expected. So take care and take a look what it has to do with this update.

[pherschel]

I have the exact same problem. The standalone entity developer would start up and a small report error window would appear - then be hidden by the splash screen.

The removal of the windows update restored functionality. Thanks for finding the temp fix! I've got to support production :-)

-Pete

[Shalex]

Thank you for your report. We have reproduced the issue with Windows 10 Update KB5006670 and will notify you about the results of our investigation.

[Shalex]

The bug with launching Entity Developer after applying Windows 10 Update KB5006670 and Windows 11 Update KB5006674 is fixed in LinqConnect v4.9.2338: viewtopic.php?f=31&t=48946.

[FlorianDahn]

I downloaded and installed that Windows 10 Update KB5006670 again and can confirm that this issue is now fixed.
Thank you guys!
Warm regards
Florian Dahn