将VS2019扩展移植到VS2022时遇Catastrophic failure错误求助

问题概述 #

将Visual Studio 2019的工具窗口扩展移植到Visual Studio 2022后，首次启动VS时扩展可正常工作，但后续打开工具窗口会抛出以下COM异常：

Exception details:
System.Runtime.InteropServices.COMException (0x8000FFFF): Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.VisualStudio.Shell.Package.CreateFrameForToolWindow(ToolWindowCreationResult result, Int32 id, Guid persistenceGuid)
   at Microsoft.VisualStudio.Shell.Package.<>c__DisplayClass84_0.<CreateToolWindow>g__CreateToolWindowWorker|1()
   at Microsoft.VisualStudio.Shell.Package.CreateToolWindow(Type toolWindowType, Int32 id, UInt32 flags, Object context, Guid persistenceGuid)
   at Microsoft.VisualStudio.Shell.Package.CreateToolWindow(Type toolWindowType, Int32 id, Object context)
   at Microsoft.VisualStudio.Shell.Package.<>c__DisplayClass94_1.<<FindToolWindow>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Shell.Package.<>c__DisplayClass94_0.<<FindToolWindow>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Shell.ToolWindowCollection.ToolWindowListener.<>c__DisplayClass1_0.<<-ctor>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Threading.AwaitExtensions.ExecuteContinuationSynchronouslyAwaiter`1.GetResult()
   at Microsoft.VisualStudio.Threading.AsyncLazy`1.<>c__DisplayClass13_0.<<GetValueAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Threading.AsyncLazy`1.GetValue(CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Shell.Package.FindToolWindow(Type toolWindowType, Int32 id, Boolean create, ProvideToolWindowAttribute tool)
   at Microsoft.VisualStudio.Shell.Package.CreateToolWindow(Guid& toolWindowType, Int32 id)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.<ConstructContent>g__ConstructContentFromPackage|145_1(WindowFrame frame)
   at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.ConstructContent()

• 临时缓解手段：删除C:\Users\username\AppData\Local\Microsoft\VisualStudio路径下的Visual Studio 17*本地目录可恢复正常，但仅生效一次。
• 使用环境：Microsoft Visual Studio Professional 2022 (64-bit) - LTSC 17.4 - Version 17.4.4
• 已完成操作：将DLL引用从旧版本更新至17.*版本，例如替换Microsoft.VisualStudio.Shell.dll为Microsoft.VisualStudio.Shell.15.0.dll

排查与解决建议 #

1. 修正Shell引用版本 #

• 当前使用的Microsoft.VisualStudio.Shell.15.0.dll是VS2017版本组件，存在兼容性问题，需替换为VS2022对应的Microsoft.VisualStudio.Shell.17.0.dll。
• 确保项目引用的Microsoft.VisualStudio.SDK NuGet包版本匹配VS2022 17.4.4，建议使用17.4.x系列的SDK包。

2. 检查ProvideToolWindowAttribute配置 #

• 移除VS2019特定的配置项，验证Style、MultiInstances、Transient等属性是否适配VS2022窗口管理机制。
• 临时设置Transient = true禁用窗口状态持久化，若问题消失，说明是持久化状态冲突导致的异常。

3. 清理工具窗口初始化逻辑 #

• 检查工具窗口类的构造函数、OnToolWindowCreated方法，确保没有持有过时的VS对象引用，窗口关闭后正确释放资源。
• 避免在窗口持久化状态中存储无法序列化的对象，VS2022对状态序列化机制有更新。

4. 验证Package类实现 #

• 确保Package类的Initialize方法没有重复注册工具窗口，或在后续启动时重复执行初始化逻辑。
• 检查FindToolWindow方法的调用参数，特别是create参数的使用场景是否正确。

5. 调试窗口创建流程 #

• 启用VS扩展调试模式，在工具窗口构造函数、CreateToolWindow调用点等关键位置设置断点，跟踪后续启动时的异常触发路径，定位具体的资源冲突或对象引用问题。

内容的提问来源于stack exchange，提问作者Pranav Gour