Microsoft.AspNetCore.Mvc 2.1.2
ASP.NET Core MVC is a web framework that gives you a powerful, patterns-based way to build dynamic websites and web APIs. ASP.NET Core MVC enables a clean separation of concerns and gives you full control over markup.
Showing the top 20 packages that depend on Microsoft.AspNetCore.Mvc.
| Packages | Downloads |
|---|---|
|
AspNetCoreRateLimit
ASP.NET Core rate limiting middleware
|
7 |
|
FluentValidation.AspNetCore
AspNetCore integration for FluentValidation
|
6 |
|
FluentValidation.AspNetCore
AspNetCore integration for FluentValidation
|
7 |
|
FluentValidation.AspNetCore
AspNetCore integration for FluentValidation
|
8 |
|
Microsoft.AspNetCore.All
Microsoft.AspNetCore.All
|
6 |
|
Microsoft.AspNetCore.All
Provides a default set of APIs for building an ASP.NET Core application, and also includes API for third-party integrations with ASP.NET Core.
This package requires the ASP.NET Core runtime. This runtime is installed by the .NET Core SDK, or can be acquired separately using installers available at https://aka.ms/dotnet-download.
|
7 |
|
Microsoft.AspNetCore.App
Provides a default set of APIs for building an ASP.NET Core application.
This package requires the ASP.NET Core runtime. This runtime is installed by the .NET Core SDK, or can be acquired separately using installers available at https://aka.ms/dotnet-download.
|
7 |
|
Microsoft.AspNetCore.App
Provides a default set of APIs for building an ASP.NET Core application.
This package requires the ASP.NET Core runtime. This runtime is installed by the .NET Core SDK, or can be acquired separately using installers available at https://aka.ms/dotnet-download.
|
9 |
|
Microsoft.AspNetCore.Identity.Service.Mvc
ASP.NET Core Identity Service integration for ASP.NET Core MVC.
|
8 |
|
Microsoft.AspNetCore.Mvc.Versioning
A service API versioning library for Microsoft ASP.NET Core.
|
8 |
|
Ocelot
Ocelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
7 |
|
Ocelot
Ocelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
13 |
|
Ocelot
This project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
6 |
|
Ocelot
This project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
11 |
|
Senparc.NeuChar.AspNet
NeuChar SDK 跨平台信息交互标准
|
20 |
|
Senparc.Weixin.AspNet
微信公众账号 - Senparc.Weixin.AspNet 模块
Senparc.Weixin SDK 开源项目：
https://github.com/JeffreySu/WeiXinMPSDK
|
7 |
|
Swashbuckle.AspNetCore.Swagger
Middleware to expose Swagger JSON endpoints from API's built on ASP.NET Core
|
8 |
|
Volo.Abp.AspNetCore.Mvc
Package Description
|
8 |
.NET Standard 2.0
- Microsoft.AspNetCore.Mvc.ApiExplorer (>= 2.1.2)
- Microsoft.AspNetCore.Mvc.Cors (>= 2.1.2)
- Microsoft.AspNetCore.Mvc.DataAnnotations (>= 2.1.2)
- Microsoft.AspNetCore.Mvc.Formatters.Json (>= 2.1.2)
- Microsoft.AspNetCore.Mvc.Localization (>= 2.1.2)
- Microsoft.AspNetCore.Mvc.RazorPages (>= 2.1.2)
- Microsoft.AspNetCore.Mvc.TagHelpers (>= 2.1.2)
- Microsoft.AspNetCore.Mvc.ViewFeatures (>= 2.1.2)
- Microsoft.AspNetCore.Mvc.Razor.Extensions (>= 2.1.1)
- Microsoft.AspNetCore.Razor.Design (>= 2.1.1)
- Microsoft.Extensions.Caching.Memory (>= 2.1.1)
- Microsoft.Extensions.DependencyInjection (>= 2.1.1)