-
Notifications
You must be signed in to change notification settings - Fork 498
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
[Preview] Clean Preview install on Windows 2016 - Exception encountered starting EditorServices #2393
[Preview] Clean Preview install on Windows 2016 - Exception encountered starting EditorServices #2393
Comments
Interesting... The last update to the extension should have redistributed that assembly Can you give me a full dump of what's in this directory?
if you use vscode insiders the path will be |
Here you go
|
Interesting. It's definitely in there... Naturally the workaround for this is:
But @rjmholt explicitly wanted to fix this scenario with the last Preview so maybe something was missed there |
I'm okay with workarounds (at least 2nd one) - it would be nice to have a graceful message, rather than a crash. |
I'm going to look into this, since it's unexpected. We might also be able to catch certain assembly load exceptions if they're thrown in the right way, but I can't guarantee anything until I've had a look. |
Experienced the very same issue today on a fresh install, Windows Server 2016. I'll now try the workaround of installing .NET Framework 4.7.2 or higher.
|
I've have a fix for this, linked above and have tested it on Windows Server 2016 with .NET 4.6.2 and .NET 4.7.0. So this should be fixed in the next release. |
Issue Description
I am experiencing a problem with...
It's a test Domain Controller and I wanted to test something out. First time install, straight install of Preview Extension, and only that extension.
Attached Logs
Follow the instructions in the README about
capturing and sending logs.
Environment Information
Visual Studio Code
PowerShell Information
Visual Studio Code Extensions
Visual Studio Code Extensions(Click to Expand)
The text was updated successfully, but these errors were encountered: