fix: support Visual Studio 2026 package loading
This commit is contained in:
@@ -1,12 +1,12 @@
|
||||
# DSH Open File Bridge for Visual Studio 2022
|
||||
# DSH Open File Bridge for Visual Studio
|
||||
|
||||
This VSIX is a background-loaded `AsyncPackage`. Each Visual Studio process enumerates its own `IVsRunningDocumentTable`, listens for RDT changes, and publishes one protocol-v1 snapshot. This avoids the ambiguity and integrity-level failures of attaching externally through EnvDTE/ROT.
|
||||
This VSIX supports Visual Studio 2022 (17.x) and Visual Studio 2026 (18.x). It is a background-loaded `AsyncPackage`. Each Visual Studio process enumerates its own `IVsRunningDocumentTable`, listens for RDT changes, and publishes one protocol-v1 snapshot. This avoids the ambiguity and integrity-level failures of attaching externally through EnvDTE/ROT.
|
||||
|
||||
Only absolute, existing local files are published. Dirty state is read through `IVsPersistDocData`; source buffers are never copied.
|
||||
|
||||
## Build and test
|
||||
|
||||
Use a Visual Studio Developer PowerShell or a machine with the VS 2022 extension workload:
|
||||
Use a Visual Studio Developer PowerShell or a machine with the Visual Studio extension workload:
|
||||
|
||||
```powershell
|
||||
dotnet restore CoopWithDsh.sln
|
||||
|
||||
Reference in New Issue
Block a user