Closed yehu1999 closed 10 months ago
Unfortunately Visual Studio 2022 + my extension seem to work only in some versions and not in other versions. Often the problem goes away with the next release of VS. I did not find out why. Hopefully the next version of VS removes the problem for you.
I have the same problem in VS 2022 (v17.6.2). The version of this extension is 0.11.166. When I open a solution in VS. It will occur an error shown in following picture. It means VS can't load "EditorPackage" successfully. The problem may be occurred by profile changed or an extension installed. Furthermore, another problem is shown when I tried to open any source code files. I tried to close all extensions but glsl to address problems. These problems will appear only when glsl extension is enabled. I hope this information is helpful for you.
Same problem here, using VS 2022 v17.6.5 on Windows 11.
THe new version may resolve this issue. Please try it out.
Possibly related issue #112
Had this issue on VS2022 17.5.x but updating to 17.7.5 fixed it 🙂
在VS2022 17.5.x上遇到此问题,但更新到17.7.5修复了此问题 🙂
YEAH!
Any remaining problems with VS 2022?
Any remaining problems with VS 2022?
My previous VS version 17.3.x and I met the same problem,by upgrading VS, the problem disappeared and all works fine🙂!
Any remaining problems with VS 2022?
Everything is all right!Great tool,very useful,thanks for fixing it!
I have same problem with vs 2022 17.8.7,update to 17.9.6, it works fine
Good
Installed product versions
Description
I couldn't open every file(.cpp/.h/.c/.myfiles) if I use this extension.
Steps to recreate
Current behavior
When open a file, it says "No EditorOptionDefinition export found for the given option name". I want to fix it by the way in https://stackoverflow.com/questions/23893497/no-editoroptiondefinition-export-found-error and I try to reboot, but they didn't work both. if I close this extension,everything comes to normal. so I think the problem maybe from the extension.
Expected behavior
I want to use it without ERROR.