Resina.NotificationManagement.HttpApi.Client
0.1.2
See the version list below for details.
dotnet add package Resina.NotificationManagement.HttpApi.Client --version 0.1.2
NuGet\Install-Package Resina.NotificationManagement.HttpApi.Client -Version 0.1.2
<PackageReference Include="Resina.NotificationManagement.HttpApi.Client" Version="0.1.2" />
paket add Resina.NotificationManagement.HttpApi.Client --version 0.1.2
#r "nuget: Resina.NotificationManagement.HttpApi.Client, 0.1.2"
// Install Resina.NotificationManagement.HttpApi.Client as a Cake Addin #addin nuget:?package=Resina.NotificationManagement.HttpApi.Client&version=0.1.2 // Install Resina.NotificationManagement.HttpApi.Client as a Cake Tool #tool nuget:?package=Resina.NotificationManagement.HttpApi.Client&version=0.1.2
Resina.ModuleManagement
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
inappsettings.json
files under theResina.ModuleManagement.Web
andResina.ModuleManagement.DbMigrator
projects 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 aed72707-6686-44b4-a9a6-54701364d1f1
aed72707-6686-44b4-a9a6-54701364d1f1
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.
Create the Database
Run Resina.ModuleManagement.DbMigrator
to create the initial database. This should be done in the first run. It is also needed if a new database migration is added to the solution later.
Solution structure
This is a layered monolith application that consists of the following applications:
Resina.ModuleManagement.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.Resina.ModuleManagement.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:
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. 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. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 is compatible. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Resina.NotificationManagement.Application.Contracts (>= 0.1.2)
- Volo.Abp.Http.Client (>= 8.1.3)
-
.NETStandard 2.1
- Resina.NotificationManagement.Application.Contracts (>= 0.1.2)
- Volo.Abp.Http.Client (>= 8.1.3)
-
net8.0
- Resina.NotificationManagement.Application.Contracts (>= 0.1.2)
- Volo.Abp.Http.Client (>= 8.1.3)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Resina.NotificationManagement Preview