Uploaded image for project: 'Qt Visual Studio Tools'
  1. Qt Visual Studio Tools
  2. QTVSADDINBUG-876

Qt VS Tools->Qt Visual Studio Tools version: 2.7.1: Initializing STUCK and no longer working

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Reported
    • Priority: Not Evaluated
    • Resolution: Unresolved
    • Affects Version/s: 2.7.1
    • Fix Version/s: None
    • Component/s: General
    • Labels:
      None
    • Environment:
    • Platform/s:
      Windows

      Description

      Just noticed was updated to 2.7.1 a few days ago and now it appears to be stuck initializing permanently. Last few days were on non-GUI work and today I tried to open a UI file. Noticed Qt VS Tools->Qt Visual Studio Tools version 2.7.1: Initializing and disabled after I could not open a UI file e.g cannot open designer! So restarted VS which takes while with my 138 project solution - but to no avail!!!! Did not realise I had automatic updates turned on for this extension. Will certainly be disabling option that once I get it it out of this horrific mess!

      After looking through the visual studio installer logs...
      <entry>
      <record>2547</record>
      <time>2021/03/08 10:13:18.296</time>
      <type>Error</type>
      <source>VisualStudio</source>
      <description>SetSite failed for package [Vsix]Source: 'QtVsTools' Description: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=16.8.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=16.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'Microsoft.VisualStudio.Threading, Version=16.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at QtVsTools.Vsix.InitializeAsync(CancellationToken cancellationToken, IProgress`1 progress) at Microsoft.VisualStudio.Shell.AsyncPackage.<>c_DisplayClass20_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b1>d.MoveNext() --- End of stack trace from previous location where exception was thrown -- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Threading.JoinableTask.<JoinAsync>d_68.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) at Microsoft.VisualStudio.Services.VsTask.GetResult() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. </description>
      <guid>

      {15021976-647E-4876-9040-2507AFDE45D2}

      </guid>
      <hr>80070002</hr>
      <errorinfo></errorinfo>
      </entry>

      I think I can hazard a guess as to the nature of the issue.

      The Microsoft.VisualStudio.Threading.dll on my machine is an older version
      I need to update visual studio. I had deferred updating as previous VS updates had broken lib and obj compatibility with several 3rd party packages.

      If correct then I would also conclude that.

      SINCE IT IS TECHNICALLY INCORRECT FOR A VSIX (or in fact any software) TO AUTOMATICALLY UPDATE ITSELF IF THE TARGET ENVIRONMENT IS INCOMPATIBLE WITH THE UPDATE

      THE QT VSTOOLS AUTO UPDATING REALLY SHOULD NOT HAVE OCCURRED.

      Perhaps it is possible for future updates to check target environment compatibility first - that is if the MS environment permits!
      I shall attempt to uninstall it and reinstall the earlier version (qt vs tools) assuming that is possible otherwise I have time and costs incurred getting 3rd party products up to date and moving on with the latest compatibility breaking visual studio updates. Actually I shall probably jut restore Dev VM from backup with disconnected network until I disable VS tools update!

      Update:
      In the end I decided to move forward rather than back and got my VS environment updated - which incidentally took ages. Everything was working fine after that. Only cost about a days work and a rebuild of the whole universe! With obvious detriment to my rather massive software installer and incremental update package sizes but that's all - at least its still in beta! My previous comment regarding rolling out of updates to incompatible environments still stands!

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            mecfc Miguel Costa
            Reporter:
            bluespider David Hussey
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Gerrit Reviews

                There are no open Gerrit changes