pharring/EditorGuidelines

Exception during loading with VS 2022 17.1

skottmckay opened this issue · 1 comments

Guidelines don't display after update to 17.1. Attempting to add a new guideline results in message saying check the activity log. Activity log has this:

  <entry>
    <record>2118</record>
    <time>2022/02/22 23:49:58.901</time>
    <type>Error</type>
    <source>Microsoft.VisualStudio.ComponentModelHost.VsShellComponentModelHost</source>
    <description>A MEF Component threw an exception at runtime: Microsoft.VisualStudio.Composition.CompositionFailedException: 
An exception was thrown while initializing part &quot;EditorGuidelines.ColumnGuideAdornmentFactory&quot;. ---&gt; 
System.IO.FileNotFoundException: Could not load file or assembly &apos;Microsoft.ApplicationInsights, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35&apos; or one of its dependencies. 
The system cannot find the file specified.&#x000D;&#x000A;   at EditorGuidelines.ColumnGuideAdornmentFactory.OnImportsSatisfied()&#x000D;&#x000A;   
--- End of inner exception stack trace ---&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.RuntimePartLifecycleTracker.InvokeOnImportsSatisfied()&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.NotifyTransitiveImportsSatisfied()&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveNext(PartLifecycleState nextState)&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveToState(PartLifecycleState requiredState)&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.GetValueReadyToExpose()&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.&lt;&gt;c__DisplayClass15_0.&lt;GetExportedValueHelper&gt;b__0()</description>
  </entry>

I tried uninstalling and re-installing the extension but still fails.

Sorry - I see this is covered by the pinned issue. Wasn't clear from the title of that that it was relevant.