IVP.Notification
1.0.6
See the version list below for details.
dotnet add package IVP.Notification --version 1.0.6
NuGet\Install-Package IVP.Notification -Version 1.0.6
<PackageReference Include="IVP.Notification" Version="1.0.6" />
paket add IVP.Notification --version 1.0.6
#r "nuget: IVP.Notification, 1.0.6"
// Install IVP.Notification as a Cake Addin #addin nuget:?package=IVP.Notification&version=1.0.6 // Install IVP.Notification as a Cake Tool #tool nuget:?package=IVP.Notification&version=1.0.6
IVP.Notification
About this solution
This is a minimalist, non-layered startup solution with the ABP Framework. All the fundamental ABP modules are already installed.
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
inappsettings.json
files under theIVP.Notification
project and change it if you need.
Before running the application
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.
This certificate is already generated by ABP CLI, so most of the time you don't need to generate it yourself. However, if you need to generate a certificate, you can use the following command:
dotnet dev-certs https -v -ep openiddict.pfx -p bb33a2bf-b73e-410e-9812-be3f5dc4b386
bb33a2bf-b73e-410e-9812-be3f5dc4b386
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.
Install Client-Side Libraries
Run the following command in the directory of your final application:
abp install-libs
This command installs all NPM packages for MVC/Razor Pages and Blazor Server UIs and this command is already run by the ABP CLI, so most of the time you don't need to run this command manually.
How to Run
The application needs to connect to a database. Run the following command in the IVP.Notification
directory to migrate the database and seed the initial data:
dotnet run --migrate-database
This command will create and seed the initial database. Then you can run the application with any IDE that supports .NET.
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 before deploying your application.
Additional resources
You can see the following resources to learn more about your solution and the ABP Framework:
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net8.0
- Microsoft.AspNetCore.Authentication.JwtBearer (>= 8.0.0)
- Microsoft.Extensions.DependencyInjection (>= 8.0.0)
- Serilog.AspNetCore (>= 8.0.0)
- Serilog.Settings.Configuration (>= 8.0.0)
- Serilog.Sinks.Async (>= 1.5.0)
- Serilog.Sinks.Seq (>= 5.2.2)
- Volo.Abp.AspNetCore.Mvc (>= 8.0.1)
- Volo.Abp.AspNetCore.SignalR (>= 8.0.1)
- Volo.Abp.Autofac (>= 8.0.1)
- Volo.Abp.AutoMapper (>= 8.0.1)
- Volo.Abp.EntityFrameworkCore (>= 8.0.1)
- Volo.Abp.EntityFrameworkCore.PostgreSql (>= 8.0.1)
- Volo.Abp.Http.Client (>= 8.0.1)
- Volo.Abp.Swashbuckle (>= 8.0.1)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.