extension no longer loads in VS2019 after PR #331

Describe the bug

extension no longer loads in VS2019 after PR #331

To Reproduce Steps to reproduce the behavior:

1. install extension or update from older version
2. start VS2019 and you get an error message

Expected behavior

extension should work fine in VS2019

Versions(please complete the following information):

• OS: Windows 10
• Devskim Version 0.5.6.63595

Additional context

SetSite failed for package [VSPackage]Source: 'Microsoft.DevSkim.VSExtension’ Description: Die Datei oder Assembly “Microsoft.VisualStudio.Threading, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden. System.IO.FileNotFoundException: Die Datei oder Assembly “Microsoft.VisualStudio.Threading, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden. File name: 'Microsoft.VisualStudio.Threading, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’at Microsoft.DevSkim.VSExtension.VSPackage.InitializeAsync(CancellationToken cancellationToken, IProgress`1 progress)at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass20_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext()

PR #331 updates dependencies to VS2022 version (version 17.x) so loading fails under VS2019 as it is 16.x

[MagicAndre1981]

you may have installed the VS2022 RC/preview side by side to VS2019 so you have the required dll on your system , I always run each VS version in a separate VM

That may be it - I do have 2022 side by side, but I was running the extension in 2019

this doesn’t matter, your system has the file so VS2019 uses it. New version 0.6.3.46140 works fine again in VS2019 and highlights issues in .cs files.

[gfs]

Very odd. I did confirm that it worked running debug from Visual Studio before merging

you may have installed the VS2022 RC/preview side by side to VS2019 so you have the required dll on your system , I always run each VS version in a separate VM

That may be it - I do have 2022 side by side, but I was running the extension in 2019 (and it in fact it is not test or marked compatible with 2022 yet, I’ve just been using it to test .NET 6). Just pushed another commit that downgrades all the other 17.x packages to 16.x.