ThisAssembly.Vsix
Allows consuming VSIX manifest properties from code, as well as MSBuild project properties from the VSIX manifest. For example: partial class ThisAssembly { public static partial class Vsix { public const string Id = "MyVsix"; } } or <PackageManifest Version="2.0.0" ...> <Metadata> <Identity Id="|%CurrentProject%;VsixId|" Version="|%CurrentProject%;VsixVersion|" Language="|%CurrentProject%;VsixLanguage|" Publisher="|%CurrentProject%;VsixPublisher|" /> <DisplayName>|%CurrentProject%;VsixDisplayName|</DisplayName> <Description>|%CurrentProject%;VsixDescription|</Description> </Metadata> ... </PackageManifest> > This project uses SponsorLink to attribute sponsor status (direct, indirect or implicit). For IDE usage, sponsor status is required. > IDE-only warnings will be emitted after a grace period otherwise. Learn more at https://github.com/devlooped#sponsorlink.
Install
dotnet add package ThisAssembly.Vsix --version 2.0.12
Install-Package ThisAssembly.Vsix -Version 2.0.12
<PackageReference Include="ThisAssembly.Vsix" Version="2.0.12" />
Frameworks
Dependencies
Adoption guide
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
Compatibility metadata lists 1 target framework; confirm the exact target used by your application.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.