FluentRouting.Mvc
Metadata
| Authors | Arjen Post |
|---|---|
| Description | ASP.NET MVC Fluent Routing is a thin wrapper around the ASP.NET MVC attribute routing engine. With Fluent Routing you can define your routes using a fluent interface, but with the full power of the attribute routing engine (inline route constraints, optional URI parameters and default values). |
| LicenseUrl | http://www.apache.org/licenses/LICENSE-2.0 |
| Owners | Arjen Post |
| ProjectUrl | https://github.com/dotarj/FluentRouting |
| RequireLicenseAcceptance | False |
| Tags | AspNet Mvc AspNetMvc Fluent Routing |
| Dependencies | Microsoft.AspNet.Mvc:5.0.0 |
| Title | ASP.NET MVC Fluent Routing |
| PackageSize | 33017 |
| PackageHashAlgorithm | SHA512 |
| PackageHash | 1E7OyEVatRfTziL3JBGGCEY1dM6K0Awi7E1FOF2qjCsbLGSSPy+XuO4H3nS641JvmUBZhXLE+I3cH+cn3YSgvA== |
| DownloadCount | 000000 |
| CreatedDate | 2014-01-30T19:36:01 |
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 FluentRouting.Mvc -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install FluentRouting.Mvc -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 FluentRouting.Mvc
- Installing the package (HTTP Basic authentication):
-
Install-Package FluentRouting.Mvc -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package FluentRouting.Mvc -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package FluentRouting.Mvc
OpenWrap
- Installing the package:
-
o add-wrap FluentRouting.Mvc
- Uninstalling the package:
-
o remove-wrap FluentRouting.Mvc
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.