csharp-abp-study/Skcks.Study.AbpProject
2024-11-22 22:33:59 +08:00
..
etc/abp-studio/run-profiles 保存项目 2024-11-22 22:33:59 +08:00
src 保存项目 2024-11-22 22:33:59 +08:00
test 保存项目 2024-11-22 22:33:59 +08:00
.editorconfig 保存项目 2024-11-22 22:33:59 +08:00
.gitattributes 保存项目 2024-11-22 22:33:59 +08:00
.gitignore 保存项目 2024-11-22 22:33:59 +08:00
common.props 保存项目 2024-11-22 22:33:59 +08:00
NuGet.Config 保存项目 2024-11-22 22:33:59 +08:00
README.md 保存项目 2024-11-22 22:33:59 +08:00
Skcks.Study.AbpProject.abpmdl 保存项目 2024-11-22 22:33:59 +08:00
Skcks.Study.AbpProject.abpsln 保存项目 2024-11-22 22:33:59 +08:00
Skcks.Study.AbpProject.sln 保存项目 2024-11-22 22:33:59 +08:00
Skcks.Study.AbpProject.sln.DotSettings 保存项目 2024-11-22 22:33:59 +08:00

Skcks.Study.AbpProject

About this solution

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.

Pre-requirements

Configurations

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 ConnectionStrings in appsettings.json files under the Skcks.Study.AbpProject.Web and Skcks.Study.AbpProject.DbMigrator projects and change it if you need. **

Before running the application

  • Run abp install-libs command 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 Skcks.Study.AbpProject.DbMigrator to 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.

Generating a Signing Certificate

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 a41bb421-ee8b-4e36-9929-de417304951f

a41bb421-ee8b-4e36-9929-de417304951f is 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: https://documentation.openiddict.com/configuration/encryption-and-signing-credentials.html#registering-a-certificate-recommended-for-production-ready-scenarios

Also, see the Configuring OpenIddict documentation for more information.

Solution structure

This is a layered monolith application that consists of the following applications:

  • Skcks.Study.AbpProject.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. ** Skcks.Study.AbpProject.Web: ASP.NET Core MVC / Razor Pages application that is the essential web application of the solution.

Deploying the application

Deploying an ABP application is not different than deploying any .NET or ASP.NET Core application. However, there are some topics that you should care about when you are deploying your applications. You can check ABP's Deployment documentation and ABP Commercial's Deployment documentation before deploying your application.

Additional resources

You can see the following resources to learn more about your solution and the ABP Framework: