Install
.NET CLI
dotnet add package SIL.DblBundle --version 17.0.0
Package Manager Console
Install-Package SIL.DblBundle -Version 17.0.0
PackageReference
<PackageReference Include="SIL.DblBundle" Version="17.0.0" />
Frameworks
Dependencies
SIL.Core
[17.0.0, )
.NETFramework4.6.2
SIL.Scripture
[17.0.0, )
.NETFramework4.6.2
SIL.WritingSystems
[17.0.0, )
.NETFramework4.6.2
System.IO.Compression
[4.3.0, )
.NETFramework4.6.2
System.Runtime.CompilerServices.Unsafe
[6.1.2, )
.NETFramework4.6.2
SIL.Core
[17.0.0, )
.NETFramework4.8
SIL.Scripture
[17.0.0, )
.NETFramework4.8
SIL.WritingSystems
[17.0.0, )
.NETFramework4.8
System.IO.Compression
[4.3.0, )
.NETFramework4.8
System.Runtime.CompilerServices.Unsafe
[6.1.2, )
.NETFramework4.8
SIL.Core
[17.0.0, )
.NETStandard2.0
SIL.Scripture
[17.0.0, )
.NETStandard2.0
SIL.WritingSystems
[17.0.0, )
.NETStandard2.0
System.IO.Compression
[4.3.0, )
.NETStandard2.0
System.Runtime.CompilerServices.Unsafe
[6.1.2, )
.NETStandard2.0
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 3 target frameworks; confirm the exact target used by your application.
The published metadata declares 15 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.
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.