An Abp Blazor Theme based Ant-Design-Blazor
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
liangshiwei 68478c7c29 Add new BlazorWebassembly example 7 months ago
..
etc/abp-studio/run-profiles Add new BlazorWebassembly example 7 months ago
src Add new BlazorWebassembly example 7 months ago
test Add new BlazorWebassembly example 7 months ago
.editorconfig Add new BlazorWebassembly example 7 months ago
.gitattributes Add new BlazorWebassembly example 7 months ago
.gitignore Add new BlazorWebassembly example 7 months ago
BookStore.abpmdl Add new BlazorWebassembly example 7 months ago
BookStore.abpsln Add new BlazorWebassembly example 7 months ago
BookStore.sln Add new BlazorWebassembly example 7 months ago
BookStore.sln.DotSettings Add new BlazorWebassembly example 7 months ago
NuGet.Config Add new BlazorWebassembly example 7 months ago
README.md Add new BlazorWebassembly example 7 months ago
common.props Add new BlazorWebassembly example 7 months ago

README.md

BookStore

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 BookStore.HttpApi.Host and BookStore.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 BookStore.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 2dae3a4f-9e73-4cb7-b7b9-7ec95c44e1a3

2dae3a4f-9e73-4cb7-b7b9-7ec95c44e1a3 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: OpenIddict Certificate Configuration

Also, see the Configuring OpenIddict documentation for more information.

Solution structure

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

  • BookStore.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.
  • BookStore.HttpApi.Host: ASP.NET Core API application that is used to expose the APIs to the clients.
  • BookStore.Blazor: ASP.NET Core Blazor Server application that is the essential web application of the solution.

Deploying the application

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.

Additional resources

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