This is a layered startup solution based on Domain Driven Design (DDD) practises. All the fundamental ABP modules are already installed. Check the Application Startup Template documentation for more info.
The solution comes with a default configuration that works out of the box. However, you may consider to change the following configuration before running your solution:
- Check the
ConnectionStringsinappsettings.jsonfiles under theSampleTesting1.WebandSampleTesting1.DbMigratorprojects and change it if you need. - Check the
ConnectionStringsinappsettings.jsonfiles under theSampleTesting1.Web.Publicas well.
- Run
abp install-libscommand on your solution folder to install client-side package dependencies. This step is automatically done when you create a new solution, if you didn't especially disabled it. However, you should run it yourself if you have first cloned this solution from your source control, or added a new client-side package dependency to your solution. - Run
SampleTesting1.DbMigratorto create the initial database. This step is also automatically done when you create a new solution, if you didn't especially disabled it. This should be done in the first run. It is also needed if a new database migration is added to the solution later.
In the production environment, you need to use a production signing certificate. ABP Framework sets up signing and encryption certificates in your application and expects an openiddict.pfx file in your application.
To generate a signing certificate, you can use the following command:
dotnet dev-certs https -v -ep openiddict.pfx -p d62add3d-b6ae-4bb3-b1cc-a5077ee4ff97
d62add3d-b6ae-4bb3-b1cc-a5077ee4ff97is the password of the certificate, you can change it to any password you want.
It is recommended to use two RSA certificates, distinct from the certificate(s) used for HTTPS: one for encryption, one for signing.
For more information, please refer to: OpenIddict Certificate Configuration
Also, see the Configuring OpenIddict documentation for more information.
This is a layered monolith application that consists of the following applications:
SampleTesting1.DbMigrator: A console application which applies the migrations and also seeds the initial data. It is useful on development as well as on production environment.SampleTesting1.Web: ASP.NET Core MVC / Razor Pages application that is the essential web application of the solution.SampleTesting1.Web.Public: ASP.NET Core MVC / Razor Pages application that is the public web application of the solution.
Deploying an ABP application follows the same process as deploying any .NET or ASP.NET Core application. However, there are important considerations to keep in mind. For detailed guidance, refer to ABP's deployment documentation.
You can find detailed setup and configuration guide(s) for your solution below:
You can see the following resources to learn more about your solution and the ABP Framework: