Storm.SvgMagic
Metadata
Authors | Phil Oyston |
---|---|
Copyrights | Phil Oyston, Storm ID Ltd. |
Description | Provides HttpHandler fallback functionality for browsers that do not support SVG (Scalable Vector Graphics) by generating and caching alternate images at request time. Inspired by SVGMagic (http://svgmagic.bitlabs.nl/) |
IconUrl | http://stormid.com/media/48267/logo.jpg |
Language | en-GB |
Owners | Phil Oyston |
ProjectUrl | http://stormid.github.io/storm-svgmagic/ |
RequireLicenseAcceptance | False |
Summary | Provides HttpHandler fallback (image conversion) functionality for browsers that do not support SVG (Scalable Vector Graphics) |
Tags | svg |
Dependencies | Svg:1.6.1 |
Title | SVG Magic for .NET |
PackageSize | 29137 |
PackageHashAlgorithm | SHA512 |
PackageHash | /OU4wUnnU86CyfcBp6myd5etAqryopAFpDgJsoN8WxZtpUuojbvWIxaWtnuKp0r54SSvQyoUJH+Xgf7ndF7kPg== |
DownloadCount | 000000 |
CreatedDate | 2015-02-25T15:00:38 |
Access
You can access data for this project using the tools and addresses described below.
NuGet (nuget.exe)
- Installing the package (HTTP Basic authentication):
-
nuget install Storm.SvgMagic -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install Storm.SvgMagic -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
NuGet (Package Manager Console)
- Installing the package (search all configured feeds):
-
Install-Package Storm.SvgMagic
- Installing the package (HTTP Basic authentication):
-
Install-Package Storm.SvgMagic -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package Storm.SvgMagic -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package Storm.SvgMagic
OpenWrap
- Installing the package:
-
o add-wrap Storm.SvgMagic
- Uninstalling the package:
-
o remove-wrap Storm.SvgMagic
Versions
A version is snapshot of a project's source code. It does not need to follow the Major.Minor.Revision.Build numbering pattern. It can be an arbitrary string of text that identifies a release or a build, in particular including meaningful words like beta, RC or RTM.