Some version of Visual Studio (VS) extension does not appear to be working with some version of VS

🌎 Discussion in English
1

continuing from here: Visual Studio extension does not appear to be working with 17.8.7

Hi,

Which is the newest VS version that I can install so that the DotVVM VS extension will work?

Currently I have VS Community 2022 Version 17.8.7 and DotVVM for Visual Studio 2022 v4.0.572.0 and this appears every time I start VS:

image

From ActivityLog.xml:

508	ERROR	SetSite failed for package [DotvvmPackage]Source: 'DotVVM.Integration.VisualStudio.VS2022' Description: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=17.10.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=17.10.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.VisualStudio.Threading, Version=17.10.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at DotVVM.Integration.VisualStudio.VsPackages.DotvvmPackage.InitializeAsync(CancellationToken cancellationToken, IProgress`1 progress)
   at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass21_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)
   at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)
2

Microsoft regularly makes updates to Visual Studio available. Every time they release an update, Riganti must make changes to the DotVVM extension. This takes an undefined amount of time.

Before updating VS, it’s always a good idea to check the Release Notes for the extension to determine if the new VS version will be supported.

As of the time of this posting, the supported latest VS version is 17.10.2 for VS 2022 and 16.11.37 for VS 2019.

Riganti will eventually get an update out there and that will resolve the issue. (Until MS makes other breaking changes again.)

I hope this helps.

3

I was lazy to not search for that page (Release notes). Thanks and yes, I’ll consult it from now on.

PS: It is working now with VS Community 2022 v17.10.4