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.

No stated dependency on Microsoft.VisualStudio.Threading, Version=17.3.0.0

See original GitHub issue

Upgrading our project to the latest version (10.2) as resulted in us being unable to utilize the Telnet Client due to an undocumented dependency on the Microsoft.VisualStudio.Threading library.

Stack Trace:

System.SystemException: Custom Exception. Cause was: The type initializer for 'PrimS.Telnet.Client' threw an exception.
 ---> System.TypeInitializationException: The type initializer for 'PrimS.Telnet.Client' threw an exception.
 ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=17.3.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

File name: 'Microsoft.VisualStudio.Threading, Version=17.3.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   --- End of inner exception stack trace ---
   at PrimS.Telnet.Client.set_IsWriteConsole(Boolean value)
   at [...]

We are able to navigate around this by including it in our project for the time being, but this needs to be listed within the Nuspec in order for Nuget to correctly identify and negotiate dependency on this library.

Issue Analytics

State:
Created a year ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

XMoose25Xcommented, Sep 7, 2022

Validated that version 11.2 works without that dependency on .net 6! Thank you for the assistance @9swampy!

1reaction

9swampycommented, Sep 2, 2022

Sorry I missed this. V0.11.0 was a kneejerk reaction to just include the required dependencies to get things working again.

https://github.com/Wumpf/IncludeToolbox/issues/73 - essentially same problem was observed here. Known issue with MS - appears to be a known issue that MS closed as low priority

Thanks for highlighting the unintended consequence. Looking in to it further… I’ll think I’ll try to follow Point 2 - Warning not applicable to .NET Core instead of accepting the VSTHRD102 warning