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

[XMoose25X]

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.

[9swampy]

Hi. Thx, I've been able to replicate the same issue but only when the main project is Net 4.7.2, 4.8 or 6.0. Does that match your usage?

[9swampy]

Let me know if 0.11.0 fixes the reference.

[9swampy]

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

Wumpf/IncludeToolbox#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

[XMoose25X]

I am sorry for the delay (and original brevity in the issue description) on my end! We are seeing this on .NET 6.0!
Disappointed to read that it's a known issue with Microsoft, but I thank you very much for such a quick response!

[9swampy]

v0.11.2 should have removed the dependencies. Let me know if it's worked for you?

[XMoose25X]

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