EditorGuidelines: "Package did not load correctly"

Maybe this isn’t supported yet, but when I try to set a guideline in Visual Studio 17.1.0 Preview 1.0, I get:

The ‘EditorGuidelinesPackage’ package did not load correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file ‘C:\Users\username\AppData\Roaming\Microsoft\VisualStudio\17.0_e8dd53cc\ActivityLog.xml’.

Restarting Visual Studio could help resolve this issue.

image

ActivityLog.xml shows:

<entry>
  <record>652</record>
  <time>2021/11/10 02:36:02.197</time>
  <type>Information</type>
  <source>VisualStudio</source>
  <description>Begin package load [EditorGuidelinesPackage]</description>
  <guid>{A0B80B01-BE16-4C42-AB44-7F8D057FAA2F}</guid>
</entry>
<entry>
  <record>653</record>
  <time>2021/11/10 02:36:02.198</time>
  <type>Error</type>
  <source>VisualStudio</source>
  <description>LegacySitePackage failed for package [EditorGuidelinesPackage]Source: &apos;EditorGuidelines&apos; Description: 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;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;File name: &apos;Microsoft.ApplicationInsights, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35&apos;&#x000D;&#x000A;   at EditorGuidelines.EditorGuidelinesPackage.Initialize()&#x000D;&#x000A;   at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)&#x000D;&#x000A;&#x000D;&#x000A;WRN: Assembly binding logging is turned OFF.&#x000D;&#x000A;To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.&#x000D;&#x000A;Note: There is some performance penalty associated with assembly bind failure logging.&#x000D;&#x000A;To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].&#x000D;&#x000A;</description>
  <guid>{A0B80B01-BE16-4C42-AB44-7F8D057FAA2F}</guid>
  <hr>80070002</hr>
  <errorinfo></errorinfo>
</entry>
<entry>
  <record>654</record>
  <time>2021/11/10 02:36:02.202</time>
  <type>Error</type>
  <source>VisualStudio</source>
  <description>SetSite failed for package [EditorGuidelinesPackage](null)</description>
  <guid>{A0B80B01-BE16-4C42-AB44-7F8D057FAA2F}</guid>
  <hr>80070002</hr>
  <errorinfo></errorinfo>
</entry>
<entry>
  <record>655</record>
  <time>2021/11/10 02:36:02.206</time>
  <type>Error</type>
  <source>VisualStudio</source>
  <description>End package load [EditorGuidelinesPackage]</description>
  <guid>{A0B80B01-BE16-4C42-AB44-7F8D057FAA2F}</guid>
  <hr>80070002</hr>
  <errorinfo></errorinfo>
</entry>

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 5
  • Comments: 21 (8 by maintainers)

Commits related to this issue

Most upvoted comments

Found it: “Developer Analytics tools” Launch the Visual Studio Installer, find the VS 2022 Preview channel and select “Modify” Then go to “Individual Components” and search for “Developer Analytics”. Check the “Developer Analytics tools” check box and update your installation. image

That should fix it. @JVimes @bddckr FYI. Please try the steps above and let me know if the issue is fixed.

The fix will have to come from the Visual Studio team in a 17.1 update. I’ve engaged VSIX support on an internal channel and I’ll also file a feedback ticket.

Another thought: a small temporary note (until mainstream VS is fixed) on your feature page (https://marketplace.visualstudio.com/items?itemName=PaulHarrington.EditorGuidelinesPreview&ssr=false#overview) briefly cautioning hopeful users that there is a known issue with a workaround, would have actually pre-empted me from contacting you, as the solution is already covered in github. Just an idea. Cheers! - Sid

Just wanted to say thank you @pharring for researching and posting a workaround. Made my day.

I can confirm that updating to VS 2022 v17.2.x fixes the above issue.