Edi.XamlControls.MetroProgressRing.Silverlight 1.1.0

dotnet add package Edi.XamlControls.MetroProgressRing.Silverlight --version 1.1.0

NuGet\Install-Package Edi.XamlControls.MetroProgressRing.Silverlight -Version 1.1.0

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="Edi.XamlControls.MetroProgressRing.Silverlight" Version="1.1.0" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

paket add Edi.XamlControls.MetroProgressRing.Silverlight --version 1.1.0

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: Edi.XamlControls.MetroProgressRing.Silverlight, 1.1.0"

#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 Edi.XamlControls.MetroProgressRing.Silverlight as a Cake Addin
#addin nuget:?package=Edi.XamlControls.MetroProgressRing.Silverlight&version=1.1.0

// Install Edi.XamlControls.MetroProgressRing.Silverlight as a Cake Tool
#tool nuget:?package=Edi.XamlControls.MetroProgressRing.Silverlight&version=1.1.0

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

A Windows 8 metro style progress ring for silverlight , converted from MahApp.Metro ProgressRing, which was for WPF only.

Original Project URL: https://github.com/MahApps/MahApps.Metro

Product	Compatible and additional computed target framework versions.
Silverlight	sl4 is compatible. sl5 is compatible.

Compatible target framework(s)

Included target framework(s) (in package)

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version	Downloads	Last updated
1.1.0	276	8/29/2013
1.0.0	123	8/29/2013

With the help of Wayne Wang, now the control is converted into a usercontrol, and no resource dictionary need to be specified in App.xaml