5 Factors to Consider When Converting a WebForms App to ASP.NET MVC Core
با توجه به یکی بودن کنترلرهای Web API و MVC در ASP.NET Core، تعاریف مسیریابی آن‌ها با نکاتی در این مطلب عنوان شد، هیچ تفاوتی ندارد.
قصد پشتیبانی از ASP.NET Core Identity را به طوری که مدنظر شما می‌باشد، ندارم.
مطالب تکمیلی مرتبط با روشی که قصد پشتیبانی از آن را دارم:
اشتراک‌ها
نمونه مثالی از ASP.NET Core و Entity Framework Core به همراه معماری DDD و CQRS و Event Sourcing
Full ASP.NET Core 2.2 application with DDD, CQRS and Event Sourcing
Technologies implemented:
- ASP.NET Core 2.2 (with .NET Core 2.2)
- ASP.NET MVC Core
- ASP.NET WebApi Core
- ASP.NET Identity Core
- Entity Framework Core 2.2
- .NET Core Native DI
- AutoMapper
- FluentValidator
- MediatR
- Swagger UI
Architecture:
- Full architecture with responsibility separation concerns, SOLID and Clean Code
- Domain Driven Design (Layers and Domain Model Pattern)
- Domain Events
- Domain Notification
- CQRS (Imediate Consistency)
- Event Sourcing
- Unit of Work
- Repository and Generic Repository
Structured data in earlier versions of ASP.NET meant creating and registering custom types and configuration sections for our applications. In ASP.NET Core and in Core MVC, structured configuration is a breeze with support for JSON documents as the storage mechanism and the ability to flatten hierarchies into highly portable keys.
Razor Pages is a new feature of ASP.NET Core MVC that makes coding page-focused scenarios easier and more productive.
Razor Pages requires ASP.NET Core 2.0.0 or later. Tooling support for Razor Pages ships in Visual Studio 2017 Update 3 or later.
Audio calling for one to one peer using signaling server as SignalR Core with ASP.NET Core 3.1 and WebRTC
Lynicon CMS for ASP.Net Core (.Net Standard 1.6, .Net 4.6). Now we believe the most powerful CMS on .Net Core.
ASP.NET Core InProcess Hosting on IIS with ASP.NET Core 2.2
