Book Image

Mastering ABP Framework

By : Halil İbrahim Kalkan
Book Image

Mastering ABP Framework

By: Halil İbrahim Kalkan

Overview of this book

ABP Framework is a complete infrastructure for creating modern web applications by following software development best practices and conventions. With ABP's high-level framework and ecosystem, you can implement the Don’t Repeat Yourself (DRY) principle and focus on your business code. Written by the creator of ABP Framework, this book will help you to gain a complete understanding of the framework and modern web application development techniques. With step-by-step explanations of essential concepts and practical examples, you'll understand the requirements of a modern web solution and how ABP Framework makes it enjoyable to develop your own solutions. You'll discover the common requirements of enterprise web application development and explore the infrastructure provided by ABP. Throughout the book, you’ll get to grips with software development best practices for building maintainable and modular web solutions. By the end of this book, you'll be able to create a complete web solution that is easy to develop, maintain, and test.
Table of Contents (24 chapters)
1
Part 1: Introduction
6
Part 2: Fundamentals of ABP Framework
11
Part 3: Implementing Domain–Driven Design
15
Part 4: User Interface and API Development
19
Part 5: Miscellaneous

Installing the Payment module into EventHub

A module itself is not a runnable project. It should be installed into a larger application and work as part of it. In this section, we will see how the Payment module is installed in the EventHub solution.

Setting the project dependencies

The Payment module consists of more than 10 projects in its solution (see Figure 15.3). Similarly, the EventHub solution has a lot of projects with three applications – the admin-side, the public, and the account (IdentityServer) applications.

I want to integrate the Payment module into the EventHub solution in all layers. Typically, each layer of the EventHub solution should depend on (use) the corresponding layer of the Payment module. The following table shows all the dependencies of the EventHub projects to the Payment module projects:

Figure 15.9 – EventHub and Payment module project dependencies

So, we should add project references one by one. For example...