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>
Install
dotnet add package ThisAssembly.Vsix --version 2.1.0-beta
Install-Package ThisAssembly.Vsix -Version 2.1.0-beta
<PackageReference Include="ThisAssembly.Vsix" Version="2.1.0-beta" />
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.
This version is marked prerelease. Validate its API and upgrade path before production use.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
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.