Skip to content
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

[VS Code] Could not load file or assembly 'XXXXXX, Version=X.X.X.X, Culture=neutral, PublicKeyToken=XXXXXXXXXXXX'. The system cannot find the file specified. #112

Closed
Salty923 opened this issue Feb 24, 2018 · 16 comments

Comments

@Salty923
Copy link

Error:

Could not load file or assembly 'System.Net.NetworkInformation, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Steps to Reproduce:

Version Data
extensionName VSLS
extensionVersion 0.2.163
protocolVersion 2.1
applicationName VSCode
applicationVersion 1.20.1
platformName MacOS
platformVersion 16.7.0
@lostintangent
Copy link
Member

lostintangent commented Feb 24, 2018

@Salty923 Thanks for reporting this! Any chance you recall how to repro it? Did you get this error immediately after installing the extension? After trying to share? Something else?

@Chuxel
Copy link
Member

Chuxel commented Mar 7, 2018

@samirbehara also hit this. Steps to Reproduce:

  1. I upgraded my VSCode version to 1.20.1 (1.20.1) and installed the VS Live Share Extension.
  2. When I click on the 'Share' button, I get this error.

From @srivatsn: could you please check if the dll is present in the extension directory i.e <user directory>\.vscode-insiders\extensions\ms-vsliveshare.vsliveshare-0.2.163\dotnet_modules\System.Net.NetworkInformation.dll

Response from @samirbehara: I verified that the dll is present in the extension directory.

@Chuxel
Copy link
Member

Chuxel commented Mar 7, 2018

@samirbehara Did you happen to have multiple windows open when installing the extension when you hit this? (Trying to determine if this is a variation of #124)

@samirbehara-zz
Copy link

@Chuxel - I will confirm that I did not have multiple windows open while installing the extension.
I spent some time trying to recreate this issue. However noticed that once I closed and reopened VSCode, the issue auto resolved and I am able to use the Live 'Share' option.

@Salty923
Copy link
Author

Salty923 commented Mar 7, 2018 via email

@Chuxel
Copy link
Member

Chuxel commented Mar 7, 2018

@Salty923 @samirbehara That is good news. 👏

@srivatsn Should we merge this in with #124 which has a fix in the queue or keep it open since the behavior was slightly different?

@srivatsn
Copy link

srivatsn commented Mar 7, 2018

I think this is different - the workaround for #124 is to uninstall and reinstall the extension. Here @samirbehara found that the file did exist on disk and simply reopening VSCode solved it. I don't understand why that would be yet.

@samirbehara-zz
Copy link

@srivatsn -- I uninstalled and reinstalled the VS Live Share extension, however was not able to replicate the error.
I also revoked the VS Live Share authorization to my GitHub account and tried to do the installation all over again, but it worked fine. So at this point I am not able to replicate this error.
It has to be some exception after you sign in to your account for the first time, where it is not able to load the necessary dll.

@Chuxel
Copy link
Member

Chuxel commented Mar 14, 2018

Consolidating #131 under this same bug. Bug info from @ffxsam:


Error:

Could not load file or assembly 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.

Steps to Reproduce:

  1. Tried to sign in via user code, because GitHub oauth wasn't working
Version Data
extensionName VSLS
extensionVersion 0.2.206
protocolVersion 2.1
applicationName VSCode
applicationVersion 1.21.0
platformName MacOS
platformVersion 17.4.0

@Chuxel Chuxel changed the title [VS Code] Could not load file or assembly 'System.Net.NetworkInformation, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified. [VS Code] Could not load file or assembly 'XXXXXX, Version=X.X.X.X, Culture=neutral, PublicKeyToken=XXXXXXXXXXXX'. The system cannot find the file specified. Mar 14, 2018
@avanderhoorn
Copy link
Member

Could the next person who runs into this issue please take a look at ~/.vscode/extensions/ms-vsliveshare.vsliveshare-xxx/dotnet_modules and confirm if the file it says can't be loaded is actually there?

@Chuxel
Copy link
Member

Chuxel commented Mar 26, 2018

Merging in #162 - @avanderhoorn, @ anubhavmishra did verify that the files were indeed on disk.


Error:

Could not load file or assembly 'System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=REDACTED'. The system cannot find the file specified.

Steps to Reproduce:

  1. Clicked signed in.
  2. Used Github to login.
  3. Login was successful, but saw the error on VSCode.
Version Data
extensionName VSLS
extensionVersion 0.2.260
protocolVersion 2.1
applicationName VSCode
applicationVersion 1.21.1
platformName MacOS
platformVersion 16.7.0

From @Chuxel:

Hey @anubhavmishra, thanks for reporting this!! I think you're hitting #112. Can you try completely shutting down VS Code and then reinstalling the extension to verify that fixes the problem?

Also, could you please take a look at ~/.vscode/extensions/ms-vsliveshare.vsliveshare-0.2.260/dotnet_modules and confirm System.Runtime.Serialization.dll is actually there?


From @anubhavmishra:

It gave me the same error message as above but for another file:

Could not load file or assembly 'System.Net.Http.Formatting, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.

I then went on to check whether that file existed under ~/.vscode/extensions/ms-vsliveshare.vsliveshare-0.2.260/dotnet_modules and it was there. Then I restarted VScode again, signed in and everything worked. :)

@Chuxel
Copy link
Member

Chuxel commented Mar 27, 2018

Merging #155 from @Dussed.

@Dussed - Could you please take a look at ~/.vscode/extensions/ms-vsliveshare.vsliveshare-0.2.260/dotnet_modules and confirm System.Runtime.Serialization.dll is actually there? After that, you should just be able to restart VS Code completely or failing that uninstall and re-install the extension to unblock you.


Error:

Could not load file or assembly 'System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.

Steps to Reproduce:

  1. Install extension for vs code on mac os
  2. Sign in via github
  3. Error appears
Version Data
extensionName VSLS
extensionVersion 0.2.260
protocolVersion 2.1
applicationName VSCode
applicationVersion 1.21.0
platformName MacOS
platformVersion 17.4.0

@Chuxel
Copy link
Member

Chuxel commented Apr 3, 2018

We have put steps in to resolve this with release v0.2.307! It's possible there are still scenarios where this error could occur, so please let us know if you encounter the problem again.

@Chuxel
Copy link
Member

Chuxel commented Apr 4, 2018

Reopening. 😭 It appears there is still a code path that is causing this error though the most recent report is a different assembly. Merging this in here to have a consolidated source. From #176 from @awentzel.


Error:

Could not load file or assembly 'Microsoft.Cascade.Ssh, Version=0.2.0.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.

Steps to Reproduce:

  1. Occurs after installing on MacOS

Really too many steps to figure out where it went wrong. Took literally 15 different attempts and different ways of installing, reloading, shutting down vscode, then restarting. This seems to be what finally did the trick to get it to run. But, lots of errors along the way.

Version Data
extensionName VSLS
extensionVersion 0.2.307
protocolVersion 2.1
applicationName VSCode
applicationVersion 1.19.1
platformName MacOS
platformVersion 17.5.0

@Chuxel
Copy link
Member

Chuxel commented Apr 18, 2018

We just released v0.2.399 that should provide some improvements in this space. It would be interesting to hear if anyone hits this again with this update.

@lostintangent
Copy link
Member

Closing this as resolved since we addressed it in an update, and we haven't seen it reported since. Please re-open if you experience this bug again. Thanks!

Chuxel added a commit that referenced this issue Oct 26, 2018
Delete accidentally added .build folder
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants