Register out-of-the-box framework services.Ĭ.UseSqlServer(Configuration), Public void ConfigureServices(IServiceCollection services)
Masstransit mediatr registration#
When you use the built-in IoC container provided by ASP.NET Core, you register the types you want to inject in the ConfigureServices method in the Startup.cs file, as in the following code: // Registration of types into ASP.NET Core built-in container
(Like DI based on the constructor, as shown previously.) Use the built-in IoC container provided by ASP.NET Core Register the dependency implementation types and interfaces or abstractionsīefore you use the objects injected through constructors, you need to know where to register the interfaces and classes that produce the objects injected into your application classes through DI. Dependency Injection works the same way for all the mentioned classes, as in the example using DI based on the constructor. It is ultimately a simple class that uses repositories, domain entities, and other application coordination in a fashion similar to a command handler. It does not matter whether that class is a command handler, an ASP.NET Core Web API controller method, or a DDD Application Service. The class uses the injected repositories to execute the transaction and persist the state changes. _logger.LogInformation("- Creating Order - Order: order) Order.AddOrderItem(item.ProductId, item.ProductName, item.UnitPrice, item.Discount, item.PictureUrl, item.Units) Var order = new Order(message.UserId, message.UserName, address, message.CardTypeId, message.CardNumber, message.CardSecurityNumber, message.CardHolderName, message.CardExpiration) Var address = new Address(message.Street, message.City, message.State, message.Country, message.ZipCode) make sure that consistency is preserved across the whole aggregate methods and constructor so validations, invariants and business logic DDD patterns comment: Add child entities and value-objects through the Order Aggregate-Root Var orderStartedIntegrationEvent = new OrderStartedIntegrationEvent(message.UserId) Īwait _orderingIntegrationEventService.AddAndSaveEventAsync(orderStartedIntegrationEvent) Add Integration event to clean the basket Public async Task Handle(CreateOrderCommand message, CancellationToken cancellationToken) _logger = logger ? throw new ArgumentNullException(nameof(logger)) _orderingIntegrationEventService = orderingIntegrationEventService ? throw new ArgumentNullException(nameof(orderingIntegrationEventService)) _mediator = mediator ? throw new ArgumentNullException(nameof(mediator)) _identityService = identityService ? throw new ArgumentNullException(nameof(identityService)) _orderRepository = orderRepository ? throw new ArgumentNullException(nameof(orderRepository))
IOrderingIntegrationEventService orderingIntegrationEventService, Public CreateOrderCommandHandler(IMediator mediator, Using DI to inject infrastructure persistence Repositories Private readonly IOrderingIntegrationEventService _orderingIntegrationEventService Private readonly IIdentityService _identityService Private readonly IOrderRepository _orderRepository The class is a command handler, which will get covered in the next section. NET is injecting the required repository objects through the constructor. In the following example, you can see how. For simpler implementations, you could directly inject your Unit of Work pattern object (the EF DbContext object), because the DBContext is also the implementation of your infrastructure persistence objects. But you could inject any other infrastructure dependency that you may have. A typical dependency to inject is a repository. Typically, you want to inject dependencies that implement infrastructure objects. Your dependencies are implemented in the services that a type needs and that you register in the IoC container. You configure the built-in container's services in the ConfigureServices method in your application's Startup class. ASP.NET Core uses the term service for any of the types you register that will be injected through DI. The application layer in the Ordering.API ASP.NET Core Web API projectĪSP.NET Core includes a simple built-in IoC container (represented by the IServiceProvider interface) that supports constructor injection by default, and ASP.NET makes certain services available through DI. The Solution Explorer view of the Ordering.API microservice, showing the subfolders under the Application folder: Behaviors, Commands, DomainEventHandlers, IntegrationEvents, Models, Queries, and Validations.įigure 7-23.
0 kommentar(er)
