MedallionShell.StrongName
1.6.2
dotnet add package MedallionShell.StrongName --version 1.6.2
NuGet\Install-Package MedallionShell.StrongName -Version 1.6.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="MedallionShell.StrongName" Version="1.6.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add MedallionShell.StrongName --version 1.6.2
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: MedallionShell.StrongName, 1.6.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install MedallionShell.StrongName as a Cake Addin
#addin nuget:?package=MedallionShell.StrongName&version=1.6.2
// Install MedallionShell.StrongName as a Cake Tool
#tool nuget:?package=MedallionShell.StrongName&version=1.6.2
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
| .NET Core | netcoreapp1.0 was computed. netcoreapp1.1 was computed. netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
| .NET Standard | netstandard1.3 is compatible. netstandard1.4 was computed. netstandard1.5 was computed. netstandard1.6 was computed. netstandard2.0 is compatible. netstandard2.1 was computed. |
| .NET Framework | net45 is compatible. net451 was computed. net452 was computed. net46 is compatible. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 is compatible. net472 was computed. net48 was computed. net481 was computed. |
| MonoAndroid | monoandroid was computed. |
| MonoMac | monomac was computed. |
| MonoTouch | monotouch was computed. |
| Tizen | tizen30 was computed. tizen40 was computed. tizen60 was computed. |
| Universal Windows Platform | uap was computed. uap10.0 was computed. |
| Xamarin.iOS | xamarinios was computed. |
| Xamarin.Mac | xamarinmac was computed. |
| Xamarin.TVOS | xamarintvos was computed. |
| Xamarin.WatchOS | xamarinwatchos was computed. |
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
-
.NETFramework 4.5
-
.NETFramework 4.6
-
.NETFramework 4.7.1
- No dependencies.
-
.NETStandard 1.3
- NETStandard.Library (>= 1.6.1)
- System.Diagnostics.Process (>= 4.3.0)
-
.NETStandard 2.0
- No dependencies.
NuGet packages (2)
Showing the top 2 NuGet packages that depend on MedallionShell.StrongName:
| Package | Downloads |
|---|---|
|
NanoByte.Razor2Pdf
Razor2Pdf renders ASP.NET Core Razor Pages as PDFs using WeasyPrint |
|
|
Razor2Pdf
Razor2Pdf renders ASP.NET Core Razor Pages as PDFs using WeasyPrint |
GitHub repositories (3)
Showing the top 3 popular GitHub repositories that depend on MedallionShell.StrongName:
| Repository | Stars |
|---|---|
|
madelson/DistributedLock
A .NET library for distributed synchronization
|
|
|
riganti/dotvvm
Open source MVVM framework for Web Apps
|
|
|
Azure/apiops
APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.
|