diff --git a/.gitignore b/.gitignore
index 2f820efc4d..f3f48c5963 100644
--- a/.gitignore
+++ b/.gitignore
@@ -271,6 +271,7 @@ modules/blogging/app/Volo.BloggingTestApp/wwwroot/files/*.*
modules/docs/app/VoloDocs.Web/Logs/*.*
modules/setting-management/app/Volo.Abp.SettingManagement.DemoApp/Logs/*.*
templates/module/app/MyCompanyName.MyProjectName.DemoApp/Logs/*.*
+templates/module/aspnet-core/host/MyCompanyName.MyProjectName.Blazor.Server.Host/Logs/logs.txt
templates/mvc/src/MyCompanyName.MyProjectName.Web/Logs/*.*
@@ -313,4 +314,4 @@ abp-build-config.json
tempkey.jwk
# ABP Analyzing files
-*.abppkg.analyze.json
\ No newline at end of file
+*.abppkg.analyze.json
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en-GB.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en-GB.json
index 970e04d24e..4ea99af7e1 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en-GB.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en-GB.json
@@ -197,6 +197,19 @@
"RemoveCache": "Remove Cache",
"Language": "Language",
"Optional": "Optional",
- "CreateArticleLanguageInfo": "The language in which the article is written"
+ "CreateArticleLanguageInfo": "The language in which the article is written",
+ "Menu:Quotation": "Quotation",
+ "Menu:Invoice": "Invoice",
+ "Menu:PaymentRequests": "Payment Requests",
+ "Permission:PaymentRequests": "Payment Requests",
+ "PaymentRequests": "Payment Requests",
+ "Creator": "Creator",
+ "ExtraProperties": "Extra Properties",
+ "Organization": "Organization",
+ "Waiting": "Waiting",
+ "Completed": "Completed",
+ "Failed": "Failed",
+ "PaymentRequestDeletionWarningMessage": "This payment request will be deleted. Do you confirm that?",
+ "Payment": "Payment"
}
}
\ No newline at end of file
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en.json
index 0cfd2a477a..bbfcb08e18 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en.json
@@ -277,6 +277,19 @@
"ThisExtensionIsNotAllowed": "This extension is not allowed.",
"TheFileIsTooLarge": "The file is too large!",
"ArticleDeletionConfirmationMessage": "Are you sure you want to hard delete this article?",
- "ChooseCoverImage": "Choose a cover image..."
+ "ChooseCoverImage": "Choose a cover image...",
+ "Menu:Quotation": "Quotation",
+ "Menu:Invoice": "Invoice",
+ "Menu:PaymentRequests": "Payment Requests",
+ "Permission:PaymentRequests": "Payment Requests",
+ "PaymentRequests": "Payment Requests",
+ "Creator": "Creator",
+ "ExtraProperties": "Extra Properties",
+ "Organization": "Organization",
+ "Waiting": "Waiting",
+ "Completed": "Completed",
+ "Failed": "Failed",
+ "PaymentRequestDeletionWarningMessage": "This payment request will be deleted. Do you confirm that?",
+ "Payment": "Payment"
}
}
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/tr.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/tr.json
index c1253db259..19e81c5788 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/tr.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/tr.json
@@ -227,6 +227,19 @@
"TheFileIsTooLarge": "Dosya çok büyük.",
"ArticleDeletionConfirmationMessage": "Bu makaleyi kalıcı olarak silmek istediğinizden emin misiniz?",
"ChooseCoverImage": "Bir kapak resmi seçin...",
- "CoverImage": "Kapak Resmi"
+ "CoverImage": "Kapak Resmi",
+ "Menu:Quotation": "Fiyatlandırma",
+ "Menu:Invoice": "Fatura",
+ "Menu:PaymentRequests": "Ödeme İstekleri",
+ "Permission:PaymentRequests": "Ödeme İstekleri",
+ "PaymentRequests": "Ödeme İstekleri",
+ "Creator": "Oluşturan",
+ "ExtraProperties": "Ekstra Özellikler",
+ "Organization": "Organizasyon",
+ "Waiting": "Bekliyor",
+ "Completed": "Tamamlandı",
+ "Failed": "Başarısız Oldu",
+ "PaymentRequestDeletionWarningMessage": "Bu ödeme isteği silinecek. Bunu onaylıyor musun?",
+ "Payment": "Ödeme"
}
}
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en-GB.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en-GB.json
index 82ffbf0f4c..442384bd0a 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en-GB.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en-GB.json
@@ -32,6 +32,7 @@
"SeeDocuments": "See Documents",
"Samples": "Samples",
"FreeDDDBook": "Free DDD E-book",
- "New": "New"
+ "New": "New",
+ "Volo.AbpIo.Domain:020005": "License extend year can not be lower than {MinExtendLicenseYear} year and greater than {MaxExtendLicenseYear} years "
}
}
\ No newline at end of file
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en.json
index 646c2f9648..b9c8d23563 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en.json
@@ -34,6 +34,7 @@
"Framework": "Framework",
"Support": "Support",
"FreeDDDBook": "Free DDD E-book",
- "New": "New"
+ "New": "New",
+ "Volo.AbpIo.Domain:020005": "License extend year can not be lower than {MinExtendLicenseYear} year and greater than {MaxExtendLicenseYear} years "
}
}
\ No newline at end of file
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/hi.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/hi.json
index cd1ec4491d..5096d3cbe7 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/hi.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/hi.json
@@ -11,8 +11,8 @@
"Volo.AbpIo.Domain:010011": "व्यक्तिगत लाइसेंस में 1 से अधिक डेवलपर नहीं हो सकते हैं!",
"Volo.AbpIo.Domain:010012": "लाइसेंस की अवधि समाप्त होने के एक महीने बाद तक लाइसेंस नहीं बढ़ाया जा सकता है!",
"Volo.AbpIo.Domain:020001": "इस NPM पैकेज को नहीं हटाया जा सका क्योंकि \"{NugetPackages}\" नुगेट पैकेज इस पैकेज पर निर्भर हैं।",
- "Volo.AbpIo.Domain:020002": "यह NPM पैकेज नहीं हटा सका क्योंकि \"{मॉड्यूल}\" मॉड्यूल इस पैकेज का उपयोग कर रहे हैं।",
- "Volo.AbpIo.Domain:020003": "इस NPM पैकेज को नहीं हटाया जा सका क्योंकि \"{मॉड्यूल}\" मॉड्यूल इस पैकेज का उपयोग कर रहे हैं और \"{NugetPackages}\" नुगेट पैकेज इस पैकेज पर निर्भर हैं।",
+ "Volo.AbpIo.Domain:020002": "यह NPM पैकेज नहीं हटा सका क्योंकि \"{Modules}\" मॉड्यूल इस पैकेज का उपयोग कर रहे हैं।",
+ "Volo.AbpIo.Domain:020003": "इस NPM पैकेज को नहीं हटाया जा सका क्योंकि \"{Modules}\" मॉड्यूल इस पैकेज का उपयोग कर रहे हैं और \"{NugetPackages}\" नुगेट पैकेज इस पैकेज पर निर्भर हैं।",
"Volo.AbpIo.Domain:020004": "इस Nuget पैकेज को हटाया नहीं जा सका क्योंकि \"{Modules}\" मॉड्यूल इस पैकेज का उपयोग कर रहे हैं।",
"WantToLearn?": "सीखना चाहते है?",
"ReadyToGetStarted?": "आरंभ करने के लिए तैयार हैं?",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/tr.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/tr.json
index 2f932f299b..04c114a6c2 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/tr.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/tr.json
@@ -28,6 +28,7 @@
"Commercial": "Ticari",
"SeeDocuments": "Dokümanlara Göz Atın",
"FreeDDDBook": "Ücretsiz DDD Kitabı",
- "New": "Yeni"
+ "New": "Yeni",
+ "Volo.AbpIo.Domain:020005": "Lisans uzatma yılı {MinExtendLicenseYear} yıldan az {MaxExtendLicenseYear} yıldan fazla olamaz."
}
}
\ No newline at end of file
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/en-GB.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/en-GB.json
index 0694811b78..af20ee9ba7 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/en-GB.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/en-GB.json
@@ -100,6 +100,7 @@
"VolosoftSharingInformationMessage": "I would like Volosoft to share my information with select partners so I can receive relevant information about their products and services.",
"WeWillSendYouADownloadLink": "We've sent the file to {0}.",
"InvalidFormInputs": "Please, type the valid information specified on the form.",
- "DDDBookEmailBody": "Thank you. To download your book, click here."
+ "DDDBookEmailBody": "Thank you. To download your book, click here.",
+ "FreeDDDEBook": "Free DDD E-Book"
}
}
\ No newline at end of file
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/en.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/en.json
index d7f9f3c651..58e4b561d6 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/en.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/en.json
@@ -357,6 +357,7 @@
"VolosoftSharingInformationMessage": "I would like Volosoft to share my information with select partners so I can receive relevant information about their products and services.",
"WeWillSendYouADownloadLink": "A link to download the e-book has been sent to {0}. Check your inbox / junk / spam boxes!",
"InvalidFormInputs": "Please, type the valid information specified on the form.",
- "DDDBookEmailBody": "Thank you. To download your book, click here."
+ "DDDBookEmailBody": "Thank you. To download your book, click here.",
+ "FreeDDDEBook": "Free DDD E-Book"
}
}
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/fi.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/fi.json
index b2da832b2a..317ace31b5 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/fi.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/fi.json
@@ -151,7 +151,7 @@
"SeeAllModules": "Katso kaikki moduulit",
"ABPCLIExplanation": "ABP CLI (Command Line Interface) on komentorivityökalu joidenkin yleisten toimintojen suorittamiseen ABP-pohjaisiin ratkaisuihin.",
"ABPSuiteEasilyCURD": "ABP Suite on työkalu, jonka avulla voit helposti luoda CRUD-sivuja",
- "WeAreHereToHelp": " Apua olemme täällä",
+ "WeAreHereToHelp": "Apua olemme täällä",
"BrowseOrAskQuestion": "Voit selata ohjeaiheitamme tai etsiä usein kysyttyjä kysymyksiä tai voit esittää meille kysymyksiä yhteydenottolomakkeella .",
"SearchQuestionPlaceholder": "Hae usein kysyttyjä kysymyksiä",
"WhatIsTheABPCommercial": "Mikä on ABP-kauppa?",
@@ -177,7 +177,7 @@
"ChangingLicenseType": "Voinko muuttaa lisenssityyppiäni tulevaisuudessa?",
"ChangingLicenseTypeExplanation": "Voit aina lisätä uusia kehittäjiä samaan lisenssityyppiin. Katso myös \"Kuinka monta kehittäjää voi työskennellä ABP Commercialilla?\". Voit myös päivittää korkeampaan lisenssiin maksamalla lasketun hintaeron. Kun päivität korkeampaan lisenssisuunnitelmaan, saat uuden suunnitelman edut, mutta lisenssin päivitys ei muuta lisenssin voimassaolon päättymispäivää.",
"LicenseExtendUpgradeDiff": "Mitä eroa on lisenssin laajennuksella ja päivityksellä?",
- "LicenseExtendUpgradeDiffExplanation": " Laajentaminen: Laajentamalla / uusimalla käyttöoikeutta saat jatkossakin ensiluokkaista tukea ja saat tärkeitä päivityksiä moduuleille ja teemoille. Lisäksi voit jatkaa uusien projektien luomista. Ja voit silti käyttää ABP Suitea, joka vauhdittaa kehitystäsi.
Päivittäminen: Päivittämällä lisenssisi edistyt korkeampaan lisenssisuunnitelmaan, jonka avulla voit saada lisäetuja . Katso lisenssisuunnitelmien väliset erot lisenssien vertailutaulukosta . Toisaalta, kun päivität, lisenssin vanhentumispäivä ei muutu! Strong > Lisenssin päättymispäivän jatkamiseksi sinun on jatkettava käyttöoikeutta.",
+ "LicenseExtendUpgradeDiffExplanation": " Extension: en prolongeant/renouvelant votre licence, vous continuerez à bénéficier d'une assistance premium et à des mises à jour majeures pour les modules et les thèmes. De plus, vous pourrez continuer à créer de nouveaux projets. Et vous pourrez toujours utiliser ABP Suite, ce qui accélère votre développement. Mise à niveau: En mettant à jour votre licence, vous passerez à un plan de licence supérieur qui vous permettra d’obtenir des avantages supplémentaires . Consultez le tableau de comparaison des licences pour vérifier les différences entre les plans de licence. En revanche, lors de la mise à niveau, la date d'expiration de votre licence ne changera pas! Pour prolonger la date de fin de votre licence, vous devez prolonger votre licence.",
"LicenseRenewalCost": "Mitkä ovat lisenssin uusimiskustannukset vuoden kuluttua?",
"LicenseRenewalCostExplanation": "Kaikkien ABP Commercial perpetual -lisenssien uusimis- (laajennus) hinta on {0} lisenssiluettelohinnasta. Tavallisen tiimilisenssin uusimishinta on $ {1}, tavallinen yrityslisenssi on $ {2} ja tavallinen yrityslisenssi on $ {3}. Jos olet jo asiakas, kirjaudu tilillesi ja tarkista käytettävissä oleva uusimishinta.",
"HowDoIRenewMyLicense": "Kuinka uusin lisenssin?",
@@ -230,7 +230,7 @@
"HowCanIRefundVatExplanation2": "Kirjaudu sisään 2Tarkista -tiliisi.",
"HowCanIRefundVatExplanation3": "Etsi sopiva tilaus ja paina \"Hyvitä myöhässä oleva alv\" (kirjoita ALV-tunnuksesi)",
"HowCanIGetMyInvoice": "Kuinka saan laskuni?",
- "HowCanIGetMyInvoiceExplanation": "Lisenssin ostamiseen on 2 maksuyhdyskäytävää: PayU ja 2Checkout. Jos ostat lisenssin 2Checkout gatewayn kautta, se lähettää PDF-laskun sähköpostiosoitteeseesi, katso 2Tarkista laskutus. Jos ostat PayU-yhdyskäytävän kautta tai pankkisiirrolla, valmistelemme ja lähetämme laskusi. Voit pyytää laskua organisaation hallintasivulta ",
+ "HowCanIGetMyInvoiceExplanation": "Lisenssin ostamiseen on 2 maksuyhdyskäytävää: PayU ja 2Checkout. Jos ostat lisenssin 2Checkout gatewayn kautta, se lähettää PDF-laskun sähköpostiosoitteeseesi, katso 2Tarkista laskutus. Jos ostat PayU-yhdyskäytävän kautta tai pankkisiirrolla, valmistelemme ja lähetämme laskusi. Voit pyytää laskua organisaation hallintasivulta ",
"Forum": "Foorumi",
"SupportExplanation": "ABP Commercial -lisenssit tarjoavat ensiluokkaisen foorumituen ABP-kehyksen asiantuntijoista koostuvalle tiimille.",
"PrivateTicket": "Yksityinen lippu",
@@ -240,7 +240,7 @@
"FastEasy": "Nopea ja helppo",
"AbpSuiteExplanation3": "ABP Suiten avulla voit luoda helposti CRUD-sivuja. Sinun tarvitsee vain määritellä entiteetti ja sen ominaisuudet, antaa loput ABP Suiten puolestasi! ABP Suite luo kaikki tarvittavat koodit CRUD-sivullesi muutamassa sekunnissa. Se tukee Angular-, MVC- ja Blazor-käyttöliittymiä.",
"RichOptions": "Monipuoliset vaihtoehdot",
- "AbpSuiteExplanation4": "ABP Suite tukee useita käyttöliittymävaihtoehtoja, kuten Razor Pages ja Kulma .Se tukee myös useita tietokantoja, kuten MongoDB ja kaikkia EntityFramework Core <: n tukemia tietokantoja. / strong> (MS SQL Server, Oracle, MySql, PostgreSQL ja lisää ).",
+ "AbpSuiteExplanation4": "ABP Suite supports multiple UI options like Razor Pages and Angular.It also supports multiple databases like MongoDB and all databases supported by EntityFramework Core (MS SQL Server, Oracle, MySql, PostgreSQL and more).",
"AbpSuiteExplanation5": "Hyvä asia on, että sinun ei tarvitse huolehtia näistä vaihtoehdoista. ABP Suite ymmärtää projektisi tyypin ja luo koodin projektillesi ja sijoittaa luodun koodin oikeaan paikkaan projektissasi.",
"SourceCode": "Lähdekoodi",
"AbpSuiteExplanation6": "ABP Suite luo lähdekoodin sinulle! Se ei luo taikuustiedostoja verkkosivun luomiseksi. ABP Suite luo lähdekoodin Entity, Repository, Application Service, Code First Migration, JavaScript / TypeScript ja CSHTML / HTML sekä tarvittavat liitännät. ABP Suite tuottaa koodin myös ohjelmistokehityksen parhaiden käytäntöjen mukaisesti, joten sinun ei tarvitse huolehtia luodun koodin laadusta.",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/fr.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/fr.json
index c5f9f1db6c..90d1fcf0c9 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/fr.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/fr.json
@@ -177,7 +177,7 @@
"ChangingLicenseType": "Puis-je changer mon type de licence à l'avenir?",
"ChangingLicenseTypeExplanation": "Vous pouvez toujours ajouter de nouveaux développeurs dans votre même type de licence. Voir aussi \"Combien de développeurs peuvent travailler sur l'ABP Commercial?\". Vous pouvez également passer à une licence supérieure en payant la différence de prix calculée. Lorsque vous passez à un plan de licence supérieur, vous bénéficiez des avantages du nouveau plan, mais la mise à niveau de la licence ne modifie pas la date d'expiration de la licence.",
"LicenseExtendUpgradeDiff": "Quelle est la différence entre l'extension de licence et la mise à niveau?",
- "LicenseExtendUpgradeDiffExplanation": " Extension: en prolongeant / renouvelant votre licence, vous continuerez à bénéficier d'une assistance premium et à des mises à jour majeures pour les modules et les thèmes. De plus, vous pourrez continuer à créer de nouveaux projets. Et vous pourrez toujours utiliser ABP Suite, ce qui accélère votre développement. Mise à niveau: En mettant à jour votre licence, vous passerez à un plan de licence supérieur qui vous permettra d’obtenir des avantages supplémentaires . Consultez le tableau de comparaison des licences pour vérifier les différences entre les plans de licence. En revanche, lors de la mise à niveau, la date d'expiration de votre licence ne changera pas! Strong > Pour prolonger la date de fin de votre licence, vous devez prolonger votre licence.",
+ "LicenseExtendUpgradeDiffExplanation": " Extension: en prolongeant/renouvelant votre licence, vous continuerez à bénéficier d'une assistance premium et à des mises à jour majeures pour les modules et les thèmes. De plus, vous pourrez continuer à créer de nouveaux projets. Et vous pourrez toujours utiliser ABP Suite, ce qui accélère votre développement. Mise à niveau: En mettant à jour votre licence, vous passerez à un plan de licence supérieur qui vous permettra d’obtenir des avantages supplémentaires . Consultez le tableau de comparaison des licences pour vérifier les différences entre les plans de licence. En revanche, lors de la mise à niveau, la date d'expiration de votre licence ne changera pas! Pour prolonger la date de fin de votre licence, vous devez prolonger votre licence.",
"LicenseRenewalCost": "Quel est le coût du renouvellement de la licence après 1 an?",
"LicenseRenewalCostExplanation": "Le taux de renouvellement (extension) de toutes les licences perpétuelles ABP Commercial correspond à {0} du prix catalogue de la licence. Le prix de renouvellement de la licence d'équipe standard est de {1} $, la licence professionnelle standard de {2} $ et la licence d'entreprise standard de {3} $. Si vous êtes déjà client, connectez-vous à votre compte pour consulter les tarifs de renouvellement disponibles.",
"HowDoIRenewMyLicense": "Comment renouveler ma licence?",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/hi.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/hi.json
index 54216f7719..dd7e117541 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/hi.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/hi.json
@@ -42,7 +42,7 @@
"NotOrganizationMember": "आप किसी संगठन के सदस्य नहीं हैं।",
"UnsubscribeLicenseExpirationEmailSuccessTitle": "सफलतापूर्वक सदस्यता समाप्त कर दी गई",
"UnsubscribeLicenseExpirationEmailSuccessMessage": "अब आपको लाइसेंस समाप्ति तिथि अनुस्मारक ईमेल प्राप्त नहीं होंगे।",
- "IndexPageHeroSection": " एक पूर्ण span> वेब विकास मंच span> अंतर्निहित ढांचा span>",
+ "IndexPageHeroSection": "एक पूर्ण वेब डेवलपमेंट प्लेटफॉर्मबिल्ट-ऑन Framework",
"AbpCommercialShortDescription": "एबीपी कमर्शियल प्री-बिल्ट एप्लिकेशन मॉड्यूल, रैपिड एप्लिकेशन डेवलपमेंट टूलिंग, पेशेवर यूआई थीम, प्रीमियम सपोर्ट आदि प्रदान करता है।",
"LiveDemo": "लाइव डेमो",
"GetLicence": "एक लाइसेंस प्राप्त करें",
@@ -135,7 +135,7 @@
"GoHome": "घर जाओ",
"CreateLiveDemo": "लाइव डेमो बनाएँ",
"RegisterToTheNewsletter": "ABP.IO के बारे में जानकारी प्राप्त करने के लिए न्यूज़लेटर के लिए रजिस्टर करें, जिसमें नई रिलीज़ आदि शामिल हैं।",
- "EnterYourEmailOrLogin": "अपने मौजूदा खाते का उपयोग करके अपना डेमो बनाने के लिए अपना ई-मेल पता दर्ज करें या अपना प्रदर्शन लॉगिन करें।",
+ "EnterYourEmailOrLogin": "अपना डेमो बनाने के लिए अपना ई-मेल पता दर्ज करें या अपने मौजूदा खाते का उपयोग करके लॉगिन करें।",
"ApplicationTemplate": "एप्लिकेशन टेम्पलेट",
"ApplicationTemplateExplanation": "एप्लिकेशन स्टार्टअप टेम्पलेट का उपयोग एक नया वेब एप्लिकेशन बनाने के लिए किया जाता है।",
"EfCoreProvider": "इकाई ढाँचा (SQL सर्वर, MySQL, PostgreSQL, Oracle और अन्य का समर्थन करता है)",
@@ -152,50 +152,50 @@
"ABPCLIExplanation": "ABP CLI (कमांड लाइन इंटरफेस) ABP आधारित समाधानों के लिए कुछ सामान्य ऑपरेशन करने के लिए एक कमांड लाइन टूल है।",
"ABPSuiteEasilyCURD": "एबीपी सूट एक उपकरण है जो आपको आसानी से CRUD पेज बनाने की अनुमति देता है",
"WeAreHereToHelp": "हम यहाँ हैं मदद span>",
- "BrowseOrAskQuestion": "आप हमारे सहायता विषयों को ब्राउज़ कर सकते हैं या अक्सर पूछे जाने वाले प्रश्नों में खोज कर सकते हैं, या आप संपर्क फ़ॉर्म का उपयोग करके हमसे एक प्रश्न पूछ सकते हैं।",
+ "BrowseOrAskQuestion": "आप हमारे सहायता विषयों को ब्राउज़ कर सकते हैं या अक्सर पूछे जाने वाले प्रश्नों में खोज कर सकते हैं, या आप संपर्क फ़ॉर्म का उपयोग करके हमसे एक प्रश्न पूछ सकते हैं।",
"SearchQuestionPlaceholder": "अक्सर पूछे जाने वाले प्रश्नों में खोजें",
"WhatIsTheABPCommercial": "ABP कमर्शियल क्या है?",
"WhatAreDifferencesThanAbpFramework": "ओपन सोर्स ABP फ्रेमवर्क और ABP कमर्शियल के बीच क्या अंतर हैं?",
- "ABPCommercialExplanation": "एबीपी कमर्शियल, खुले स्रोत के शीर्ष पर बनाए गए प्रीमियम मॉड्यूल, टूल, थीम और सेवाओं का एक सेट है जो ABP फ्रेमवर्क है। एबीपी कमर्शियल को एबीपी फ्रेमवर्क के पीछे उसी टीम द्वारा विकसित और समर्थित किया जा रहा है।",
- "WhatAreDifferencesThanABPFrameworkExplanation": "
ABP फ्रेमवर्क ASP.NET Core के लिए एक मॉड्यूलर, थीमेबल, माइक्रो-सर्विस संगत एप्लिकेशन डेवलपमेंट फ्रेमवर्क है। यह आपको हर नई परियोजना के लिए खुद को दोहराने के बजाय अपने खुद के व्यवसाय कोड पर ध्यान केंद्रित करने के लिए एक पूर्ण वास्तुकला और एक मजबूत बुनियादी ढांचा प्रदान करता है। यह सॉफ्टवेयर विकास सर्वोत्तम प्रथाओं और लोकप्रिय उपकरणों पर आधारित है जिन्हें आप पहले से जानते हैं। p>
एबीपी फ्रेमवर्क पूरी तरह से मुक्त, खुला स्रोत और समुदाय-संचालित है। यह एक मुफ्त थीम और कुछ पूर्व-निर्मित मॉड्यूल (जैसे पहचान प्रबंधन और किरायेदार प्रबंधन) प्रदान करता है। p>",
- "VisitTheFrameworkVSCommercialDocument": "अधिक जानकारी के लिए, निम्न लिंक पर जाएं {1} ",
+ "ABPCommercialExplanation": "एबीपी कमर्शियल ओपन सोर्स ABP फ्रेमवर्क के शीर्ष पर निर्मित प्रीमियम मॉड्यूल, टूल, थीम और सेवाओं का एक सेट है। एबीपी कमर्शियल को एबीपी ढांचे के पीछे उसी टीम द्वारा विकसित और समर्थित किया जा रहा है।",
+ "WhatAreDifferencesThanABPFrameworkExplanation": "
ABP फ्रेमवर्क ASP.NET कोर के लिए एक मॉड्यूलर, थीम योग्य, माइक्रो-सर्विस संगत एप्लिकेशन डेवलपमेंट फ्रेमवर्क है। यह आपको हर नई परियोजना के लिए खुद को दोहराने के बजाय अपने स्वयं के व्यवसाय कोड पर ध्यान केंद्रित करने के लिए एक पूर्ण वास्तुकला और एक मजबूत बुनियादी ढांचा प्रदान करता है। यह सॉफ्टवेयर विकास सर्वोत्तम प्रथाओं और लोकप्रिय टूल पर आधारित है जिन्हें आप पहले से जानते हैं।
एबीपी ढांचा पूरी तरह से मुक्त, खुला स्रोत और समुदाय संचालित है। यह एक मुफ्त थीम और कुछ पूर्व-निर्मित मॉड्यूल (जैसे पहचान प्रबंधन और किरायेदार प्रबंधन) भी प्रदान करता है।
",
+ "VisitTheFrameworkVSCommercialDocument": "अधिक जानकारी के लिए, निम्न लिंक पर जाएँ {1} ",
"ABPCommercialFollowingBenefits": "एबीपी वाणिज्यिक एबीपी ढांचे के शीर्ष पर निम्नलिखित लाभ जोड़ता है;",
"Professional": "पेशेवर",
"UIThemes": "यूआई थीम",
- "EnterpriseModules": "एंटरप्राइज रेडी, फीचर से भरपूर, पहले से निर्मित एप्लिकेशन मॉड्यूल (जैसे पहचान सर्वर प्रबंधन, सास प्रबंधन, भाषा प्रबंधन)",
- "ToolingToSupport": "अपनी विकास उत्पादकता का समर्थन करने का टूल",
- "PremiumSupportLink": "प्रीमियम समर्थन ",
+ "EnterpriseModules": "एंटरप्राइज़ तैयार, सुविधा संपन्न, पूर्व-निर्मित एप्लिकेशन मॉड्यूल (उदा. पहचान सर्वर प्रबंधन, SaaS प्रबंधन, भाषा प्रबंधन)",
+ "ToolingToSupport": "आपकी विकास उत्पादकता का समर्थन करने के लिए टूलिंग (उदा. ABP Suite)",
+ "PremiumSupportLink": "प्रीमियम समर्थन",
"WhatDoIDownloadABPCommercial": "जब मैं एबीपी कमर्शियल खरीदता हूं तो क्या डाउनलोड करता हूं?",
- "CreateUnlimitedSolutions": "एक बार जब आप एक एबीपी कमर्शियल लाइसेंस खरीदते हैं, तो आप असीमित समाधान बना पाएंगे, जैसे कि Get Started दस्तावेज़ में वर्णित है।",
+ "CreateUnlimitedSolutions": "एक बार जब आप एबीपी वाणिज्यिक लाइसेंस खरीद लेते हैं, तो आप असीमित समाधान बनाने में सक्षम होंगे जैसा कि आरंभ करना दस्तावेज़ में वर्णित है।",
"ABPCommercialSolutionExplanation": "जब आप एक नया एप्लिकेशन बनाते हैं, तो आपको अपनी प्राथमिकताओं के आधार पर एक विज़ुअल स्टूडियो समाधान (एक स्टार्टअप टेम्प्लेट) मिलता है। डाउनलोड किए गए समाधान में आपके लिए पहले से इंस्टॉल और कॉन्फ़िगर किए गए वाणिज्यिक मॉड्यूल और थीम हैं। यदि आप चाहें तो आप पहले से स्थापित मॉड्यूल को हटा सकते हैं या किसी अन्य मॉड्यूल को जोड़ सकते हैं। सभी मॉड्यूल और थीम डिफ़ॉल्ट रूप से एक NuGet / NPM पैकेज का उपयोग किया जाता है।",
- "StartDevelopWithTutorials": "डाउनलोड किया गया समाधान अच्छी तरह से वास्तुकला और दस्तावेज है। आप अपने स्वयं के व्यवसाय कोड को इस आधार पर विकसित करना शुरू कर सकते हैं कि वह ट्यूटोरियल्स का अनुसरण कर सकता है",
- "TryTheCommercialDemo": "ABP कमर्शियल स्टार्टअप टेम्प्लेट का उपयोग करके बनाए गए एक नमूना अनुप्रयोग को देखने के लिए आप डेमो का प्रयास कर सकते हैं।",
+ "StartDevelopWithTutorials": "डाउनलोड किया गया समाधान अच्छी तरह से संरचित और प्रलेखित है। आप ट्यूटोरियल . का अनुसरण करके इसके आधार पर अपना खुद का व्यवसाय कोड विकसित करना शुरू कर सकते हैं",
+ "TryTheCommercialDemo": "ABP कमर्शियल स्टार्टअप टेम्प्लेट का उपयोग करके बनाए गए एक नमूना एप्लिकेशन को देखने के लिए आप डेमो आज़मा सकते हैं।",
"HowManyProducts": "ABP वाणिज्यिक का उपयोग करके मैं कितने विभिन्न उत्पाद / समाधान बना सकता हूं?",
"HowManyProductsExplanation": "ABP प्रोजेक्ट बनाने की कोई सीमा नहीं है। आप जितने चाहें उतने प्रोजेक्ट बना सकते हैं, उन्हें विकसित कर सकते हैं और उन्हें विभिन्न सर्वरों पर अपलोड कर सकते हैं।",
"HowManyDevelopers": "एबीपी कमर्शियल पर कितने डेवलपर काम कर सकते हैं?",
- "HowManyDevelopersExplanation": "एबीपी वाणिज्यिक लाइसेंस प्रति डेवलपर हैं। विभिन्न लाइसेंस प्रकारों में अलग-अलग डेवलपर सीमाएँ होती हैं। हालाँकि, जब भी आपको आवश्यकता हो, आप किसी भी प्रकार के लाइसेंस में अधिक डेवलपर्स जोड़ सकते हैं। लाइसेंस प्रकार, डेवलपर सीमा और अतिरिक्त डेवलपर लागतों के लिए कीमतें पृष्ठ देखें।",
+ "HowManyDevelopersExplanation": "एबीपी वाणिज्यिक लाइसेंस प्रति डेवलपर हैं। विभिन्न लाइसेंस प्रकारों की अलग-अलग डेवलपर सीमाएँ होती हैं। हालांकि, जब भी आपको आवश्यकता हो, आप किसी भी प्रकार के लाइसेंस में अधिक डेवलपर जोड़ सकते हैं। लाइसेंस प्रकारों, डेवलपर सीमाओं और अतिरिक्त डेवलपर लागतों के लिए कीमतें पृष्ठ देखें।",
"ChangingLicenseType": "क्या मैं भविष्य में अपना लाइसेंस प्रकार बदल सकता हूं?",
"ChangingLicenseTypeExplanation": "आप अपने समान लाइसेंस प्रकार में हमेशा नए डेवलपर्स को जोड़ सकते हैं। यह भी देखें \"एबीपी कमर्शियल पर कितने डेवलपर काम कर सकते हैं?\"। आप गणना मूल्य अंतर का भुगतान करके एक उच्च लाइसेंस के लिए भी अपग्रेड कर सकते हैं। जब आप उच्च लाइसेंस योजना में अपग्रेड करते हैं, तो आपको नई योजना का लाभ मिलता है, लेकिन लाइसेंस अपग्रेड लाइसेंस की समाप्ति की तारीख को नहीं बदलता है।",
"LicenseExtendUpgradeDiff": "लाइसेंस विस्तार और उन्नयन के बीच क्या अंतर है?",
"LicenseExtendUpgradeDiffExplanation": " विस्तार: strong> अपने लाइसेंस का विस्तार / नवीनीकरण करके, आप प्रीमियम समर्थन प्राप्त करना और मॉड्यूल और थीम के लिए प्रमुख अपडेट प्राप्त करना जारी रखेंगे। इसके अलावा, आप नई परियोजनाओं को जारी रखने में सक्षम होंगे। और आप अभी भी एबीपी सूट का उपयोग कर पाएंगे जो आपके विकास को गति देता है। उन्नयन: strong> अपने लाइसेंस को अपग्रेड करके, आप एक उच्च लाइसेंस योजना को बढ़ावा देंगे जिससे आप अतिरिक्त लाभ प्राप्त कर सकेंगे। । लाइसेंस योजनाओं के बीच अंतर की जांच करने के लिए लाइसेंस तुलना तालिका देखें। दूसरी ओर, जब आप अपग्रेड करते हैं, तो आपकी लाइसेंस की समाप्ति तिथि नहीं बदलेगी! Strong> > अपनी लाइसेंस की अंतिम तिथि बढ़ाने के लिए, आपको अपने लाइसेंस का विस्तार करना होगा।",
"LicenseRenewalCost": "1 वर्ष के बाद लाइसेंस नवीनीकरण लागत क्या है?",
- "LicenseRenewalCostExplanation": "सभी एबीपी वाणिज्यिक स्थायी लाइसेंसों का नवीकरण (विस्तार) दर लाइसेंस सूची मूल्य का {0} है। मानक टीम लाइसेंस का नवीनीकरण मूल्य $ {1} है, मानक व्यवसाय लाइसेंस $ {2} है और मानक एंटरप्राइज़ लाइसेंस $ {3} है। यदि आप पहले से ही ग्राहक हैं, तो उपलब्ध नवीनीकरण मूल्य निर्धारण की समीक्षा करने के लिए अपने खाते में लॉग इन करें ।",
+ "LicenseRenewalCostExplanation": "सभी एबीपी वाणिज्यिक स्थायी लाइसेंसों की नवीनीकरण (विस्तार) दर लाइसेंस सूची मूल्य का {0} है। मानक टीम लाइसेंस का नवीनीकरण मूल्य ${1} है, मानक व्यवसाय लाइसेंस ${2} है और मानक एंटरप्राइज़ लाइसेंस ${3} है। यदि आप पहले से ही ग्राहक हैं, तो उपलब्ध नवीनीकरण मूल्य-निर्धारण की समीक्षा के लिए अपने खाते में लॉग इन करें।",
"HowDoIRenewMyLicense": "मैं अपने लाइसेंस का नवीनीकरण कैसे करूँ?",
- "HowDoIRenewMyLicenseExplanation": "आप अपने लाइसेंस को संगठन प्रबंधन पृष्ठ पर नेविगेट करके नवीनीकृत कर सकते हैं। हमारी रियायती अर्ली रिन्यूअल दरों का लाभ उठाने के लिए, सुनिश्चित करें कि आप अपने लाइसेंस की समय सीमा समाप्त होने से पहले नवीनीकरण करें। हालाँकि, जब आपका प्रारंभिक नवीनीकरण अवसर बंद हो जाता है, तो यह जानने की चिंता न करें। आपकी सदस्यता समाप्त होने से पहले आपको 2 अनुस्मारक ई-मेल प्राप्त होंगे। हम उन्हें 30 दिन, समाप्ति से 7 दिन पहले भेज देंगे।",
+ "HowDoIRenewMyLicenseExplanation": "आप संगठन प्रबंधन पृष्ठ पर नेविगेट करके अपने लाइसेंस का नवीनीकरण कर सकते हैं। हमारी रियायती प्रारंभिक नवीनीकरण दरों का लाभ उठाने के लिए, अपने लाइसेंस की समय सीमा समाप्त होने से पहले नवीनीकरण करना सुनिश्चित करें। हालाँकि, यह जानने की चिंता न करें कि आपका प्रारंभिक नवीनीकरण अवसर कब बंद होगा। आपकी सदस्यता समाप्त होने से पहले आपको 2 अनुस्मारक ई-मेल प्राप्त होंगे। हम उन्हें समाप्ति से ७ दिन पहले, ३० दिनों में भेजेंगे।",
"IsSourceCodeIncluded": "क्या मेरे लाइसेंस में वाणिज्यिक मॉड्यूल और थीम का स्रोत कोड शामिल है?",
"IsSourceCodeIncludedExplanation1": "आपके द्वारा खरीदे गए लाइसेंस प्रकार पर निर्भर करता है:",
"IsSourceCodeIncludedExplanation2": " टीम strong>: आपका समाधान मॉड्यूल और थीम को NuGet और NPM पैकेज के रूप में उपयोग करता है। इसमें उनका स्रोत कोड शामिल नहीं है। इस तरह, जब भी कोई नया संस्करण उपलब्ध हो, आप इन मॉड्यूल और थीम को आसानी से अपग्रेड कर सकते हैं। हालाँकि, आप मॉड्यूल और थीम के स्रोत कोड प्राप्त नहीं कर सकते।",
"IsSourceCodeIncludedExplanation3": " व्यवसाय / उद्यम strong>: टीम लाइसेंस के अतिरिक्त, आप किसी भी मॉड्यूल या थीम की आवश्यकता के स्रोत कोड को डाउनलोड करने में सक्षम हैं। तुम भी एक विशेष मॉड्यूल के लिए NuGet / NPM पैकेज संदर्भ निकाल सकते हैं और इसे पूरी तरह से बदलने के लिए अपने समाधान के लिए अपने स्रोत कोड को सीधे जोड़ सकते हैं।",
- "IsSourceCodeIncludedExplanation4": "
एक मॉड्यूल के स्रोत कोड को आपके समाधान में शामिल करना आपको उस मॉड्यूल को अनुकूलित करने की अधिकतम स्वतंत्रता देता है। हालाँकि, तब नया संस्करण जारी होने पर मॉड्यूल को स्वचालित रूप से अपग्रेड करना संभव नहीं होगा। p>
किसी भी लाइसेंस में ABP सुइट स्रोत कोड शामिल नहीं है, जो एक बाहरी उपकरण है जो आपके लिए कोड बनाता है और सहायता करता है आपके विकास के लिए। p>
लाइसेंस प्रकारों के अन्य अंतरों के लिए मूल्य निर्धारण पृष्ठ देखें। p>",
+ "IsSourceCodeIncludedExplanation4": "
अपने समाधान में मॉड्यूल के स्रोत कोड को शामिल करने से आपको उस मॉड्यूल को अनुकूलित करने की अधिकतम स्वतंत्रता मिलती है। हालांकि, नया संस्करण जारी होने पर मॉड्यूल को स्वचालित रूप से अपग्रेड करना संभव नहीं होगा।
किसी भी लाइसेंस में एबीपी सूट स्रोत कोड शामिल नहीं है, जो एक बाहरी उपकरण है जो आपके लिए कोड उत्पन्न करता है और सहायता करता है। आपके विकास के लिए।
लाइसेंस प्रकारों के बीच अन्य अंतरों के लिए मूल्य निर्धारण पृष्ठ देखें।
",
"ChangingDevelopers": "क्या मैं भविष्य में अपने संगठन के पंजीकृत डेवलपर्स को बदल सकता हूं?",
"ChangingDevelopersExplanation": "अपने लाइसेंस में नए डेवलपर्स को जोड़ने के अलावा, आप मौजूदा डेवलपर्स को भी बदल सकते हैं (आप एक डेवलपर को हटा सकते हैं और एक ही सीट पर एक नया जोड़ सकते हैं) बिना किसी अतिरिक्त लागत के।",
"WhatHappensWhenLicenseEnds": "मेरे लाइसेंस की अवधि समाप्त होने पर क्या होता है?",
- "WhatHappensWhenLicenseEndsExplanation1": "ABP कमर्शियल लाइसेंस का प्रकार स्थायी लाइसेंस है। आपके लाइसेंस की समय सीमा समाप्त होने के बाद, आप अपना प्रोजेक्ट विकसित करना जारी रख सकते हैं। और आप अपने लाइसेंस को नवीनीकृत करने के लिए बाध्य नहीं हैं। आपका लाइसेंस एक वर्ष के अपडेट और समर्थन योजना के साथ आता है। नई सुविधाओं को प्राप्त करने के लिए, प्रदर्शन में वृद्धि, बग फिक्स, समर्थन और एबीपी सूट का उपयोग करना जारी रखें, प्रत्येक वर्ष अपनी योजना को नवीनीकृत करना सुनिश्चित करें। जब आपका लाइसेंस समाप्त हो जाता है, तो आप निम्नलिखित लाभ प्राप्त नहीं कर पाएंगे;",
+ "WhatHappensWhenLicenseEndsExplanation1": "ABP वाणिज्यिक लाइसेंस प्रकार स्थायी लाइसेंस है। आपके लाइसेंस की समय सीमा समाप्त होने के बाद, आप अपने प्रोजेक्ट को विकसित करना जारी रख सकते हैं। और आप अपने लाइसेंस को नवीनीकृत करने के लिए बाध्य नहीं हैं। आपका लाइसेंस बॉक्स से बाहर एक साल के अपडेट और समर्थन योजना के साथ आता है। नई सुविधाओं, प्रदर्शन में सुधार, बग फिक्स, समर्थन प्राप्त करना जारी रखने और एबीपी सूट का उपयोग जारी रखने के लिए, हर साल अपनी योजना को नवीनीकृत करना सुनिश्चित करें। जब आपका लाइसेंस समाप्त हो जाता है, तो आप निम्नलिखित में से अधिक लाभ प्राप्त नहीं कर पाएंगे;",
"WhatHappensWhenLicenseEndsExplanation2": "आप एबीपी कमर्शियल का उपयोग करके नए समाधान नहीं बना सकते हैं, लेकिन आप अपने मौजूदा अनुप्रयोगों को हमेशा के लिए विकसित कर सकते हैं।",
"WhatHappensWhenLicenseEndsExplanation3": "आप अपने मुख्य संस्करण के भीतर मॉड्यूल और विषयों के लिए अद्यतन प्राप्त करने में सक्षम होंगे। उदाहरण के लिए; यदि आप किसी मॉड्यूल के v3.2.0 का उपयोग कर रहे हैं, तो आप उस मॉड्यूल के v3.x.x (v3.3.0, v3.5.2 ... आदि) के लिए अपडेट प्राप्त कर सकते हैं। लेकिन आपको अगले प्रमुख संस्करण के लिए अपडेट नहीं मिल सकता है (जैसे v4.x, v5.x)",
"WhatHappensWhenLicenseEndsExplanation4": "आप अपने लाइसेंस समाप्त होने के बाद एबीपी वाणिज्यिक मंच में जोड़े गए नए मॉड्यूल और थीम स्थापित नहीं कर सकते।",
"WhatHappensWhenLicenseEndsExplanation5": "आप एबीपी सूट का उपयोग नहीं कर सकते।",
- "WhatHappensWhenLicenseEndsExplanation6": "आपको अब और प्रीमियम सहायता नहीं मिल सकती है।",
+ "WhatHappensWhenLicenseEndsExplanation6": "अब आपको प्रीमियम सहायता नहीं मिल सकती है।",
"WhatHappensWhenLicenseEndsExplanation7": "यदि आप इन लाभों को प्राप्त करना जारी रखना चाहते हैं तो आप अपनी सदस्यता को नवीनीकृत कर सकते हैं। जब आप अपनी सदस्यता को नवीनीकृत करते हैं तो 20% छूट मिलती है।",
"WhenShouldIRenewMyLicense": "मुझे अपना लाइसेंस कब नवीनीकृत करना चाहिए?",
"WhenShouldIRenewMyLicenseExplanation1": "यदि आप अपना लाइसेंस समाप्त होने के बाद अपने लाइसेंस का नवीनीकरण 1 महीने strong> के भीतर करते हैं, तो कुल लाइसेंस मूल्य पर% 20 छूट लागू होगी।",
@@ -206,21 +206,21 @@
"DoYouAcceptBankWireTransferExplanation": "हां, हम बैंक वायर ट्रांसफर स्वीकार करते हैं। बैंक वायर ट्रांसफर के माध्यम से लाइसेंस राशि भेजने के बाद, हमें अपनी रसीद और अनुरोधित लाइसेंस प्रकार ई-मेल के माध्यम से भेजें। हमारे अंतरराष्ट्रीय बैंक खाते की जानकारी:",
"HowToUpgrade": "नया संस्करण उपलब्ध होने पर मौजूदा एप्लिकेशन को कैसे अपग्रेड किया जाए?",
"HowToUpgradeExplanation1": "जब आप ABP कमर्शियल का उपयोग करके एक नया एप्लिकेशन बनाते हैं, तो सभी मॉड्यूल और थीम को NuGet और NPM पैकेज के रूप में उपयोग किया जाता है। इसलिए, नया संस्करण उपलब्ध होने पर आप आसानी से संकुल को अपग्रेड कर सकते हैं।",
- "HowToUpgradeExplanation2": "मानक NuGet / NPM अपग्रेड के अलावा, ABP CLI एक अपडेट कमांड प्रदान करता है जो आपके समाधान में सभी एबीपी से संबंधित पैकेजों को स्वचालित रूप से ढूंढता है और उन्हें अपग्रेड करता है।",
+ "HowToUpgradeExplanation2": "मानक NuGet/NPM अपग्रेड के अलावा, ABP CLI एक अपडेट कमांड प्रदान करता है जो आपके समाधान में सभी ABP संबंधित पैकेजों को स्वचालित रूप से ढूंढता और अपग्रेड करता है।",
"DatabaseSupport": "कौन से डेटाबेस सिस्टम समर्थित हैं?",
- "DatabaseSupportExplanation": "ABP फ्रेमवर्क स्वयं ही डेटाबेस अज्ञेयवादी है और अपनी प्रकृति के अनुसार किसी भी डेटाबेस प्रदाता के साथ काम कर सकता है। वर्तमान में कार्यान्वित प्रदाताओं की सूची के लिए डेटा एक्सेस दस्तावेज़ देखें।",
+ "DatabaseSupportExplanation": "एबीपी फ्रेमवर्क अपने आप में डेटाबेस अज्ञेयवादी है और अपनी प्रकृति से किसी भी डेटाबेस प्रदाता के साथ काम कर सकता है। वर्तमान में कार्यान्वित प्रदाताओं की सूची के लिए डेटा एक्सेस दस्तावेज़ देखें।",
"UISupport": "कौन से UI फ्रेमवर्क समर्थित हैं?",
"Supported": "समर्थित",
- "UISupportExplanation": "ABP फ्रेमवर्क स्वयं UI फ्रेमवर्क अज्ञेयवादी है और किसी भी UI फ्रेमवर्क के साथ काम कर सकता है। हालाँकि, सभी UI फ्रेमवर्क के लिए स्टार्टअप टेम्प्लेट, मॉड्यूल UI और थीम लागू नहीं किए गए थे। UI विकल्पों की अप-टू-डेट सूची के लिए आरंभ किया गया दस्तावेज़ देखें।",
+ "UISupportExplanation": "एबीपी फ्रेमवर्क अपने आप में यूआई फ्रेमवर्क अज्ञेयवादी है और किसी भी यूआई फ्रेमवर्क के साथ काम कर सकता है। हालांकि, स्टार्टअप टेम्प्लेट, मॉड्यूल UI और थीम सभी UI फ्रेमवर्क के लिए लागू नहीं किए गए थे। UI विकल्पों की अप-टू-डेट सूची के लिए आरंभ करने वाला दस्तावेज़ देखें।",
"MicroserviceSupport": "क्या यह सूक्ष्म सेवा वास्तुकला का समर्थन करता है?",
- "MicroserviceSupportExplanation1": "एबीपी ढांचे का एक प्रमुख लक्ष्य सूक्ष्म सेवा समाधान बनाने के लिए एक सुविधाजनक बुनियादी ढांचा प्रदान करना है। यह समझने के लिए कि यह माइक्रो-सर्विस सिस्टम बनाने में कैसे मदद करता है, यह समझने के लिए माइक्रो-सर्विस आर्किटेक्चर दस्तावेज़ देखें।",
- "MicroserviceSupportExplanation2": "सभी एबीपी कमर्शियल मॉड्यूल्स को मॉड्यूल डेवलपमेंट बेस्ट प्रैक्टिस दस्तावेज़ का पालन करके माइक्रो-सर्विस परिनियोजन परिदृश्य (अपने एपीआई और डेटाबेस के साथ) का समर्थन करने के लिए डिज़ाइन किया गया है।",
- "MicroserviceSupportExplanation3": "हम आपको अपना स्वयं का समाधान बनाने में मदद करने के लिए एक माइक्रो-सेवा वास्तुकला कार्यान्वयन को प्रदर्शित करने वाला एक नमूना माइक्रो-सर्विस डेमो समाधान प्रदान करते हैं।",
+ "MicroserviceSupportExplanation1": "एबीपी ढांचे के प्रमुख लक्ष्यों में से एक सूक्ष्म सेवा समाधान बनाने के लिए एक सुविधाजनक बुनियादी ढांचा प्रदान करना है। यह समझने के लिए कि यह माइक्रो-सर्विस सिस्टम बनाने में कैसे मदद करता है, माइक्रो-सर्विस आर्किटेक्चर दस्तावेज़ देखें।",
+ "MicroserviceSupportExplanation2": "सभी एबीपी वाणिज्यिक मॉड्यूल मॉड्यूल विकास सर्वोत्तम प्रथाओं दस्तावेज़ का पालन करके माइक्रो-सेवा परिनियोजन परिदृश्यों (अपने स्वयं के एपीआई और डेटाबेस के साथ) का समर्थन करने के लिए डिज़ाइन किए गए हैं।",
+ "MicroserviceSupportExplanation3": "हम एक नमूना माइक्रो-सर्विस डेमो सॉल्यूशन प्रदान करते हैं जो आपको अपना समाधान बनाने में मदद करने के लिए एक माइक्रो-सर्विस आर्किटेक्चर कार्यान्वयन दर्शाता है।",
"MicroserviceSupportExplanation4": "तो, संक्षिप्त उत्तर \" हां है, यह सूक्ष्म सेवा वास्तुकला का समर्थन करता है strong>\"।",
"MicroserviceSupportExplanation5": "हालाँकि, एक माइक्रो-सर्विस सिस्टम एक समाधान है और हर समाधान में अलग-अलग आवश्यकताएं, नेटवर्क टोपोलॉजी, संचार परिदृश्य, प्रमाणीकरण संभावनाएं, डेटाबेस पृथक्करण / साझा करने के निर्णय, रनटाइम कॉन्फ़िगरेशन, 3 पार्टी सिस्टम एकीकरण और कई और अधिक होंगे।",
"MicroserviceSupportExplanation6": "ABP फ्रेमवर्क और ABP कमर्शियल आपको अपने स्वयं के समाधान का निर्माण करने में मदद करने के लिए सूक्ष्म सेवा परिदृश्य, सूक्ष्म सेवा संगत मॉड्यूल, नमूने और प्रलेखन के लिए बुनियादी ढाँचा प्रदान करता है। लेकिन अपने सपनों के समाधान को सीधे आपके लिए पहले से डाउनलोड करने की उम्मीद न करें। आपको इसे समझने और अपनी आवश्यकताओं के आधार पर कुछ हिस्सों को एक साथ लाने की आवश्यकता होगी।",
"WhereCanIDownloadSourceCode": "मैं स्रोत-कोड कहां से डाउनलोड कर सकता हूं?",
- "WhereCanIDownloadSourceCodeExplanation": "आप एबीपी सूट या एबीपी सीएलआई के माध्यम से सभी एबीपी मॉड्यूल, कोणीय पैकेज और थीम के स्रोत कोड डाउनलोड कर सकते हैं। स्रोत-कोड डाउनलोड कैसे करें? देखें",
+ "WhereCanIDownloadSourceCodeExplanation": "आप एबीपी सूट या एबीपी सीएलआई के माध्यम से सभी एबीपी मॉड्यूल, एंगुलर पैकेज और थीम का सोर्स कोड डाउनलोड कर सकते हैं। देखें स्रोत-कोड कैसे डाउनलोड करें?",
"ComputerLimitation": "एबीपी विकसित करते समय एक डेवलपर कितने कंप्यूटरों पर लॉगिन कर सकता है?",
"ComputerLimitationExplanation": "हम विशेष रूप से प्रति व्यक्ति / लाइसेंस प्राप्त डेवलपर के लिए {0} कंप्यूटर strong> की अनुमति देते हैं। जब भी किसी तीसरे मशीन पर एबीपी कमर्शियल उत्पादों को विकसित करने के लिए डेवलपर की आवश्यकता होती है, तो स्थिति को समझाते हुए लाइसेंस@abp.io को एक ई-मेल भेजा जाना चाहिए और फिर हम अपने सिस्टम में उचित आवंटन करेंगे।",
"RefundPolicy": "क्या आपके पास धनवापसी नीति है?",
@@ -230,17 +230,17 @@
"HowCanIRefundVatExplanation2": "अपने 2 चेकआउट खाते में लॉग इन करें",
"HowCanIRefundVatExplanation3": "उपयुक्त आदेश खोजें और \"रिफंड बेल्ड वैट\" दबाएं (अपनी वैट आईडी दर्ज करें)",
"HowCanIGetMyInvoice": "मैं अपना चालान कैसे प्राप्त कर सकता हूं?",
- "HowCanIGetMyInvoiceExplanation": "लाइसेंस खरीदने के लिए 2 भुगतान गेटवे हैं: PayU और 2 चेकआउट। यदि आप 2Checkout गेटवे के माध्यम से अपना लाइसेंस खरीदते हैं, तो यह आपके ईमेल पते पर पीडीएफ चालान भेजता है, देखें 2 चेकआउट चालान। यदि आप पेयू गेटवे या बैंक वायर ट्रांसफर के माध्यम से खरीदते हैं, तो हम आपका चालान तैयार करेंगे और भेजेंगे। आप अपने चालान का अनुरोध संगठन प्रबंधन पृष्ठ से कर सकते हैं",
+ "HowCanIGetMyInvoiceExplanation": "लाइसेंस खरीदने के लिए 2 भुगतान गेटवे हैं: PayU और 2 चेकआउट। यदि आप 2Checkout गेटवे के माध्यम से अपना लाइसेंस खरीदते हैं, तो यह आपके ईमेल पते पर पीडीएफ चालान भेजता है, देखें 2 चेकआउट चालान। यदि आप पेयू गेटवे या बैंक वायर ट्रांसफर के माध्यम से खरीदते हैं, तो हम आपका चालान तैयार करेंगे और भेजेंगे। आप अपने चालान का अनुरोध संगठन प्रबंधन पृष्ठ से कर सकते हैं",
"Forum": "मंच",
"SupportExplanation": "ABP कमर्शियल लाइसेंस एक टीम द्वारा प्रीमियम फ़ोरम सपोर्ट प्रदान करता है जिसमें ABP फ्रेमवर्क विशेषज्ञ होते हैं।",
"PrivateTicket": "निजी टिकट",
"PrivateTicketExplanation": "एंटरप्राइज लाइसेंस में ई-मेल और टिकट प्रणाली के साथ एक निजी सहायता भी शामिल है।",
"AbpSuiteExplanation1": "ABP सुइट आपको कुछ ही मिनटों में वेब पेज बनाने की अनुमति देता है। यह .NET कोर ग्लोबल टूल है जिसे कमांड लाइन से इंस्टॉल किया जा सकता है।",
- "AbpSuiteExplanation2": "यह एक नया ABP समाधान बना सकता है, डेटाबेस से फ्रंट-एंड तक CRUD पेज बना सकता है। तकनीकी ओवरव्यू के लिए दस्तावेज़ देखें",
+ "AbpSuiteExplanation2": "यह एक नया ABP समाधान बना सकता है, डेटाबेस से फ्रंट-एंड तक CRUD पेज बना सकता है। तकनीकी ओवरव्यू के लिए दस्तावेज़ देखें",
"FastEasy": "तेज और आसान",
"AbpSuiteExplanation3": "ABP सुइट आपको आसानी से CRUD पेज बनाने की अनुमति देता है। आपको बस अपनी इकाई और उसके गुणों को परिभाषित करने की आवश्यकता है, बाकी को आप के लिए एबीपी सूट करने दें! एबीपी सूट कुछ ही सेकंड में आपके सीआरयूडी पृष्ठ के लिए सभी आवश्यक कोड उत्पन्न करता है। यह Angular, MVC और Blazor यूजर इंटरफेस को सपोर्ट करता है।",
"RichOptions": "अमीर विकल्प",
- "AbpSuiteExplanation4": "ABP सुइट रेजर पेज और Angular । यह MongoDB जैसे कई डेटाबेस का समर्थन करता है और सभी डेटाबेस EntityFramework Core <द्वारा समर्थित है / strong> (MS SQL सर्वर, Oracle, MySql, PostgreSQL और )।",
+ "AbpSuiteExplanation4": "ABP Suite supports multiple UI options like Razor Pages and Angular.It also supports multiple databases like MongoDB and all databases supported by EntityFramework Core (MS SQL Server, Oracle, MySql, PostgreSQL and more).",
"AbpSuiteExplanation5": "अच्छी बात यह है कि, आपको उन विकल्पों के बारे में चिंता करने की ज़रूरत नहीं है। एबीपी सूट आपके प्रोजेक्ट के प्रकार को समझता है और आपकी परियोजना के लिए कोड बनाता है और उत्पन्न कोड को आपके प्रोजेक्ट में सही जगह पर रखता है।",
"SourceCode": "सोर्स कोड",
"AbpSuiteExplanation6": "ABP स्वीट आपके लिए सोर्स कोड जेनरेट करता है! यह वेब पेज जनरेट करने के लिए मैजिक फाइल्स जेनरेट नहीं करता है। एबीपी सूट इकाई, रिपोजिटरी, एप्लीकेशन सर्विस, कोड फर्स्ट माइग्रेशन, जावास्क्रिप्ट / टाइपस्क्रिप्ट और सीएसएचटीएमएल / एचटीएमएल strong> और आवश्यक इंटरफेस के लिए भी स्रोत कोड उत्पन्न करता है। ABP Suite सॉफ्टवेयर डेवलपमेंट के बेस्ट प्रैक्टिसेस strong> के अनुसार कोड भी तैयार करता है, इसलिए आपको जनरेट किए गए कोड की गुणवत्ता के बारे में चिंता करने की आवश्यकता नहीं है।",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/it.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/it.json
index 766702a92b..2eaef28623 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/it.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/it.json
@@ -151,7 +151,7 @@
"SeeAllModules": "Vedi tutti i moduli",
"ABPCLIExplanation": "ABP CLI (Command Line Interface) è uno strumento a riga di comando per eseguire alcune operazioni comuni per soluzioni basate su ABP.",
"ABPSuiteEasilyCURD": "ABP Suite è uno strumento che ti permette di creare facilmente pagine CRUD",
- "WeAreHereToHelp": "Siamo qui per Aiuto ",
+ "WeAreHereToHelp": "Siamo qui per Aiuto ",
"BrowseOrAskQuestion": "Puoi sfogliare i nostri argomenti della guida o cercare nelle domande frequenti oppure puoi farci una domanda utilizzando il modulo di contatto .",
"SearchQuestionPlaceholder": "Cerca nelle domande frequenti",
"WhatIsTheABPCommercial": "Cos'è l'ABP Commercial?",
@@ -177,7 +177,7 @@
"ChangingLicenseType": "Posso cambiare il mio tipo di licenza in futuro?",
"ChangingLicenseTypeExplanation": "Puoi sempre aggiungere nuovi sviluppatori con lo stesso tipo di licenza. Vedi anche \"Quanti sviluppatori possono lavorare su ABP Commercial?\". Puoi anche passare a una licenza superiore pagando la differenza di prezzo calcolata. Quando esegui l'aggiornamento a un piano di licenza superiore, ottieni i vantaggi del nuovo piano, ma l'aggiornamento della licenza non modifica la data di scadenza della licenza.",
"LicenseExtendUpgradeDiff": "Qual è la differenza tra estensione della licenza e aggiornamento?",
- "LicenseExtendUpgradeDiffExplanation": " Estensione: estendendo / rinnovando la tua licenza, continuerai a ricevere supporto premium e a ricevere aggiornamenti importanti per moduli e temi. Inoltre, potrai continuare a creare nuovi progetti. E sarai ancora in grado di utilizzare ABP Suite che accelera il tuo sviluppo. Upgrade: aggiornando la tua licenza, promuoverai un piano di licenza superiore che ti consentirà di ottenere ulteriori vantaggi . Consulta la tabella di confronto delle licenze per verificare le differenze tra i piani di licenza. D'altra parte, quando esegui l'upgrade, la data di scadenza della licenza non cambierà! Strong > Per estendere la data di fine della licenza, è necessario estendere la licenza.",
+ "LicenseExtendUpgradeDiffExplanation": " Estensione: estendendo/rinnovando la tua licenza, continuerai a ricevere supporto premium e a ricevere aggiornamenti importanti per moduli e temi. Inoltre, potrai continuare a creare nuovi progetti. E sarai ancora in grado di utilizzare ABP Suite che accelera il tuo sviluppo. Upgrade: aggiornando la tua licenza, promuoverai un piano di licenza superiore che ti consentirà di ottenere ulteriori vantaggi . Consulta la tabella di confronto delle licenze per verificare le differenze tra i piani di licenza. D'altra parte, quando esegui l'upgrade, la data di scadenza della licenza non cambierà! Per estendere la data di fine della licenza, è necessario estendere la licenza.",
"LicenseRenewalCost": "Qual è il costo del rinnovo della licenza dopo 1 anno?",
"LicenseRenewalCostExplanation": "La tariffa di rinnovo (estensione) di tutte le licenze perpetue ABP Commercial è {0} del prezzo di listino della licenza. Il prezzo di rinnovo della licenza Team standard è $ {1}, la licenza Business standard è $ {2} e la licenza Enterprise standard è $ {3}. Se sei già un cliente, accedi al tuo account per esaminare i prezzi di rinnovo disponibili.",
"HowDoIRenewMyLicense": "Come rinnovo la mia licenza?",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/tr.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/tr.json
index 76d6fc7c57..c07678b890 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/tr.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Commercial/Localization/Resources/tr.json
@@ -97,6 +97,7 @@
"VolosoftSharingInformationMessage": "Volosoft'un ürünlerimi seçkin ortaklarla paylaşmasını kabul ediyorum, böylece ilgili ortakların ürünleri ve hizmetleri hakkında ilgili bilgileri alabilirim.",
"WeWillSendYouADownloadLink": "{0} adresine email gönderilmiştir.",
"InvalidFormInputs": "Lütfen formda belirtilen geçerli bilgileri yazınız.",
- "DDDBookEmailBody": "Teşekkürler. Kitabı indirmek için, buraya tıklayınız."
+ "DDDBookEmailBody": "Teşekkürler. Kitabı indirmek için, buraya tıklayınız.",
+ "FreeDDDEBook": "Ücretsiz DDD E-Kitap"
}
}
\ No newline at end of file
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Community/Localization/Resources/fi.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Community/Localization/Resources/fi.json
index cba33bfc30..3d06abb52e 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Community/Localization/Resources/fi.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Community/Localization/Resources/fi.json
@@ -118,7 +118,7 @@
"CreatePostCoverInfo": "Lisää kansikuva, jotta voit luoda tehokkaan viestin. Lataa 16: 9-kuvasuhteen kuvat parhaan näkymän saamiseksi. Tiedoston enimmäiskoko: 1 Mt.",
"ThankYouForContribution": "Kiitos osallistumisesta ABP-yhteisöön.",
"GithubArticle": "Github-artikkeli",
- "GithubArticleSubmitStepOne": " 1. Kirjoita artikkeli mistä tahansa julkisesta GitHub-arkistosta Markdown-muodossa. esimerkki ",
+ "GithubArticleSubmitStepOne": "1. Kirjoita artikkeli mistä tahansa julkisesta GitHub-arkistosta Markdown-muodossa. esimerkki ",
"GithubArticleSubmitStepTwo": " 2. Lähetä artikkelin URL-osoite lomaketta käyttämällä.",
"GithubArticleSubmitStepThree": " 3. Artikkelisi renderöidään tällä verkkosivustolla.",
"YoutubeVideo": "Youtube-video",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Community/Localization/Resources/hi.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Community/Localization/Resources/hi.json
index a3f824d6ba..546531445e 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Community/Localization/Resources/hi.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Community/Localization/Resources/hi.json
@@ -96,7 +96,7 @@
"JoinOurArticleNewsletter": "हमारे लेख समाचार पत्र में शामिल हों",
"Community": "समुदाय",
"Marketing": "विपणन",
- "CommunityPrivacyPolicyConfirmation": "मैं नियम और शर्तों और गोपनीयता नीति से सहमत हूं।",
+ "CommunityPrivacyPolicyConfirmation": "मैं नियम और शर्तों और गोपनीयता नीति से सहमत हूं।",
"ArticleRequestMessageTitle": "GitHub पर एक लेख / ट्यूटोरियल जिसे आप इस वेब साइट पर देखना चाहते हैं, का अनुरोध करने के लिए एक समस्या खोलें ।",
"ArticleRequestMessageBody": "यहाँ, समुदाय द्वारा अनुरोधित लेखों की सूची। क्या आप एक अनुरोधित लेख लिखना चाहते हैं? कृपया अनुरोध पर क्लिक करें और चर्चा में शामिल हों।",
"Language": "भाषा: हिन्दी",
@@ -118,7 +118,7 @@
"CreatePostCoverInfo": "एक प्रभावी पोस्ट बनाने के लिए, एक कवर फ़ोटो जोड़ें। सर्वश्रेष्ठ दृश्य के लिए 16: 9 पहलू अनुपात चित्र अपलोड करें। अधिकतम फ़ाइल आकार: 1 एमबी।",
"ThankYouForContribution": "ABP समुदाय में योगदान के लिए धन्यवाद।",
"GithubArticle": "गीथब लेख",
- "GithubArticleSubmitStepOne": " 1। span> मार्कडाउन प्रारूप के साथ किसी भी सार्वजनिक GitHub रिपॉजिटरी पर एक लेख लिखें। उदाहरण ",
+ "GithubArticleSubmitStepOne": "1. मार्कडाउन प्रारूप के साथ किसी भी सार्वजनिक GitHub रिपॉजिटरी पर एक लेख लिखें। उदाहरण ",
"GithubArticleSubmitStepTwo": " 2। span> फ़ॉर्म का उपयोग करके अपना लेख URL सबमिट करें।",
"GithubArticleSubmitStepThree": " 3। span> इस वेब साइट में आपका लेख प्रस्तुत किया जाएगा।",
"YoutubeVideo": "यूट्यूब वीडियो",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en-GB.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en-GB.json
index 1f060d00b0..c53bf82d37 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en-GB.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en-GB.json
@@ -255,8 +255,6 @@
"Surname": "Surname",
"CompanyName": "Company Name",
"DoYouAgreePrivacyPolicy": "I agree to the Terms & Conditions and Privacy Policy.",
- "VolosoftMarketingInformationMessage": "I would like information, tips, and offers about Solutions for Businesses and Organizations and other Volosoft products and services.",
- "VolosoftSharingInformationMessage": "I would like Volosoft to share my information with select partners so I can receive relevant information about their products and services.",
"Free": "Free",
"DDDEBook": "DDD E-book",
"PracticalGuideForImplementingDDD": "This book is a practical guide for implementing the Domain Driven Design with the ABP Framework.",
@@ -270,6 +268,8 @@
"WeWillSendYouADownloadLink": "We've sent the file to {0}.",
"GoHome": "Go Home",
"InvalidFormInputs": "Please, type the valid information specified on the form.",
- "DDDBookEmailBody": "Thank you. To download your book, click here."
+ "DDDBookEmailBody": "Thank you. To download your book, click here.",
+ "SubscribeToNewsletter": "Subscribe to the newsletter to get information about happenings in the ABP.IO Platform, like new releases, articles, offers, and more.",
+ "FirstEdition": "First Edition"
}
}
\ No newline at end of file
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json
index 87da55dbab..1385845f2e 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json
@@ -244,7 +244,7 @@
"ExampleUseCase": "Example Use Case",
"DomainAndApplicationLogic": "Domain Logic & Application Logic",
"Author": "Author",
- "Page": "Page",
+ "Pages": "Pages",
"PublishedOn": "Published on",
"FreeEBook": "Free E-Book",
"Download": "Download",
@@ -256,8 +256,6 @@
"Surname": "Surname",
"CompanyName": "Company Name",
"DoYouAgreePrivacyPolicy": "I agree to the Terms & Conditions and Privacy Policy.",
- "VolosoftMarketingInformationMessage": "I would like information, tips, and offers about Solutions for Businesses and Organizations and other Volosoft products and services.",
- "VolosoftSharingInformationMessage": "I would like Volosoft to share my information with select partners so I can receive relevant information about their products and services.",
"Free": "Free",
"DDDEBook": "DDD E-book",
"PracticalGuideForImplementingDDD": "This book is a practical guide for implementing the Domain Driven Design with the ABP Framework.",
@@ -268,9 +266,13 @@
"DomainVsApplicationLogic": "Domain Logic vs Application Logic",
"SamplesAndDiscussions": "Samples & Discussions",
"EmailNotValid": "Please enter a valid email address.",
- "WeWillSendYouADownloadLink": "A link to download the e-book has been sent to {0}. Check your inbox / junk / spam boxes!",
+ "WeWillSendYouADownloadLink": "A link to download the e-book has been sent to {0}. Check your inbox, junk or spam boxes!",
"GoHome": "Go Home",
"InvalidFormInputs": "Please, type the valid information specified on the form.",
- "DDDBookEmailBody": "Thank you. To download your book, click here."
+ "DDDBookEmailBody": "Thank you. To download your book, click here.",
+ "SubscribeToNewsletter": "Subscribe to the newsletter to get information about happenings in the ABP.IO Platform, like new releases, articles, offers, and more.",
+ "FirstEdition": "First Edition",
+ "ThankYou": "Thank you!",
+ "CheckboxMandatory": "You need to check this to proceed!"
}
}
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/fr.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/fr.json
index 878af5e830..23ae2cc444 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/fr.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/fr.json
@@ -155,7 +155,7 @@
"Code": "Code",
"Result": "Résultat",
"SeeTheDocumentForMoreInformation": "Consultez le {0} document pour plus d'informations",
- "IndexPageHeroSection": " open source Application Web Framework pour asp.net core ",
+ "IndexPageHeroSection": "open sourceWeb Application Framework for asp.net core",
"UiFramework": "Framework de l'interface utilisateur",
"EmailAddress": "Adresse e-mail",
"Mobile": "Mobile",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/hi.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/hi.json
index a7974d8658..a36dbf5aeb 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/hi.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/hi.json
@@ -94,7 +94,7 @@
"DynamicForms": "गतिशील रूप",
"BundlingMinification": "बंडलिंग और न्यूनतमकरण",
"BackgroundJobs": "बैकग्राउंड जॉब्स",
- "BackgroundJobsExplanation": "सरल कक्षाओं को परिभाषित करें ताकि पृष्ठभूमि में नौकरियों को निष्पादित किया जा सके। अंतर्निहित नौकरी प्रबंधक का उपयोग करें या अपने स्वयं के एकीकृत करें। Hangfire और RabbitMQ एकीकरण पहले से ही उपलब्ध हैं।",
+ "BackgroundJobsExplanation": "कतारबद्ध के रूप में पृष्ठभूमि में कार्य निष्पादित करने के लिए सरल वर्गों को परिभाषित करें। बिल्ट-इन जॉब मैनेजर का उपयोग करें या अपना खुद का एकीकृत करें। Hangfire और RabbitMQ एकीकरण पहले से ही उपलब्ध हैं।",
"DDDInfrastructure": "डीडीडी इन्फ्रास्ट्रक्चर",
"DomainDrivenDesignInfrastructure": "डोमेन संचालित डिज़ाइन इन्फ्रास्ट्रक्चर",
"AutoRESTAPIs": "ऑटो रीस्ट एपीआई",
@@ -104,7 +104,7 @@
"TestInfrastructure": "टेस्ट इन्फ्रास्ट्रक्चर",
"AuditLoggingEntityHistories": "ऑडिट लॉगिंग और इकाई इतिहास",
"ObjectToObjectMapping": "ऑब्जेक्ट टू ऑब्जेक्ट मैपिंग",
- "ObjectToObjectMappingExplanation": "AutoMapper एकीकरण के साथ अमूर्तता के लिए ऑब्जेक्ट मैपिंग पर ऑब्जेक्ट ।",
+ "ObjectToObjectMappingExplanation": "ऑटोमैपर एकीकरण के साथ ऑब्जेक्ट टू ऑब्जेक्ट मैपिंग एब्स्ट्रैक्शन।",
"EmailSMSAbstractions": "ईमेल और एसएमएस अंश",
"EmailSMSAbstractionsWithTemplatingSupport": "ईमेल और एसएमएस अंशांकन समर्थन के साथ",
"Localization": "स्थानीयकरण",
@@ -154,8 +154,8 @@
"AndMore": "और अधिक...",
"Code": "कोड",
"Result": "परिणाम",
- "SeeTheDocumentForMoreInformation": "अधिक जानकारी के लिए {0} दस्तावेज़ देखें",
- "IndexPageHeroSection": "<स्पैन क्लास = \"फर्स्ट-लाइन शाइन\"> ओपन सोर्स strong> span> <स्पैन क्लास = \"सेकंड-लाइन टेक्स्ट-अपरकेस\"> वेब एप्लिकेशन फ्रेमवर्क span> asp.net core के लिए strong> span>",
+ "SeeTheDocumentForMoreInformation": "अधिक जानकारी के लिए {0} दस्तावेज़ देखें",
+ "IndexPageHeroSection": "open sourceWeb Application Framework for asp.net core",
"UiFramework": "यूआई फ्रेमवर्क",
"EmailAddress": "ईमेल पता",
"Mobile": "मोबाइल",
@@ -169,13 +169,13 @@
"JoinTheABPCommunityInfo": "एक जीवंत समुदाय के साथ शामिल हों और ABP फ्रेमवर्क में योगदानकर्ता बनें!",
"AllArticles": "सभी चीज़ें",
"SubmitYourArticle": "अपना लेख प्रस्तुत करें",
- "DynamicClientProxyDocument": " JavaScript और C # के लिए डायनेमिक क्लाइंट प्रॉक्सी दस्तावेज़ देखें।",
- "EmailSMSAbstractionsDocument": "अधिक जानकारी के लिए ईमेल करना और एसएमएस भेजने के दस्तावेज़ देखें।",
+ "DynamicClientProxyDocument": "JavaScript और C# के लिए गतिशील क्लाइंट प्रॉक्सी दस्तावेज़ देखें।",
+ "EmailSMSAbstractionsDocument": "अधिक जानकारी के लिए ईमेलिंग और एसएमएस भेजना दस्तावेज़ देखें।",
"CreateProjectWizard": "यह विज़ार्ड स्टार्टअप टेम्प्लेट से एक नई परियोजना बनाता है जो आपकी परियोजना को शुरू करने के लिए ठीक से कॉन्फ़िगर किया गया है।",
"TieredOption": "एक ऐसा समाधान तैयार करता है जहाँ वेब और Http API परतें शारीरिक रूप से अलग हो जाती हैं। यदि जांच नहीं की जाती है, तो एक स्तरित समाधान बनाता है जो कम जटिल है और अधिकांश परिदृश्यों के लिए उपयुक्त है।",
"SeparateIdentityServerOption": "सर्वर एप्लिकेशन को दो अनुप्रयोगों में अलग करता है: पहला पहचान सर्वर के लिए है और दूसरा आपके सर्वर साइड HTTP एपीआई के लिए है।",
"UseslatestPreVersion": "नवीनतम पूर्व-रिलीज़ संस्करण का उपयोग करता है",
- "ReadTheDocumentation": "<स्पैन क्लास = \"टेक्स्ट-प्राइमरी\"> पढ़ें span> <स्पैन क्लास = \"टेक्स्ट-सक्सेस\"> डॉक्यूमेंटेशन span>",
+ "ReadTheDocumentation": "पढ़ेंदस्तावेज़ीकरण",
"Documentation": "प्रलेखन",
"GettingStartedTutorial": "स्टार्टिंग ट्यूटोरियल",
"ApplicationDevelopmentTutorial": "अनुप्रयोग विकास ट्यूटोरियल",
@@ -183,7 +183,7 @@
"InstallABPCLIInfo": "एबीपी सीएलआई एबीपी ढांचे के साथ एक नया समाधान शुरू करने का सबसे तेज़ तरीका है। कमांड लाइन विंडो का उपयोग करके ABP CLI स्थापित करें:",
"DifferentLevelOfNamespaces": "आप विभिन्न स्तरों के नामस्थानों का उपयोग कर सकते हैं; जैसे BookStore, Acme.BookStore या Acme.Retail.BookStore।",
"ABPCLIExamplesInfo": " नया strong> कमांड डेटाबेस प्रदाता के रूप में एंटिटी फ्रेमवर्क कोर strong> के साथ स्तरित MVC एप्लिकेशन strong> बनाता है। हालांकि, इसके पास अतिरिक्त विकल्प हैं। उदाहरण:",
- "SeeCliDocumentForMoreInformation": "अधिक विकल्पों के लिए ABP CLI दस्तावेज़ देखें या ऊपर \"डायरेक्ट डाउनलोड\" टैब चुनें।",
+ "SeeCliDocumentForMoreInformation": "अधिक विकल्पों के लिए ABP CLI दस्तावेज़ देखें या ऊपर \"डायरेक्ट डाउनलोड\" टैब चुनें।",
"Optional": "ऐच्छिक",
"LocalFrameworkRef": "फ्रेमवर्क पैकेज के लिए स्थानीय प्रोजेक्ट संदर्भ रखें।",
"BlobStoring": "ब्लॉब भंडारण",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/it.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/it.json
index e4cdc73bf2..35d86ceefb 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/it.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/it.json
@@ -155,7 +155,7 @@
"Code": "Codice",
"Result": "Risultato",
"SeeTheDocumentForMoreInformation": "Consulta il {0} documento per ulteriori informazioni",
- "IndexPageHeroSection": " open source Framework applicazione web per asp.net core ",
+ "IndexPageHeroSection": " open source Framework applicazione web per asp.net core ",
"UiFramework": "Framework dell'interfaccia utente",
"EmailAddress": "Indirizzo e-mail",
"Mobile": "Mobile",
@@ -175,7 +175,7 @@
"TieredOption": "Crea una soluzione a più livelli in cui i livelli API Web e Http sono fisicamente separati. Se non selezionata, crea una soluzione a più livelli meno complessa e adatta alla maggior parte degli scenari.",
"SeparateIdentityServerOption": "Separa il lato server in due applicazioni: la prima è per il server di identità e la seconda è per l'API HTTP lato server.",
"UseslatestPreVersion": "Utilizza l'ultima versione pre-rilascio",
- "ReadTheDocumentation": " Leggi La documentazione ",
+ "ReadTheDocumentation": " Leggi La documentazione ",
"Documentation": "Documentazione",
"GettingStartedTutorial": "Tutorial introduttivo",
"ApplicationDevelopmentTutorial": "Tutorial sullo sviluppo di applicazioni",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/tr.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/tr.json
index 84a0173273..0d02300061 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/tr.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/tr.json
@@ -218,8 +218,6 @@
"Surname": "Soyad",
"CompanyName": "Şirket adı",
"DoYouAgreePrivacyPolicy": "Şartlar & Koşulları ve Gizlilik Politikasını kabul ediyorum.",
- "VolosoftMarketingInformationMessage": "İşletmeler ve Organizasyonlar için çözümler ve diğer Volosoft ürün ve hizmetleri hakkında bilgi, ipucu ve teklifler almak istiyorum.",
- "VolosoftSharingInformationMessage": "Volosoft'un ürünlerimi seçkin ortaklarla paylaşmasını kabul ediyorum, böylece ilgili ortakların ürünleri ve hizmetleri hakkında ilgili bilgileri alabilirim.",
"Free": "Ücretsiz",
"DDDEBook": "DDD E-kitap",
"PracticalGuideForImplementingDDD": "Bu kitap ABP Framework ile birlikte Domain Driven Design'ın uygulanması için pratik bir kılavuz görevi görür.",
@@ -233,6 +231,8 @@
"WeWillSendYouADownloadLink": "{0} adresine email gönderilmiştir.",
"GoHome": "Anasayfaya Dön",
"InvalidFormInputs": "Lütfen formda belirtilen geçerli bilgileri yazınız.",
- "DDDBookEmailBody": "Teşekkürler. Kitabı indirmek için, buraya tıklayınız."
+ "DDDBookEmailBody": "Teşekkürler. Kitabı indirmek için, buraya tıklayınız.",
+ "SubscribeToNewsletter": "ABP.IO Platform'u ile ilgili yeni haberler, makaleler, teklifler ve daha fazlası gibi gelişmeler hakkında bilgi almak için bültene abone olun.",
+ "FirstEdition": "İlk Baskı"
}
}
\ No newline at end of file
diff --git a/docs/en/CLI.md b/docs/en/CLI.md
index f2e7df219b..829b9480c7 100644
--- a/docs/en/CLI.md
+++ b/docs/en/CLI.md
@@ -42,6 +42,7 @@ Here, the list of all available commands before explaining their details:
* **`login`**: Authenticates on your computer with your [abp.io](https://abp.io/) username and password.
* **`logout`**: Logouts from your computer if you've authenticated before.
* **`bundle`**: Generates script and style references for an ABP Blazor project.
+* **`install-libs`**: Install NPM Packages for MVC / Razor Pages and Blazor Server UI types.
### help
@@ -433,3 +434,18 @@ abp bundle [options]
`bundle` command reads the `appsettings.json` file inside the Blazor project for bundling options. For more details about managing style and script references in Blazor apps, see [Managing Global Scripts & Styles](UI/Blazor/Global-Scripts-Styles.md)
+### install-libs
+
+This command install NPM Packages for MVC / Razor Pages and Blazor Server UI types. Its **executing directory** or passed ```--working-directory``` parameter's directory must contain a project file(*.csproj).
+
+`install-libs` command reads the `abp.resourcemapping.js` file to manage package. For more details see [Client Side Package Management](UI/AspNetCore/Client-Side-Package-Management.md).
+
+Usage:
+
+````bash
+abp install-libs [options]
+````
+
+#### Options
+
+* ```--working-directory``` or ```-wd```: Specifies the working directory. This option is useful when executing directory doesn't contain a project file.
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2020-04-27-Use-Azure-Active-Directory-Authentication-for-MVC-Razor-Page-Applications/POST.md b/docs/en/Community-Articles/2020-04-27-Use-Azure-Active-Directory-Authentication-for-MVC-Razor-Page-Applications/POST.md
index 146d250d1f..b2c307bcb3 100644
--- a/docs/en/Community-Articles/2020-04-27-Use-Azure-Active-Directory-Authentication-for-MVC-Razor-Page-Applications/POST.md
+++ b/docs/en/Community-Articles/2020-04-27-Use-Azure-Active-Directory-Authentication-for-MVC-Razor-Page-Applications/POST.md
@@ -6,23 +6,21 @@ Adding Azure Active Directory is pretty straightforward in ABP framework. Couple
Two different **alternative approaches** for AzureAD integration will be demonstrated for better coverage.
-1. ~~**AddAzureAD**: This approach uses Microsoft [AzureAD UI nuget package](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.AzureAD.UI/) which is very popular when users search the web about how to integrate AzureAD to their web application.~~ Now marked **Obsolete** (see https://github.com/aspnet/Announcements/issues/439).
-2. **AddOpenIdConnect**: This approach uses default [OpenIdConnect](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.OpenIdConnect/) which can be used for not only AzureAD but for all OpenId connections.
+1. **AddOpenIdConnect**: This approach uses default [OpenIdConnect](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.OpenIdConnect/) which can be used for not only AzureAD but for all OpenId connections.
3. **AddMicrosoftIdentityWebAppAuthentication:** This approach uses newly introduced [Microsoft.Identity.Web nuget package](https://www.nuget.org/packages/Microsoft.Identity.Web/) to replace AddAzureAD.
+3. ~~**AddAzureAD**: This approach uses Microsoft [AzureAD UI nuget package](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.AzureAD.UI/) which is very popular when users search the web about how to integrate AzureAD to their web application.~~ Now marked **Obsolete** (see https://github.com/aspnet/Announcements/issues/439).
> There is **no difference** in functionality between these approaches. AddAzureAD is an abstracted way of OpenIdConnection ([source](https://github.com/dotnet/aspnetcore/blob/c56aa320c32ee5429d60647782c91d53ac765865/src/Azure/AzureAD/Authentication.AzureAD.UI/src/AzureADAuthenticationBuilderExtensions.cs#L122)) with predefined cookie settings.
>
> However there are key differences in integration to ABP applications because of default configurated signin schemes which will be explained below.
-## 1. AddAzureAD
+## 1. AddOpenIdConnect
-This approach uses the most common way to integrate AzureAD by using the [Microsoft AzureAD UI nuget package](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.AzureAD.UI/).
-
-If you choose this approach, you will need to install `Microsoft.AspNetCore.Authentication.AzureAD.UI` package to your **.Web** project. Also, since AddAzureAD extension uses [configuration binding](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-3.1#default-configuration), you need to update your appsettings.json file located in your **.Web** project.
+If you don't want to use an extra nuget package in your application, you can use the straight default [OpenIdConnect](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.OpenIdConnect/) which can be used for all OpenId connections including AzureAD external authentication.
-#### **Updating `appsettings.json`**
+You don't have to use `appsettings.json` configuration but it is a good practice to set AzureAD information in the `appsettings.json`.
-You need to add a new section to your `appsettings.json` which will be binded to configuration when configuring the `OpenIdConnectOptions`:
+To get the AzureAD information from `appsettings.json`, which will be used in `OpenIdConnectOptions` configuration, simply add a new section to `appsettings.json` located in your **.Web** project:
````json
"AzureAd": {
@@ -34,63 +32,90 @@ You need to add a new section to your `appsettings.json` which will be binded to
}
````
-> Important configuration here is the CallbackPath. This value must be the same with one of your Azure AD-> app registrations-> Authentication -> RedirectUri.
-
-Then, you need to configure the `OpenIdConnectOptions` to complete the integration.
-
-#### Configuring OpenIdConnectOptions
-
-In your **.Web** project, locate your **ApplicationWebModule** and modify `ConfigureAuthentication` method with the following:
+Then, In your **.Web** project; you can modify the `ConfigureAuthentication` method located in your **ApplicationWebModule** with the following:
````csharp
private void ConfigureAuthentication(ServiceConfigurationContext context, IConfiguration configuration)
{
- JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();
- JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Add("sub", ClaimTypes.NameIdentifier);
context.Services.AddAuthentication()
- .AddIdentityServerAuthentication(options =>
- {
- options.Authority = configuration["AuthServer:Authority"];
+ ... //Omitted other third party configurations
+ .AddOpenIdConnect("AzureOpenId", "Azure Active Directory OpenId", options =>
+ {
+ options.Authority = "https://login.microsoftonline.com/" + configuration["AzureAd:TenantId"] + "/v2.0/";
+ options.ClientId = configuration["AzureAd:ClientId"];
+ options.ResponseType = OpenIdConnectResponseType.CodeIdToken;
+ options.CallbackPath = configuration["AzureAd:CallbackPath"];
+ options.ClientSecret = configuration["AzureAd:ClientSecret"];
options.RequireHttpsMetadata = false;
- options.ApiName = "Acme.BookStore";
- })
- .AddAzureAD(options => configuration.Bind("AzureAd", options));
+ options.SaveTokens = true;
+ options.GetClaimsFromUserInfoEndpoint = true;
+ options.Scope.Add("email");
- context.Services.Configure(AzureADDefaults.OpenIdScheme, options =>
+ options.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");
+ });
+ }
+````
+
+> **Don't forget to:**
+>
+> * Add `options.Scope.Add("email");` since [default signin scheme is `AzureADOpenID`](https://github.com/dotnet/aspnetcore/blob/c56aa320c32ee5429d60647782c91d53ac765865/src/Azure/AzureAD/Authentication.AzureAD.UI/src/AzureADOpenIdConnectOptionsConfiguration.cs#L35).
+> * Add `options.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");`. Mapping this to [ClaimTypes.NameIdentifier](https://github.com/dotnet/runtime/blob/6d395de48ac718a913e567ae80961050f2a9a4fa/src/libraries/System.Security.Claims/src/System/Security/Claims/ClaimTypes.cs#L59) is important since default SignIn Manager behavior uses this claim type for external login information.
+
+
+
+And that's it, integration is completed. Keep on mind that you can connect any other external authentication providers.
+
+## 2. Alternative Approach: AddMicrosoftIdentityWebApp
+
+With .Net 5.0, AzureAd is marked [obsolete](https://github.com/dotnet/aspnetcore/issues/25807) and will not be supported in the near future. However its expanded functionality is available in [microsoft-identity-web](https://github.com/AzureAD/microsoft-identity-web/wiki) packages.
+
+Add (or replace with) the new nuget package Microsoft.Identity.Web nuget package](https://www.nuget.org/packages/Microsoft.Identity.Web/).
+
+In your **.Web** project; you update the `ConfigureAuthentication` method located in your **ApplicationWebModule** with the following while having the AzureAd appsettings section as defined before:
+
+````csharp
+private void ConfigureAuthentication(ServiceConfigurationContext context, IConfiguration configuration)
+ {
+ context.Services.AddAuthentication()
+ ... //Omitted other third party configurations
+ .AddMicrosoftIdentityWebApp(configuration.GetSection("AzureAd"));
+
+ context.Services.Configure(OpenIdConnectDefaults.AuthenticationScheme, options =>
{
- options.Authority = options.Authority + "/v2.0/";
+ options.Authority = "https://login.microsoftonline.com/" + configuration["AzureAd:TenantId"] + "/v2.0/";
options.ClientId = configuration["AzureAd:ClientId"];
- options.CallbackPath = configuration["AzureAd:CallbackPath"];
options.ResponseType = OpenIdConnectResponseType.CodeIdToken;
+ options.CallbackPath = configuration["AzureAd:CallbackPath"];
+ options.ClientSecret = configuration["AzureAd:ClientSecret"];
options.RequireHttpsMetadata = false;
-
- options.TokenValidationParameters.ValidateIssuer = false;
+ options.SaveTokens = false;
options.GetClaimsFromUserInfoEndpoint = true;
- options.SaveTokens = true;
- options.SignInScheme = IdentityConstants.ExternalScheme;
- options.Scope.Add("email");
+ options.SignInScheme = IdentityConstants.ExternalScheme;
+
+ options.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");
});
}
````
+And that's all to add new Microsoft-Identity-Web.
+
> **Don't forget to:**
>
-> * Add `.AddAzureAD(options => configuration.Bind("AzureAd", options))` after `.AddAuthentication()`. This binds your AzureAD appsettings and easy to miss out.
-> * Add `JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear()`. This will disable the default Microsoft claim type mapping.
-> * Add `JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Add("sub", ClaimTypes.NameIdentifier)`. Mapping this to [ClaimTypes.NameIdentifier](https://github.com/dotnet/runtime/blob/6d395de48ac718a913e567ae80961050f2a9a4fa/src/libraries/System.Security.Claims/src/System/Security/Claims/ClaimTypes.cs#L59) is important since default SignIn Manager behavior uses this claim type for external login information.
> * Add `options.SignInScheme = IdentityConstants.ExternalScheme` since [default signin scheme is `AzureADOpenID`](https://github.com/dotnet/aspnetcore/blob/c56aa320c32ee5429d60647782c91d53ac765865/src/Azure/AzureAD/Authentication.AzureAD.UI/src/AzureADOpenIdConnectOptionsConfiguration.cs#L35).
-> * Add `options.Scope.Add("email")` if you are using **v2.0** endpoint of AzureAD since v2.0 endpoint doesn't return the `email` claim as default. The [Account Module](https://docs.abp.io/en/abp/latest/Modules/Account) uses `email` claim to [register external users](https://github.com/abpframework/abp/blob/be32a55449e270d2d456df3dabdc91f3ffdd4fa9/modules/account/src/Volo.Abp.Account.Web/Pages/Account/Login.cshtml.cs#L215).
+> * Add `options.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");`. Mapping this to [ClaimTypes.NameIdentifier](https://github.com/dotnet/runtime/blob/6d395de48ac718a913e567ae80961050f2a9a4fa/src/libraries/System.Security.Claims/src/System/Security/Claims/ClaimTypes.cs#L59) is important since default SignIn Manager behavior uses this claim type for external login information.
-You are done and integration is completed.
+Keep in mind that [Microsoft-Identity-Web](https://github.com/AzureAD/microsoft-identity-web) is relatively new and keeps getting new enhancements, features and documentation.
-## 2. Alternative Approach: AddOpenIdConnect
+## 3. Obsolete Alternative Approach: AddAzureAD
-If you don't want to use an extra nuget package in your application, you can use the straight default [OpenIdConnect](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.OpenIdConnect/) which can be used for all OpenId connections including AzureAD external authentication.
+This approach uses the most common way to integrate AzureAD by using the [Microsoft AzureAD UI nuget package](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.AzureAD.UI/).
-You don't have to use `appsettings.json` configuration but it is a good practice to set AzureAD information in the `appsettings.json`.
+If you choose this approach, you will need to install `Microsoft.AspNetCore.Authentication.AzureAD.UI` package to your **.Web** project. Also, since AddAzureAD extension uses [configuration binding](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-3.1#default-configuration), you need to update your appsettings.json file located in your **.Web** project.
-To get the AzureAD information from `appsettings.json`, which will be used in `OpenIdConnectOptions` configuration, simply add a new section to `appsettings.json` located in your **.Web** project:
+#### **Updating `appsettings.json`**
+
+You need to add a new section to your `appsettings.json` which will be binded to configuration when configuring the `OpenIdConnectOptions`:
````json
"AzureAd": {
@@ -102,74 +127,49 @@ To get the AzureAD information from `appsettings.json`, which will be used in `O
}
````
-Then, In your **.Web** project; you can modify the `ConfigureAuthentication` method located in your **ApplicationWebModule** with the following:
-
-````csharp
-private void ConfigureAuthentication(ServiceConfigurationContext context, IConfiguration configuration)
- {
- JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();
- JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Add("sub", ClaimTypes.NameIdentifier);
-
- context.Services.AddAuthentication()
- .AddIdentityServerAuthentication(options =>
- {
- options.Authority = configuration["AuthServer:Authority"];
- options.RequireHttpsMetadata = false;
- options.ApiName = "BookStore";
- })
- .AddOpenIdConnect("AzureOpenId", "Azure Active Directory OpenId", options =>
- {
- options.Authority = "https://login.microsoftonline.com/" + configuration["AzureAd:TenantId"] + "/v2.0/";
- options.ClientId = configuration["AzureAd:ClientId"];
- options.ResponseType = OpenIdConnectResponseType.CodeIdToken;
- options.CallbackPath = configuration["AzureAd:CallbackPath"];
- options.RequireHttpsMetadata = false;
- options.SaveTokens = true;
- options.GetClaimsFromUserInfoEndpoint = true;
-
- options.Scope.Add("email");
- });
- }
-````
-
-And that's it, integration is completed. Keep on mind that you can connect any other external authentication providers.
-
-## 3. AddMicrosoftIdentityWebAppAuthentication
+> Important configuration here is the CallbackPath. This value must be the same with one of your Azure AD-> app registrations-> Authentication -> RedirectUri.
-With .Net 5.0, AzureAd is marked [obsolete](https://github.com/dotnet/aspnetcore/issues/25807) and will not be supported in the near future. However its expanded functionality is available in [microsoft-identity-web](https://github.com/AzureAD/microsoft-identity-web/wiki) packages.
+Then, you need to configure the `OpenIdConnectOptions` to complete the integration.
-Add (or replace with) the new nuget package Microsoft.Identity.Web nuget package](https://www.nuget.org/packages/Microsoft.Identity.Web/).
+#### Configuring OpenIdConnectOptions
-In your **.Web** project; you update the `ConfigureAuthentication` method located in your **ApplicationWebModule** with the following while having the AzureAd appsettings section as defined before:
+In your **.Web** project, locate your **ApplicationWebModule** and modify `ConfigureAuthentication` method with the following:
````csharp
private void ConfigureAuthentication(ServiceConfigurationContext context, IConfiguration configuration)
{
- JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();
- JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Add("sub", ClaimTypes.NameIdentifier);
context.Services.AddAuthentication()
- .AddIdentityServerAuthentication(options =>
- {
- options.Authority = configuration["AuthServer:Authority"];
- options.RequireHttpsMetadata = false;
- options.ApiName = "Acme.BookStore";
- });
-
- context.Services.AddMicrosoftIdentityWebAppAuthentication(
- configuration: configuration,
- configSectionName: "AzureAd",
- openIdConnectScheme:"AzureAD",
- cookieScheme:null);
+ ... //Omitted other third party configurations
+ .AddAzureAD(options => configuration.Bind("AzureAd", options));
+
+ context.Services.Configure(AzureADDefaults.OpenIdScheme, options =>
+ {
+ options.Authority = options.Authority + "/v2.0/";
+ options.ClientId = configuration["AzureAd:ClientId"];
+ options.CallbackPath = configuration["AzureAd:CallbackPath"];
+ options.ResponseType = OpenIdConnectResponseType.CodeIdToken;
+ options.RequireHttpsMetadata = false;
+
+ options.TokenValidationParameters.ValidateIssuer = false;
+ options.GetClaimsFromUserInfoEndpoint = true;
+ options.SaveTokens = true;
+ options.SignInScheme = IdentityConstants.ExternalScheme;
+
+ options.Scope.Add("email");
+
+ options.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");
+ });
}
````
-And that's all to add new Microsoft-Identity-Web.
-
> **Don't forget to:**
>
-> * Pass **cookieScheme** parameter as **null** or your [*GetExternalLoginInfoAsync* method will always return null](https://github.com/AzureAD/microsoft-identity-web/issues/133#).
+> * Add `.AddAzureAD(options => configuration.Bind("AzureAd", options))` after `.AddAuthentication()`. This binds your AzureAD appsettings and easy to miss out.
+> * Add `options.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");`. Mapping this to [ClaimTypes.NameIdentifier](https://github.com/dotnet/runtime/blob/6d395de48ac718a913e567ae80961050f2a9a4fa/src/libraries/System.Security.Claims/src/System/Security/Claims/ClaimTypes.cs#L59) is important since default SignIn Manager behavior uses this claim type for external login information.
+> * Add `options.SignInScheme = IdentityConstants.ExternalScheme` since [default signin scheme is `AzureADOpenID`](https://github.com/dotnet/aspnetcore/blob/c56aa320c32ee5429d60647782c91d53ac765865/src/Azure/AzureAD/Authentication.AzureAD.UI/src/AzureADOpenIdConnectOptionsConfiguration.cs#L35).
+> * Add `options.Scope.Add("email")` if you are using **v2.0** endpoint of AzureAD since v2.0 endpoint doesn't return the `email` claim as default. The [Account Module](https://docs.abp.io/en/abp/latest/Modules/Account) uses `email` claim to [register external users](https://github.com/abpframework/abp/blob/be32a55449e270d2d456df3dabdc91f3ffdd4fa9/modules/account/src/Volo.Abp.Account.Web/Pages/Account/Login.cshtml.cs#L215).
-Keep in mind that [Microsoft-Identity-Web](https://github.com/AzureAD/microsoft-identity-web) is relatively new and keeps getting new enhancements, features and documentation.
+You are done and integration is completed.
## The Source Code
@@ -247,3 +247,14 @@ You can find the source code of the completed example [here](https://github.com/
await Task.CompletedTask;
});
````
+
+* I get page not found error on redirection to **https://login.live.com/oauth20_authorize.srf?**!
+
+ * Probably you are trying to login with Microsoft account to Azure portal instead of the Azure AD account. Try azure AD user account for login instead of microsoft account. You can also check the answers for [this question](https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_dirservices-mso_o365b/cant-login-in-loginlivecom-with-a-ms-account-valid/6da991e6-9528-461a-9638-9c5680e95888) and [this question](https://docs.microsoft.com/en-us/answers/questions/34806/azure-ad-404-error-when-login-with-microsoft-accou.html) for more details.
+
+# May 2021 Update
+
+- **AddOpenIdConnect**: Removed `JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();` and added `sub` claim mapping in ClaimActions rather than global mapping.
+- Updated `AddMicrosoftIdentityWebAppAuthentication ` to `AddMicrosoftIdentityWebApp`.
+- Updated OpenIdConnect and AddMicrosoftIdentityWebApp configurations.
+- Obsolete approach moved to third place in the list.
diff --git a/docs/en/Community-Articles/2020-09-16-How-to-Setup-Azure-Active-Directory-and-Integrate-Abp-Angular-Application/POST.md b/docs/en/Community-Articles/2020-09-16-How-to-Setup-Azure-Active-Directory-and-Integrate-Abp-Angular-Application/POST.md
index c7f4f40917..a1c63529a2 100644
--- a/docs/en/Community-Articles/2020-09-16-How-to-Setup-Azure-Active-Directory-and-Integrate-Abp-Angular-Application/POST.md
+++ b/docs/en/Community-Articles/2020-09-16-How-to-Setup-Azure-Active-Directory-and-Integrate-Abp-Angular-Application/POST.md
@@ -23,20 +23,9 @@ This means your application will be using AzureAD user store for authentication.
Lets start with adding OpenId connection. Open the **HttpApiHostModule.cs** and update the **ConfigureAuthentication** method as below:
```csharp
-JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();
-JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Add("sub", ClaimTypes.NameIdentifier);
context.Services.AddAuthentication()
- .AddIdentityServerAuthentication(options =>
- {
- options.Authority = configuration["AuthServer:Authority"];
- options.RequireHttpsMetadata = false;
- options.ApiName = "NonTieredAngular";
- options.JwtBackChannelHandler = new HttpClientHandler()
- {
- ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator
- };
- })
+ ... //Omitted other third party configurations
.AddOpenIdConnect("AzureOpenId", "Azure AD OpenId", options =>
{
options.Authority = "https://login.microsoftonline.com/" + configuration["AzureAd:TenantId"] + "/v2.0/";
@@ -48,6 +37,8 @@ context.Services.AddAuthentication()
options.SaveTokens = true;
options.GetClaimsFromUserInfoEndpoint = true;
options.Scope.Add("email");
+
+ options.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");
});
```
@@ -58,10 +49,7 @@ public override void ConfigureServices(ServiceConfigurationContext context)
{
var hostingEnvironment = context.Services.GetHostingEnvironment();
var configuration = context.Services.GetConfiguration();
-
- JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();
- JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Add("sub", ClaimTypes.NameIdentifier);
-
+
context.Services.AddAuthentication()
.AddOpenIdConnect("AzureOpenId", "Azure AD OpenId", options =>
{
@@ -120,3 +108,8 @@ Next time you hit login, you should be seeing login screen enabled Azure AD like
* But I don't want my users to see default login screen. I want my users to login **only** from AzureAD.
* You can **mimic** this behaviour by customizing the login page and instantly trigger Azure AD provider click. For more info, you can check [this article](https://community.abp.io/articles/how-to-customize-the-login-page-for-mvc-razor-page-applications-9a40f3cd).
+
+# May 2021 Update
+
+- **AddOpenIdConnect**: Removed `JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();` and added `sub` claim mapping in ClaimActions rather than global mapping.
+- Updated OpenIdConnect configurations.
diff --git a/docs/en/Domain-Driven-Design-Implementation-Guide.md b/docs/en/Domain-Driven-Design-Implementation-Guide.md
index bf466e04c8..dc28845396 100644
--- a/docs/en/Domain-Driven-Design-Implementation-Guide.md
+++ b/docs/en/Domain-Driven-Design-Implementation-Guide.md
@@ -1,1982 +1,5 @@
# Implementing Domain Driven Design
-## Introduction
+This document has been packaged as a **free e-book** and can be downloaded from the following URL:
-This is a **practical guide** for implementing the Domain Driven Design (DDD). While the implementation details rely on the ABP Framework infrastructure, core concepts, principles and patterns are applicable in any kind of solution, even if it is not a .NET solution.
-
-### Goals
-
-The goals of this document are to
-
-* **Introduce and explain** the DDD architecture, concepts, principles, patterns and building blocks.
-* Explain the **layered architecture** & solution structure offered by the ABP Framework.
-* Introduce **explicit rules** to implement DDD patterns and best practices by giving **concrete examples**.
-* Show what **ABP Framework provides** you as the infrastructure for implementing DDD in a proper way.
-* And finally, provide **suggestions** based on software development **best practices** and our experiences to create a **maintainable codebase**.
-
-### Simple Code!
-
-> **Playing football** is very **simple**, but **playing simple football** is the **hardest thing** there is.
-> — Johan Cruyff
-
-If we take this famous quote for programming, we can say;
-
-> **Writing code** is very **simple**, but **writing simple code** is the **hardest thing** there is.
-> — ???
-
-In this document, we will introduce **simple rules**, those are **easy to implement**.
-
-Once your **application grows**, it will be **hard to follow** these rules. Sometimes you find **breaking rules** will save you time in a short term. However, the saved time in the short term will bring much **more time loss** in the middle and long term. Your code base becomes **complicated** and hard to maintain. Most of the business applications are **re-written** just because you **can't maintain** it anymore.
-
-If you **follow the rules and best practices**, your code base will be simpler and easier to maintain. Your application **reacts to changes** faster.
-
-## What is the Domain Driven Design?
-
-Domain-driven design (DDD) is an approach to software development for **complex** needs by connecting the implementation to an **evolving** model;
-
-DDD is suitable for **complex domains** and **large-scale** applications rather than simple CRUD applications. It focuses on the **core domain logic** rather than the infrastructure details. It helps to build a **flexible**, modular and **maintainable** code base.
-
-### OOP & SOLID
-
-Implementing DDD highly relies on the Object Oriented Programming (OOP) and [SOLID](https://en.wikipedia.org/wiki/SOLID) principles. Actually, it **implements** and **extends** these principles. So, a **good understanding** of OOP & SOLID helps you a lot while truly implementing the DDD.
-
-### DDD Layers & Clean Architecture
-
-There are four fundamental layers of a Domain Driven Based Solution;
-
-
-
-**Business Logic** places into two layers, the *Domain layer* and the *Application Layer*, while they contain different kinds of business logic;
-
-* **Domain Layer** implements the core, use-case independent business logic of the domain/system.
-* **Application Layer** implements the use cases of the application based on the domain. A use case can be thought as a user interaction on the User Interface (UI).
-* **Presentation Layer** contains the UI elements (pages, components) of the application.
-* **Infrastructure Layer** supports other layer by implementing the abstractions and integrations to 3rd-party library and systems.
-
-The same layering can be shown as the diagram below and known as the **Clean Architecture**, or sometimes the **Onion Architecture**:
-
-
-
-In the Clean Architecture, each layer only **depends on the layer directly inside it**. The most independent layer is shown in the most inner circle and it is the Domain Layer.
-
-### Core Building Blocks
-
-DDD mostly **focuses on the Domain & Application Layers** and ignores the Presentation and Infrastructure. They are seen as *details* and the business layers should not depend on them.
-
-That doesn't mean the Presentation and Infrastructure layers are not important. They are very important. UI frameworks and database providers have their own rules and best practices that you need to know and apply. However these are not in the topics of DDD.
-
-This section introduces the essential building blocks of the Domain & Application Layers.
-
-#### Domain Layer Building Blocks
-
-* **Entity**: An [Entity](Entities.md) is an object with its own properties (state, data) and methods that implements the business logic that is executed on these properties. An entity is represented by its unique identifier (Id). Two entity object with different Ids are considered as different entities.
-* **Value Object**: A [Value Object](Value-Objects.md) is another kind of domain object that is identified by its properties rather than a unique Id. That means two Value Objects with same properties are considered as the same object. Value objects are generally implemented as immutable and mostly are much simpler than the Entities.
-* **Aggregate & Aggregate Root**: An [Aggregate](Entities.md) is a cluster of objects (entities and value objects) bound together by an **Aggregate Root** object. The Aggregate Root is a specific type of an entity with some additional responsibilities.
-* **Repository** (interface): A [Repository](Repositories.md) is a collection-like interface that is used by the Domain and Application Layers to access to the data persistence system (the database). It hides the complexity of the DBMS from the business code. Domain Layer contains the `interface`s of the repositories.
-* **Domain Service**: A [Domain Service](Domain-Services.md) is a stateless service that implements core business rules of the domain. It is useful to implement domain logic that depends on multiple aggregate (entity) type or some external services.
-* **Specification**: A [Specification](Specifications.md) is used to define named, reusable and combinable filters for entities and other business objects.
-* **Domain Event**: A [Domain Event](Event-Bus.md) is a way of informing other services in a loosely coupled manner, when a domain specific event occurs.
-
-#### Application Layer Building Blocks
-
-* **Application Service**: An [Application Service](Application-Services.md) is a stateless service that implements use cases of the application. An application service typically gets and returns DTOs. It is used by the Presentation Layer. It uses and coordinates the domain objects to implement the use cases. A use case is typically considered as a Unit Of Work.
-* **Data Transfer Object (DTO)**: A [DTO](Data-Transfer-Objects.md) is a simple object without any business logic that is used to transfer state (data) between the Application and Presentation Layers.
-* **Unit of Work (UOW)**: A [Unit of Work](Unit-Of-Work.md) is an atomic work that should be done as a transaction unit. All the operations inside a UOW should be committed on success or rolled back on a failure.
-
-## Implementation: The Big Picture
-
-### Layering of a .NET Solution
-
-The picture below shows a Visual Studio Solution created using the ABP's [application startup template](Startup-Templates/Application.md):
-
-
-
-The solution name is `IssueTracking` and it consists of multiple projects. The solution is layered by considering **DDD principles** as well as **development** and **deployment** practicals. The sub sections below explains the projects in the solution;
-
-> Your solution structure may be slightly different if you choose a different UI or Database provider. However, the Domain and Application layers will be same and this is the essential point for the DDD perspective. See the [Application Startup Template](Startup-Templates/Application.md) document if you want to know more about the solution structure.
-
-#### The Domain Layer
-
-The Domain Layer is splitted into two projects;
-
-* `IssueTracking.Domain` is the **essential domain layer** that contains all the **building blocks** (entities, value objects, domain services, specifications, repository interfaces, etc.) introduced before.
-* `IssueTracking.Domain.Shared` is a thin project that contains some types those belong to the Domain Layer, but shared with all other layers. For example, it may contain some constants and `enum`s related to the Domain Objects but need to be **reused by other layers**.
-
-#### The Application Layer
-
-The Application Layer is also splitted into two projects;
-
-* `IssueTracking.Application.Contracts` contains the application service **interfaces** and the **DTO**s used by these interfaces. This project can be shared by the client applications (including the UI).
-* `IssueTracking.Application` is the **essential application layer** that **implements** the interfaces defined in the Contracts project.
-
-#### The Presentation Layer
-
-* `IssueTracking.Web` is an ASP.NET Core MVC / Razor Pages application for this example. This is the only executable application that serves the application and the APIs.
-
-> ABP Framework also supports different kind of UI frameworks including [Angular](UI/Angular/Quick-Start.md) and [Blazor](UI/Blazor/Overall.md). In these cases, the `IssueTracking.Web` doesn't exist in the solution. Instead, an `IssueTracking.HttpApi.Host` application will be in the solution to serve the HTTP APIs as a standalone endpoint to be consumed by the UI applications via HTTP API calls.
-
-#### The Remote Service Layer
-
-* `IssueTracking.HttpApi` project contains HTTP APIs defined by the solution. It typically contains MVC `Controller`s and related models, if available. So, you write your HTTP APIs in this project.
-
-> Most of the time, API Controllers are just wrappers around the Application Services to expose them to the remote clients. Since ABP Framework's [Automatic API Controller System](API/Auto-API-Controllers.md) **automatically configures and exposes your Application Services as API Controllers**, you typically don't create Controllers in this project. However, the startup solution includes it for the cases you need to manually create API controllers.
-
-* `IssueTracking.HttpApi.Client` project is useful when you have a C# application that needs to consume your HTTP APIs. Once the client application references this project, it can directly [inject](Dependency-Injection.md) & use the Application Services. This is possible by the help of the ABP Framework's [Dynamic C# Client API Proxies System](API/Dynamic-CSharp-API-Clients.md).
-
-> There is a Console Application in the `test` folder of the solution, named `IssueTracking.HttpApi.Client.ConsoleTestApp`. It simply uses the `IssueTracking.HttpApi.Client` project to consume the APIs exposed by the application. It is just a demo application and you can safely delete it. You can even delete the `IssueTracking.HttpApi.Client` project if you think that you don't need to them.
-
-#### The Infrastructure Layer
-
-In a DDD implementation, you may have a single Infrastructure project to implement all the abstractions and integrations, or you may have different projects for each dependency.
-
-We suggest a balanced approach; Create separate projects for main infrastructure dependencies (like Entity Framework Core) and a common infrastructure project for other infrastructure.
-
-ABP's startup solution has two projects for the Entity Framework Core integration;
-
-* `IssueTracking.EntityFrameworkCore` is the essential integration package for the EF Core. Your application's `DbContext`, database mappings, implementations of the repositories and other EF Core related stuff are located here.
-* `IssueTracking.EntityFrameworkCore.DbMigrations` is a special project to manage the Code First database migrations. There is a separate `DbContext` in this project to track the migrations. You typically don't touch this project much except you need to create a new database migration or add an [application module](Modules/Index.md) that has some database tables and naturally requires to create a new database migration.
-
-> You may wonder why there are two projects for the EF Core. It is mostly related to [modularity](Module-Development-Basics.md). Each module has its own independent `DbContext` and your application has also one `DbContext`. `DbMigrations` project contains a **union** of the modules to track and apply a **single migration path**. While most of the time you don't need to know it, you can see the [EF Core migrations](Entity-Framework-Core-Migrations.md) document for more information.
-
-#### Other Projects
-
-There is one more project, `IssueTracking.DbMigrator`, that is a simple Console Application that **migrates** the database schema and **[seeds](Data-Seeding.md) the initial** data when you execute it. It is a useful **utility application** that you can use it in development as well as in production environment.
-
-### Dependencies of the Projects in the Solution
-
-The diagram below shows the essential dependencies (project references) between the projects in the solution (`IssueTracking.` part is not shown to be simple)
-
-
-
-The projects have been explained before. Now, we can explain the reasons of the dependencies;
-
-* `Domain.Shared` is the project that all other projects directly or indirectly depend on. So, all the types in this project are available to all projects.
-* `Domain` only depends on the `Domain.Shared` because it is already a (shared) part of the domain. For example, an `IssueType` enum in the `Domain.Shared` can be used by an `Issue` entity in the `Domain` project.
-* `Application.Contracts` depends on the `Domain.Shared`. In this way, you can reuse these types in the DTOs. For example, the same `IssueType` enum in the `Domain.Shared` can be used by a `CreateIssueDto` as a property.
-* `Application` depends on the `Application.Contracts` since it implements the Application Service interfaces and uses the DTOs inside it. It also depends on the `Domain` since the Application Services are implemented using the Domain Objects defined inside it.
-* `EntityFrameworkCore` depends on the `Domain` since it maps the Domain Objects (entities and value types) to database tables (as it is an ORM) and implements the repository interfaces defined in the `Domain`.
-* `HttpApi` depends on the `Application.Contracts` since the Controllers inside it inject and use the Application Service interfaces as explained before.
-* `HttpApi.Client` depends on the `Application.Contracts` since it can consume the Application Services as explained before.
-* `Web` depends on the `HttpApi` since it serves the HTTP APIs defined inside it. Also, in this way, it indirectly depends on the `Application.Contracts` project to consume the Application Services in the Pages/Components.
-
-#### Dashed Dependencies
-
-When you investigate the solution, you will see two more dependencies shown with the dashed lines in the figure above. `Web` project depends on the `Application` and `EntityFrameworkCore` projects which *theoretically* should not be like that but actually it is.
-
-This is because the `Web` is the final project that runs and hosts the application and the **application needs the implementations of the Application Services and the Repositories** while running.
-
-This design decision potentially allows you to use Entities and EF Core objects in the Presentation Layer which **should be strictly avoided**. However, we find the alternative designs over complicated. Here, two of the alternatives if you want to remove this dependency;
-
-* Convert `Web` project to a razor class library and create a new project, like `Web.Host`, that depends on the `Web`, `Application` and `EntityFrameworkCore` projects and hosts the application. You don't write any UI code here, but use **only for hosting**.
-* Remove `Application` and `EntityFrameworkCore` dependencies from the `Web` project and load their assemblies on application initialization. You can use ABP's [Plug-In Modules](PlugIn-Modules.md) system for that purpose.
-
-### Execution Flow a DDD Based Application
-
-The figure below shows a typical request flow for a web application that has been developed based on DDD patterns.
-
-
-
-* The request typically begins with a user interaction on the UI (a *use case*) that causes an HTTP request to the server.
-* An MVC Controller or a Razor Page Handler in the Presentation Layer (or in the Distributed Services Layer) handles the request and can perform some cross cutting concerns in this stage ([Authorization](Authorization.md), [Validation](Validation.md), [Exception Handling](Exception-Handling.md), etc.). A Controller/Page injects the related Application Service interface and calls its method(s) by sending and receiving DTOs.
-* The Application Service uses the Domain Objects (Entities, Repository interfaces, Domain Services, etc.) to implement the *use case*. Application Layer implements some cross cutting concerns (Authorization, Validation, etc.). An Application Service method should be a [Unit Of Work](Unit-Of-Work.md). That means it should be atomic.
-
-Most of the cross cutting concerns are **automatically and conventionally implemented by the ABP Framework** and you typically don't need to write code for them.
-
-### Common Principles
-
-Before going into details, let's see some overall DDD principles;
-
-#### Database Provider / ORM Independence
-
-The domain and the application layers should be ORM / Database Provider agnostic. They should only depend on the Repository interfaces and the Repository interfaces don't use any ORM specific objects.
-
-Here, the main reasons of this principle;
-
-1. To make your domain/application **infrastructure independent** since the infrastructure may change in the future or you may need to support a second database type later.
-2. To make your domain/application **focus on the business code** by hiding the infrastructure details behind the repositories.
-3. To make your **automated tests** easier since you can mock the repositories in this case.
-
-> As a respect to this principle, none of the projects in the solution has reference to the `EntityFrameworkCore` project, except the startup application.
-
-##### Discussion About the Database Independence Principle
-
-Especially, the **reason 1** deeply effects your domain **object design** (especially, the entity relations) and **application code**. Assume that you are using [Entity Framework Core](Entity-Framework-Core.md) with a relational database. If you are willing to make your application switchable to [MongoDB](MongoDB.md) later, you can't use some very **useful EF Core features**. Examples;
-
-* You can't assume [Change Tracking](https://docs.microsoft.com/en-us/ef/core/querying/tracking) since MongoDB provider can't do it. So, you always need to explicitly update the changed entities.
-* You can't use [Navigation Properties](https://docs.microsoft.com/en-us/ef/core/modeling/relationships) (or Collections) to other Aggregates in your entities since this is not possible for a Document Database. See the "Rule: Reference Other Aggregates Only By Id" section for more info.
-
-If you think such features are **important** for you and you **will never stray** from the EF Core, we believe that it is worth **stretching this principle**. We still suggest to use the repository pattern to hide the infrastructure details. But you can assume that you are using EF Core while designing your entity relations and writing your application code. You can even reference to the EF Core NuGet Package from your application layer to be able to directly use the asynchronous LINQ extension methods, like `ToListAsync()` (see the *IQueryable & Async Operations* section in the [Repositories](Repositories.md) document for more info).
-
-#### Presentation Technology Agnostic
-
-The presentation technology (UI Framework) is one of the most changed parts of a real world application. It is very important to design the **Domain and Application Layers** to be completely **unaware** of the presentation technology/framework. This principle is relatively easy to implement and ABP's startup template makes it even easier.
-
-In some cases, you may need to have **duplicate logic** in the application and presentation layers. For example, you may need to duplicate the **validation** and **authorization** checks in both layers. The checks in the UI layer is mostly for **user experience** while checks in the application and domain layers are for **security and data integrity**. That's perfectly normal and necessary.
-
-#### Focus on the State Changes, Not Reporting
-
-DDD focuses on how the domain objects **changes and interactions**; How to create an entity and change its properties by preserving the data **integrity/validity** and implementing the **business rules**.
-
-DDD **ignores reporting** and mass querying. That doesn't mean they are not important. If your application doesn't have fancy dashboards and reports, who would use it? However, reporting is another topic. You typically want to use the full power of the SQL Server or even use a separate data source (like ElasticSearch) for reporting purpose. You will write optimized queries, create indexes and even stored procedures(!). You are free to do all these things as long as you don't infect them into your business logic.
-
-## Implementation: The Building Blocks
-
-This is the essential part of this guide. We will introduce and explain some **explicit rules** with examples. You can follow these rules and apply in your solution while implementing the Domain Driven Design.
-
-### The Example Domain
-
-The examples will use some concepts those are used by GitHub, like `Issue`, `Repository`, `Label` and `User`, you are already familiar with. The figure below shows some of the aggregates, aggregate roots, entities, value object and the relations between them:
-
-
-
-**Issue Aggregate** consists of an `Issue` Aggregate Root that contains `Comment` and `IssueLabel` collections. Other aggregates are shown as simple since we will focus on the Issue Aggregate:
-
-
-
-### Aggregates
-
-As said before, an [Aggregate](Entities.md) is a cluster of objects (entities and value objects) bound together by an Aggregate Root object. This section will introduce the principles and rules related to the Aggregates.
-
-> We refer the term *Entity* both for *Aggregate Root* and *sub-collection entities* unless we explicitly write *Aggregate Root* or *sub-collection entity*.
-
-#### Aggregate / Aggregate Root Principles
-
-##### Business Rules
-
-Entities are responsible to implement the business rules related to the properties of their own. The *Aggregate Root Entities* are also responsible for their sub-collection entities.
-
-An aggregate should maintain its self **integrity** and **validity** by implementing domain rules and constraints. That means, unlike the DTOs, Entities have **methods to implement some business logic**. Actually, we should try to implement business rules in the entities wherever possible.
-
-##### Single Unit
-
-An aggregate is **retrieved and saved as a single unit**, with all the sub-collections and properties. For example, if you want to add a `Comment` to an `Issue`, you need to;
-
-* Get the `Issue` from database with including all the sub-collections (`Comment`s and `IssueLabel`s).
-* Use methods on the `Issue` class to add a new comment, like `Issue.AddComment(...);`.
-* Save the `Issue` (with all sub-collections) to the database as a single database operation (update).
-
-That may seem strange to the developers used to work with **EF Core & Relational Databases** before. Getting the `Issue` with all details seems **unnecessary and inefficient**. Why don't we just execute an SQL `Insert` command to database without querying any data?
-
-The answer is that we should **implement the business** rules and preserve the data **consistency** and **integrity** in the **code**. If we have a business rule like "*Users can not comment on the locked issues*", how can we check the `Issue`'s lock state without retrieving it from the database? So, we can execute the business rules only if the related objects available in the application code.
-
-On the other hand, **MongoDB** developers will find this rule very natural. In MongoDB, an aggregate object (with sub-collections) is saved in a **single collection** in the database (while it is distributed into several tables in a relational database). So, when you get an aggregate, all the sub-collections are already retrieved as a part of the query, without any additional configuration.
-
-ABP Framework helps to implement this principle in your applications.
-
-**Example: Add a comment to an issue**
-
-````csharp
-public class IssueAppService : ApplicationService, IIssueAppService
-{
- private readonly IRepository _issueRepository;
-
- public IssueAppService(IRepository issueRepository)
- {
- _issueRepository = issueRepository;
- }
-
- [Authorize]
- public async Task CreateCommentAsync(CreateCommentDto input)
- {
- var issue = await _issueRepository.GetAsync(input.IssueId);
- issue.AddComment(CurrentUser.GetId(), input.Text);
- await _issueRepository.UpdateAsync(issue);
- }
-}
-````
-
-`_issueRepository.GetAsync` method retrieves the `Issue` with all details (sub-collections) as a single unit by default. While this works out of the box for MongoDB, you need to configure your aggregate details for the EF Core. But, once you configure, repositories automatically handle it. `_issueRepository.GetAsync` method gets an optional parameter, `includeDetails`, that you can pass `false` to disable this behavior when you need it.
-
-> See the *Loading Related Entities* section of the [EF Core document](Entity-Framework-Core.md) for the configuration and alternative scenarios.
-
-`Issue.AddComment` gets a `userId` and comment `text`, implements the necessary business rules and adds the comment to the Comments collection of the `Issue`.
-
-Finally, we use `_issueRepository.UpdateAsync` to save changes to the database.
-
-> EF Core has a **change tracking** feature. So, you actually don't need to call `_issueRepository.UpdateAsync`. It will be automatically saved thanks to ABP's Unit Of Work system that automatically calls `DbContext.SaveChanges()` at the end of the method. However, for MongoDB, you need to explicitly update the changed entity.
->
-> So, if you want to write your code Database Provider independent, you should always call the `UpdateAsync` method for the changed entities.
-
-##### Transaction Boundary
-
-An aggregate is generally considered as a transaction boundary. If a use case works with a single aggregate, reads and saves it as a single unit, all the changes made to the aggregate objects are saved together as an atomic operation and you don't need to an explicit database transaction.
-
-However, in real life, you may need to change **more than one aggregate instances** in a single use case and you need to use database transactions to ensure **atomic update** and **data consistency**. Because of that, ABP Framework uses an explicit database transaction for a use case (an application service method boundary). See the [Unit Of Work](Unit-Of-Work.md) documentation for more info.
-
-##### Serializability
-
-An aggregate (with the root entity and sub-collections) should be serializable and transferrable on the wire as a single unit. For example, MongoDB serializes the aggregate to JSON document while saving to the database and deserializes from JSON while reading from the database.
-
-> This requirement is not necessary when you use relational databases and ORMs. However, it is an important practice of Domain Driven Design.
-
-The following rules will already bring the serializability.
-
-#### Aggregate / Aggregate Root Rules & Best Practices
-
-The following rules ensures implementing the principles introduced above.
-
-##### Reference Other Aggregates Only By Id
-
-The first rule says an Aggregate should reference to other aggregates only by their Id. That means you can not add navigation properties to other aggregates.
-
-* This rule makes it possible to implement the serializability principle.
-* It also prevents different aggregates manipulate each other and leaking business logic of an aggregate to one another.
-
-You see two aggregate roots, `GitRepository` and `Issue` in the example below;
-
-
-
-* `GitRepository` should not have a collection of the `Issue`s since they are different aggregates.
-* `Issue` should not have a navigation property for the related `GitRepository` since it is a different aggregate.
-* `Issue` can have `RepositoryId` (as a `Guid`).
-
-So, when you have an `Issue` and need to have `GitRepository` related to this issue, you need to explicitly query it from database by the `RepositoryId`.
-
-###### For EF Core & Relational Databases
-
-In MongoDB, it is naturally not suitable to have such navigation properties/collections. If you do that, you find a copy of the destination aggregate object in the database collection of the source aggregate since it is being serialized to JSON on save.
-
-However, EF Core & relational database developers may find this restrictive rule unnecessary since EF Core can handle it on database read and write. We see this an important rule that helps to **reduce the complexity** of the domain prevents potential problems and we strongly suggest to implement this rule. However, if you think it is practical to ignore this rule, see the *Discussion About the Database Independence Principle* section above.
-
-##### Keep Aggregates Small
-
-One good practice is to keep an aggregate simple and small. This is because an aggregate will be loaded and saved as a single unit and reading/writing a big object has performance problems. See the example below:
-
-
-
-Role aggregate has a collection of `UserRole` value objects to track the users assigned for this role. Notice that `UserRole` is not another aggregate and it is not a problem for the rule *Reference Other Aggregates Only By Id*. However, it is a problem in practical. A role may be assigned to thousands (even millions) of users in a real life scenario and it is a significant performance problem to load thousands of items whenever you query a `Role` from database (remember: Aggregates are loaded by their sub-collections as a single unit).
-
-On the other hand, `User` may have such a `Roles` collection since a user doesn't have much roles in practical and it can be useful to have a list of roles while you are working with a User Aggregate.
-
-If you think carefully, there is one more problem when Role and User both have the list of relation when use a **non-relational database, like MongoDB**. In this case, the same information is duplicated in different collections and it will be hard to maintain data consistency (whenever you add an item to `User.Roles`, you need to add it to `Role.Users` too).
-
-So, determine your aggregate boundaries and size based on the following considerations;
-
-* Objects used together.
-* Query (load/save) performance and memory consumption.
-* Data integrity, validity and consistency.
-
-In practical;
-
-* Most of the aggregate roots will **not have sub-collections**.
-* A sub-collection should not have more than **100-150 items** inside it at the most case. If you think a collection potentially can have more items, don't define the collection as a part of the aggregate and consider to extract another aggregate root for the entity inside the collection.
-
-##### Primary Keys of the Aggregate Roots / Entities
-
-* An aggregate root typically has a single `Id` property for its identifier (Primark Key: PK). We prefer `Guid` as the PK of an aggregate root entity (see the [Guid Genertation document](Guid-Generation.md) to learn why).
-* An entity (that's not the aggregate root) in an aggregate can use a composite primary key.
-
-For example, see the Aggregate root and the Entity below:
-
-
-
-* `Organization` has a `Guid` identifier (`Id`).
-* `OrganizationUser` is a sub-collection of an `Organization` and has a composite primary key consists of the `OrganizationId` and `UserId`.
-
-That doesn't mean sub-collection entities should always have composite PKs. They may have single `Id` properties when it's needed.
-
-> Composite PKs are actually a concept of relational databases since the sub-collection entities have their own tables and needs to a PK. On the other hand, for example, in MongoDB you don't need to define PK for the sub-collection entities at all since they are stored as a part of the aggregate root.
-
-##### Constructors of the Aggregate Roots / Entities
-
-The constructor is located where the lifecycle of an entity begins. There are a some responsibilities of a well designed constructor:
-
-* Gets the **required entity properties** as parameters to **create a valid entity**. Should force to pass only for the required parameters and may get non-required properties as optional parameters.
-* **Checks validity** of the parameters.
-* Initializes **sub-collections**.
-
-**Example: `Issue` (Aggregate Root) constructor**
-
-````csharp
-using System;
-using System.Collections.Generic;
-using System.Collections.ObjectModel;
-using Volo.Abp;
-using Volo.Abp.Domain.Entities;
-
-namespace IssueTracking.Issues
-{
- public class Issue : AggregateRoot
- {
- public Guid RepositoryId { get; set; }
- public string Title { get; set; }
- public string Text { get; set; }
- public Guid? AssignedUserId { get; set; }
- public bool IsClosed { get; set; }
- public IssueCloseReason? CloseReason { get; set; } //enum
-
- public ICollection Labels { get; set; }
-
- public Issue(
- Guid id,
- Guid repositoryId,
- string title,
- string text = null,
- Guid? assignedUserId = null
- ) : base(id)
- {
- RepositoryId = repositoryId;
- Title = Check.NotNullOrWhiteSpace(title, nameof(title));
-
- Text = text;
- AssignedUserId = assignedUserId;
-
- Labels = new Collection();
- }
-
- private Issue() { /* for deserialization & ORMs */ }
- }
-}
-````
-
-* `Issue` class properly **forces to create a valid entity** by getting minimum required properties in its constructor as parameters.
-* The constructor **validates** the inputs (`Check.NotNullOrWhiteSpace(...)` throws `ArgumentException` if the given value is empty).
-* It **initializes the sub-collections**, so you don't get a null reference exception when you try to use the `Labels` collection after creating the `Issue`.
-* The constructor also **takes the `id`** and passes to the `base` class. We don't generate `Guid`s inside the constructor to be able to delegate this responsibility to another service (see [Guid Generation](Guid-Generation.md)).
-* Private **empty constructor** is necessary for ORMs. We made it `private` to prevent accidently using it in our own code.
-
-> See the [Entities](Entities.md) document to learn more about creating entities with the ABP Framework.
-
-##### Entity Property Accessors & Methods
-
-The example above may seem strange to you! For example, we force to pass a non-null `Title` in the constructor. However, the developer may then set the `Title` property to `null` without any control. This is because the example code above just focuses on the constructor.
-
-If we declare all the properties with **public setters** (like the example `Issue` class above), we can't force **validity** and **integrity** of the entity in its lifecycle. So;
-
-* Use **private setter** for a property when you need to perform any **logic** while setting that property.
-* Define public methods to manipulate such properties.
-
-**Example: Methods to change the properties in a controlled way**
-
-````csharp
-using System;
-using Volo.Abp;
-using Volo.Abp.Domain.Entities;
-
-namespace IssueTracking.Issues
-{
- public class Issue : AggregateRoot
- {
- public Guid RepositoryId { get; private set; } //Never changes
- public string Title { get; private set; } //Needs validation
- public string Text { get; set; } //No validation
- public Guid? AssignedUserId { get; set; } //No validation
- public bool IsClosed { get; private set; } //Should be changed with CloseReason
- public IssueCloseReason? CloseReason { get; private set; } //Should be changed with IsClosed
-
- //...
-
- public void SetTitle(string title)
- {
- Title = Check.NotNullOrWhiteSpace(title, nameof(title));
- }
-
- public void Close(IssueCloseReason reason)
- {
- IsClosed = true;
- CloseReason = reason;
- }
-
- public void ReOpen()
- {
- IsClosed = false;
- CloseReason = null;
- }
- }
-}
-````
-
-* `RepositoryId` setter made private and there is no way to change it after creating an `Issue` because this is what we want in this domain: An issue can't be moved to another repository.
-* `Title` setter made private and `SetTitle` method has been created if you want to change it later in a controlled way.
-* `Text` and `AssignedUserId` has public setters since there is no restriction on them. They can be null or any other value. We think it is unnecessary to define separate methods to set them. If we need later, we can add methods and make the setters private. Breaking changes are not problem in the domain layer since the domain layer is an internal project, it is not exposed to clients.
-* `IsClosed` and `IssueCloseReason` are pair properties. Defined `Close` and `ReOpen` methods to change them together. In this way, we prevent to close an issue without any reason.
-
-##### Business Logic & Exceptions in the Entities
-
-When you implement validation and business logic in the entities, you frequently need to manage the exceptional cases. In these cases;
-
-* Create **domain specific exceptions**.
-* **Throw these exceptions** in the entity methods when necessary.
-
-**Example**
-
-````csharp
-public class Issue : AggregateRoot
-{
- //...
-
- public bool IsLocked { get; private set; }
- public bool IsClosed { get; private set; }
- public IssueCloseReason? CloseReason { get; private set; }
-
- public void Close(IssueCloseReason reason)
- {
- IsClosed = true;
- CloseReason = reason;
- }
-
- public void ReOpen()
- {
- if (IsLocked)
- {
- throw new IssueStateException(
- "Can not open a locked issue! Unlock it first."
- );
- }
-
- IsClosed = false;
- CloseReason = null;
- }
-
- public void Lock()
- {
- if (!IsClosed)
- {
- throw new IssueStateException(
- "Can not open a locked issue! Unlock it first."
- );
- }
-
- IsLocked = true;
- }
-
- public void Unlock()
- {
- IsLocked = false;
- }
-}
-````
-
-There are two business rules here;
-
-* A locked issue can not be re-opened.
-* You can not lock an open issue.
-
-`Issue` class throws an `IssueStateException` in these cases to force the business rules:
-
-````csharp
-using System;
-
-namespace IssueTracking.Issues
-{
- public class IssueStateException : Exception
- {
- public IssueStateException(string message)
- : base(message)
- {
-
- }
- }
-}
-````
-
-There are two potential problems of throwing such exceptions;
-
-1. In case of such an exception, should the **end user** see the exception (error) message? If so, how do you **localize** the exception message? You can not use the [localization](Localization.md) system, because you can't inject and use `IStringLocalizer` in the entities.
-2. For a web application or HTTP API, what **HTTP Status Code** should return to the client?
-
-ABP's [Exception Handling](Exception-Handling.md) system solves these and similar problems.
-
-**Example: Throwing a business exception with code**
-
-````csharp
-using Volo.Abp;
-
-namespace IssueTracking.Issues
-{
- public class IssueStateException : BusinessException
- {
- public IssueStateException(string code)
- : base(code)
- {
-
- }
- }
-}
-````
-
-* `IssueStateException` class inherits the `BusinessException` class. ABP returns 403 (forbidden) HTTP Status code by default (instead of 500 - Internal Server Error) for the exceptions derived from the `BusinessException`.
-* The `code` is used as a key in the localization resource file to find the localized message.
-
-Now, we can change the `ReOpen` method as shown below:
-
-````csharp
-public void ReOpen()
-{
- if (IsLocked)
- {
- throw new IssueStateException("IssueTracking:CanNotOpenLockedIssue");
- }
-
- IsClosed = false;
- CloseReason = null;
-}
-````
-
-> Use constants instead of magic strings.
-
-And add an entry to the localization resource like below:
-
-````json
-"IssueTracking:CanNotOpenLockedIssue": "Can not open a locked issue! Unlock it first."
-````
-
-* When you throw the exception, ABP automatically uses this localized message (based on the current language) to show to the end user.
-* The exception code (`IssueTracking:CanNotOpenLockedIssue` here) is also sent to the client, so it may handle the error case programmatically.
-
-> For this example, you could directly throw `BusinessException` instead of defining a specialized `IssueStateException`. The result will be same. See the [exception handling document](Exception-Handling.md) for all the details.
-
-##### Business Logic in Entities Requiring External Services
-
-It is simple to implement a business rule in an entity method when the business logic only uses the properties of that entity. What if the business logic requires to **query database** or **use any external services** that should be resolved from the [dependency injection](Dependency-Injection.md) system. Remember; **Entities can not inject services!**
-
-There are two common ways of implementing such a business logic:
-
-* Implement the business logic on an entity method and **get external dependencies as parameters** of the method.
-* Create a **Domain Service**.
-
-Domain Services will be explained later. But, now let's see how it can be implemented in the entity class.
-
-**Example: Business Rule: Can not assign more than 3 open issues to a user concurrently**
-
-````csharp
-public class Issue : AggregateRoot
-{
- //...
- public Guid? AssignedUserId { get; private set; }
-
- public async Task AssignToAsync(AppUser user, IUserIssueService userIssueService)
- {
- var openIssueCount = await userIssueService.GetOpenIssueCountAsync(user.Id);
-
- if (openIssueCount >= 3)
- {
- throw new BusinessException("IssueTracking:ConcurrentOpenIssueLimit");
- }
-
- AssignedUserId = user.Id;
- }
-
- public void CleanAssignment()
- {
- AssignedUserId = null;
- }
-}
-````
-
-* `AssignedUserId` property setter made private. So, the only way to change it to use the `AssignToAsync` and `CleanAssignment` methods.
-* `AssignToAsync` gets an `AppUser` entity. Actually, it only uses the `user.Id`, so you could get a `Guid` value, like `userId`. However, this way ensures that the `Guid` value is `Id` of an existing user and not a random `Guid` value.
-* `IUserIssueService` is an arbitrary service that is used to get open issue count for a user. It's the responsibility of the code part (that calls the `AssignToAsync`) to resolve the `IUserIssueService` and pass here.
-* `AssignToAsync` throws exception if the business rule doesn't meet.
-* Finally, if everything is correct, `AssignedUserId` property is set.
-
-This method perfectly guarantees to apply the business logic when you want to assign an issue to a user. However, it has some problems;
-
-* It makes the entity class **depending on an external service** which makes the entity **complicated**.
-* It makes **hard to use** the entity. The code that uses the entity now needs to inject `IUserIssueService` and pass to the `AssignToAsync` method.
-
-An alternative way of implementing this business logic is to introduce a **Domain Service**, which will be explained later.
-
-### Repositories
-
-A [Repository](Repositories.md) is a collection-like interface that is used by the Domain and Application Layers to access to the data persistence system (the database) to read and write the Business Objects, generally the Aggregates.
-
-Common Repository principles are;
-
-* Define a repository **interface in the Domain Layer** (because it is used in the Domain and Application Layers), **implement in the Infrastructure Layer** (*EntityFrameworkCore* project in the startup template).
-* **Do not include business logic** inside the repositories.
-* Repository interface should be **database provider / ORM independent**. For example, do not return a `DbSet` from a repository method. `DbSet` is an object provided by the EF Core.
-* **Create repositories for aggregate roots**, not for all entities. Because, sub-collection entities (of an aggregate) should be accessed over the aggregate root.
-
-#### Do Not Include Domain Logic in Repositories
-
-While this rule seems obvious at the beginning, it is easy to leak business logic into repositories.
-
-**Example: Get inactive issues from a repository**
-
-````csharp
-using System;
-using System.Collections.Generic;
-using System.Threading.Tasks;
-using Volo.Abp.Domain.Repositories;
-
-namespace IssueTracking.Issues
-{
- public interface IIssueRepository : IRepository
- {
- Task> GetInActiveIssuesAsync();
- }
-}
-````
-
-`IIssueRepository` extends the standard `IRepository<...>` interface by adding a `GetInActiveIssuesAsync` method. This repository works with such an `Issue` class:
-
-````csharp
-public class Issue : AggregateRoot, IHasCreationTime
-{
- public bool IsClosed { get; private set; }
- public Guid? AssignedUserId { get; private set; }
- public DateTime CreationTime { get; private set; }
- public DateTime? LastCommentTime { get; private set; }
- //...
-}
-````
-
-(the code shows only the properties we need for this example)
-
-The rule says the repository shouldn't know the business rules. The question here is "**What is an inactive issue**? Is it a business rule definition?"
-
-Let's see the implementation to understand it:
-
-````csharp
-using System;
-using System.Collections.Generic;
-using System.Linq;
-using System.Threading.Tasks;
-using IssueTracking.EntityFrameworkCore;
-using Microsoft.EntityFrameworkCore;
-using Volo.Abp.Domain.Repositories.EntityFrameworkCore;
-using Volo.Abp.EntityFrameworkCore;
-
-namespace IssueTracking.Issues
-{
- public class EfCoreIssueRepository :
- EfCoreRepository,
- IIssueRepository
- {
- public EfCoreIssueRepository(
- IDbContextProvider dbContextProvider)
- : base(dbContextProvider)
- {
- }
-
- public async Task> GetInActiveIssuesAsync()
- {
- var daysAgo30 = DateTime.Now.Subtract(TimeSpan.FromDays(30));
-
- var dbSet = await GetDbSetAsync();
- return await dbSet.Where(i =>
-
- //Open
- !i.IsClosed &&
-
- //Assigned to nobody
- i.AssignedUserId == null &&
-
- //Created 30+ days ago
- i.CreationTime < daysAgo30 &&
-
- //No comment or the last comment was 30+ days ago
- (i.LastCommentTime == null || i.LastCommentTime < daysAgo30)
-
- ).ToListAsync();
- }
- }
-}
-````
-
-(Used EF Core for the implementation. See the [EF Core integration document](Entity-Framework-Core.md) to learn how to create custom repositories with the EF Core.)
-
-When we check the `GetInActiveIssuesAsync` implementation, we see a **business rule that defines an in-active issue**: The issue should be **open**, **assigned to nobody**, **created 30+ days ago** and has **no comment in the last 30 days**.
-
-This is an implicit definition of a business rule that is hidden inside a repository method. The problem occurs when we need to reuse this business logic.
-
-For example, let's say that we want to add an `bool IsInActive()` method on the `Issue` entity. In this way, we can check activeness when we have an issue entity.
-
-Let's see the implementation:
-
-````csharp
-public class Issue : AggregateRoot, IHasCreationTime
-{
- public bool IsClosed { get; private set; }
- public Guid? AssignedUserId { get; private set; }
- public DateTime CreationTime { get; private set; }
- public DateTime? LastCommentTime { get; private set; }
- //...
-
- public bool IsInActive()
- {
- var daysAgo30 = DateTime.Now.Subtract(TimeSpan.FromDays(30));
- return
- //Open
- !IsClosed &&
-
- //Assigned to nobody
- AssignedUserId == null &&
-
- //Created 30+ days ago
- CreationTime < daysAgo30 &&
-
- //No comment or the last comment was 30+ days ago
- (LastCommentTime == null || LastCommentTime < daysAgo30);
- }
-}
-````
-
-We had to copy/paste/modify the code. What if the definition of the activeness changes? We should not forget to update both places. This is a duplication of a business logic, which is pretty dangerous.
-
-A good solution to this problem is the *Specification Pattern*!
-
-### Specifications
-
-A [specification](Specifications.md) is a **named**, **reusable**, **combinable** and **testable** class to filter the Domain Objects based on the business rules.
-
-ABP Framework provides necessary infrastructure to easily create specification classes and use them inside your application code. Let's implement the in-active issue filter as a specification class:
-
-````csharp
-using System;
-using System.Linq.Expressions;
-using Volo.Abp.Specifications;
-
-namespace IssueTracking.Issues
-{
- public class InActiveIssueSpecification : Specification
- {
- public override Expression> ToExpression()
- {
- var daysAgo30 = DateTime.Now.Subtract(TimeSpan.FromDays(30));
- return i =>
-
- //Open
- !i.IsClosed &&
-
- //Assigned to nobody
- i.AssignedUserId == null &&
-
- //Created 30+ days ago
- i.CreationTime < daysAgo30 &&
-
- //No comment or the last comment was 30+ days ago
- (i.LastCommentTime == null || i.LastCommentTime < daysAgo30);
- }
- }
-}
-````
-
-`Specification` base class simplifies to create a specification class by defining an expression. Just moved the expression here, from the repository.
-
-Now, we can re-use the `InActiveIssueSpecification` in the `Issue` entity and `EfCoreIssueRepository` classes.
-
-#### Using within the Entity
-
-`Specification` class provides an `IsSatisfiedBy` method that returns `true` if the given object (entity) satisfies the specification. We can re-write the `Issue.IsInActive` method as shown below:
-
-````csharp
-public class Issue : AggregateRoot, IHasCreationTime
-{
- public bool IsClosed { get; private set; }
- public Guid? AssignedUserId { get; private set; }
- public DateTime CreationTime { get; private set; }
- public DateTime? LastCommentTime { get; private set; }
- //...
-
- public bool IsInActive()
- {
- return new InActiveIssueSpecification().IsSatisfiedBy(this);
- }
-}
-````
-
-Just created a new instance of the `InActiveIssueSpecification` and used its `IsSatisfiedBy` method to re-use the expression defined by the specification.
-
-#### Using with the Repositories
-
-First, starting from the repository interface:
-
-````csharp
-public interface IIssueRepository : IRepository
-{
- Task> GetIssuesAsync(ISpecification spec);
-}
-````
-
-Renamed `GetInActiveIssuesAsync` to simple `GetIssuesAsync` by taking a specification object. Since the **specification (the filter) has been moved out of the repository**, we no longer need to create different methods to get issues with different conditions (like `GetAssignedIssues(...)`, `GetLockedIssues(...)`, etc.)
-
-Updated implementation of the repository can be like that:
-
-````csharp
-public class EfCoreIssueRepository :
- EfCoreRepository,
- IIssueRepository
-{
- public EfCoreIssueRepository(
- IDbContextProvider dbContextProvider)
- : base(dbContextProvider)
- {
- }
-
- public async Task> GetIssuesAsync(ISpecification spec)
- {
- var dbSet = await GetDbSetAsync();
- return await dbSet
- .Where(spec.ToExpression())
- .ToListAsync();
- }
-}
-````
-
-Since `ToExpression()` method returns an expression, it can be directly passed to the `Where` method to filter the entities.
-
-Finally, we can pass any Specification instance to the `GetIssuesAsync` method:
-
-````csharp
-public class IssueAppService : ApplicationService, IIssueAppService
-{
- private readonly IIssueRepository _issueRepository;
-
- public IssueAppService(IIssueRepository issueRepository)
- {
- _issueRepository = issueRepository;
- }
-
- public async Task DoItAsync()
- {
- var issues = await _issueRepository.GetIssuesAsync(
- new InActiveIssueSpecification()
- );
- }
-}
-````
-
-##### With Default Repositories
-
-Actually, you don't have to create custom repositories to be able to use specifications. The standard `IRepository` already extends the `IQueryable`, so you can use the standard LINQ extension methods over it:
-
-````csharp
-public class IssueAppService : ApplicationService, IIssueAppService
-{
- private readonly IRepository _issueRepository;
-
- public IssueAppService(IRepository issueRepository)
- {
- _issueRepository = issueRepository;
- }
-
- public async Task DoItAsync()
- {
- var queryable = await _issueRepository.GetQueryableAsync();
- var issues = AsyncExecuter.ToListAsync(
- queryable.Where(new InActiveIssueSpecification())
- );
- }
-}
-````
-
-`AsyncExecuter` is a utility provided by the ABP Framework to use asynchronous LINQ extension methods (like `ToListAsync` here) without depending on the EF Core NuGet package. See the [Repositories document](Repositories.md) for more information.
-
-#### Combining the Specifications
-
-One powerful side of the Specifications is they are combinable. Assume that we have another specification that returns `true` only if the `Issue` is in a Milestone:
-
-````csharp
-public class MilestoneSpecification : Specification
-{
- public Guid MilestoneId { get; }
-
- public MilestoneSpecification(Guid milestoneId)
- {
- MilestoneId = milestoneId;
- }
-
- public override Expression> ToExpression()
- {
- return i => i.MilestoneId == MilestoneId;
- }
-}
-````
-
-This Specification is *parametric* as a difference from the `InActiveIssueSpecification`. We can combine both specifications to get a list of inactive issues in a specific milestone:
-
-````csharp
-public class IssueAppService : ApplicationService, IIssueAppService
-{
- private readonly IRepository _issueRepository;
-
- public IssueAppService(IRepository issueRepository)
- {
- _issueRepository = issueRepository;
- }
-
- public async Task DoItAsync(Guid milestoneId)
- {
- var queryable = await _issueRepository.GetQueryableAsync();
- var issues = AsyncExecuter.ToListAsync(
- queryable
- .Where(
- new InActiveIssueSpecification()
- .And(new MilestoneSpecification(milestoneId))
- .ToExpression()
- )
- );
- }
-}
-````
-
-The example above uses the `And` extension method to combine the specifications. There are more combining methods are available, like `Or(...)` and `AndNot(...)`.
-
-> See the [Specifications document](Specifications.md) for more details about the specification infrastructure provided by the ABP Framework.
-
-### Domain Services
-
-Domain Services implement domain logic which;
-
-* Depends on **services and repositories**.
-* Needs to work with **multiple aggregates**, so the logic doesn't properly fit in any of the aggregates.
-
-Domain Services work with Domain Objects. Their methods can **get and return entities, value objects, primitive types**... etc. However, **they don't get/return DTOs**. DTOs is a part of the Application Layer.
-
-**Example: Assigning an issue to a user**
-
-Remember how an issue assignment has been implemented in the `Issue` entity:
-
-````csharp
-public class Issue : AggregateRoot
-{
- //...
- public Guid? AssignedUserId { get; private set; }
-
- public async Task AssignToAsync(AppUser user, IUserIssueService userIssueService)
- {
- var openIssueCount = await userIssueService.GetOpenIssueCountAsync(user.Id);
-
- if (openIssueCount >= 3)
- {
- throw new BusinessException("IssueTracking:ConcurrentOpenIssueLimit");
- }
-
- AssignedUserId = user.Id;
- }
-
- public void CleanAssignment()
- {
- AssignedUserId = null;
- }
-}
-````
-
-Here, we will move this logic into a Domain Service.
-
-First, changing the `Issue` class:
-
-````csharp
-public class Issue : AggregateRoot
-{
- //...
- public Guid? AssignedUserId { get; internal set; }
-}
-````
-
-* Removed the assign-related methods.
-* Changed `AssignedUserId` property's setter from `private` to `internal`, to allow to set it from the Domain Service.
-
-The next step is to create a domain service, named `IssueManager`, that has `AssignToAsync` to assign the given issue to the given user.
-
-````csharp
-public class IssueManager : DomainService
-{
- private readonly IRepository _issueRepository;
-
- public IssueManager(IRepository issueRepository)
- {
- _issueRepository = issueRepository;
- }
-
- public async Task AssignToAsync(Issue issue, AppUser user)
- {
- var openIssueCount = await _issueRepository.CountAsync(
- i => i.AssignedUserId == user.Id && !i.IsClosed
- );
-
- if (openIssueCount >= 3)
- {
- throw new BusinessException("IssueTracking:ConcurrentOpenIssueLimit");
- }
-
- issue.AssignedUserId = user.Id;
- }
-}
-````
-
-`IssueManager` can inject any service dependency and use to query open issue count on the user.
-
-> We prefer and suggest to use the `Manager` suffix for the Domain Services.
-
-The only problem of this design is that `Issue.AssignedUserId` is now open to set out of the class. However, it is not `public`. It is `internal` and changing it is possible only inside the same Assembly, the `IssueTracking.Domain` project for this example solution. We think this is reasonable;
-
-* Domain Layer developers are already aware of domain rules and they use the `IssueManager`.
-* Application Layer developers are already forces to use the `IssueManager` since they don't directly set it.
-
-While there is a tradeoff between two approaches, we prefer to create Domain Services when the business logic requires to work with external services.
-
-> If you don't have a good reason, we think **there is no need to create interfaces** (like `IIssueManager` for the `IssueManager`) for Domain Services.
-
-### Application Services
-
-An [Application Service](Application-Services.md) is a stateless service that implements **use cases** of the application. An application service typically **gets and returns DTOs**. It is used by the Presentation Layer. It **uses and coordinates the domain objects** (entities, repositories, etc.) to implement the use cases.
-
-Common principles of an application service are;
-
-* Implement the **application logic** that is specific to the current use-case. Do not implement the core domain logic inside the application services. We will come back to differences between Application Domain logics.
-* **Never get or return entities** for an application service method. This breaks the encapsulation of the Domain Layer. Always get and return DTOs.
-
-**Example: Assign an Issue to a User**
-
-````csharp
-using System;
-using System.Threading.Tasks;
-using IssueTracking.Users;
-using Microsoft.AspNetCore.Authorization;
-using Volo.Abp.Application.Services;
-using Volo.Abp.Domain.Repositories;
-
-namespace IssueTracking.Issues
-{
- public class IssueAppService : ApplicationService, IIssueAppService
- {
- private readonly IssueManager _issueManager;
- private readonly IRepository _issueRepository;
- private readonly IRepository _userRepository;
-
- public IssueAppService(
- IssueManager issueManager,
- IRepository issueRepository,
- IRepository userRepository)
- {
- _issueManager = issueManager;
- _issueRepository = issueRepository;
- _userRepository = userRepository;
- }
-
- [Authorize]
- public async Task AssignAsync(IssueAssignDto input)
- {
- var issue = await _issueRepository.GetAsync(input.IssueId);
- var user = await _userRepository.GetAsync(input.UserId);
-
- await _issueManager.AssignToAsync(issue, user);
-
- await _issueRepository.UpdateAsync(issue);
- }
- }
-}
-````
-
-An application service method typically has three steps those are implemented here;
-
-1. Get the related domain objects from database to implement the use case.
-2. Use domain objects (domain services, entities, etc.) to perform the actual operation.
-3. Update the changed entities in the database.
-
-> The last *Update* is not necessary if your are using EF Core since it has a Change Tracking system. If you want to take advantage of this EF Core feature, please see the *Discussion About the Database Independence Principle* section above.
-
-`IssueAssignDto` in this example is a simple DTO class:
-
-````csharp
-using System;
-
-namespace IssueTracking.Issues
-{
- public class IssueAssignDto
- {
- public Guid IssueId { get; set; }
- public Guid UserId { get; set; }
- }
-}
-````
-
-### Data Transfer Objects
-
-A [DTO](Data-Transfer-Objects.md) is a simple object that is used to transfer state (data) between the Application and Presentation Layers. So, Application Service methods gets and returns DTOs.
-
-#### Common DTO Principles & Best Practices
-
-* A DTO **should be serializable**, by its nature. Because, most of the time it is transferred over network. So, it should have a **parameterless (empty) constructor**.
-* Should not contain any **business logic**.
-* **Never** inherit from or reference to **entities**.
-
-**Input DTOs** (those are passed to the Application Service methods) have different natures than **Output DTOs** (those are returned from the Application Service methods). So, they will be treated differently.
-
-#### Input DTO Best Practices
-
-##### Do not Define Unused Properties for Input DTOs
-
-Define **only the properties needed** for the use case! Otherwise, it will be **confusing for the clients** to use the Application Service method. You can surely define **optional properties**, but they should effect how the use case is working, when the client provides them.
-
-This rule seems unnecessary first. Who would define unused parameters (input DTO properties) for a method? But it happens, especially when you try to reuse input DTOs.
-
-##### Do not Re-Use Input DTOs
-
-Define a **specialized input DTO for each use case** (Application Service method). Otherwise, some properties are not used in some cases and this violates the rule defined above: *Do not Define Unused Properties for Input DTOs*.
-
-Sometimes, it seems appealing to reuse the same DTO class for two use cases, because they are almost same. Even if they are same now, they will probably become different by the time and you will come to the same problem. **Code duplication is a better practice than coupling use cases**.
-
-Another way of reusing input DTOs is **inheriting** DTOs from each other. While this can be useful in some rare cases, most of the time it brings you to the same point.
-
-**Example: User Application Service**
-
-````csharp
-public interface IUserAppService : IApplicationService
-{
- Task CreateAsync(UserDto input);
- Task UpdateAsync(UserDto input);
- Task ChangePasswordAsync(UserDto input);
-}
-````
-
-`IUserAppService` uses `UserDto` as the input DTO in all methods (use cases). `UserDto` is defined below:
-
-````csharp
-public class UserDto
-{
- public Guid Id { get; set; }
- public string UserName { get; set; }
- public string Email { get; set; }
- public string Password { get; set; }
- public DateTime CreationTime { get; set; }
-}
-````
-
-For this example;
-
-* `Id` is not used in *Create* since the server determines it.
-* `Password` is not used in *Update* since we have another method for it.
-* `CreationTime` is never used since we can't allow client to send the Creation Time. It should be set in the server.
-
-A true implementation can be like that:
-
-````csharp
-public interface IUserAppService : IApplicationService
-{
- Task CreateAsync(UserCreationDto input);
- Task UpdateAsync(UserUpdateDto input);
- Task ChangePasswordAsync(UserChangePasswordDto input);
-}
-````
-
-With the given input DTO classes:
-
-````csharp
-public class UserCreationDto
-{
- public string UserName { get; set; }
- public string Email { get; set; }
- public string Password { get; set; }
-}
-
-public class UserUpdateDto
-{
- public Guid Id { get; set; }
- public string UserName { get; set; }
- public string Email { get; set; }
-}
-
-public class UserChangePasswordDto
-{
- public Guid Id { get; set; }
- public string Password { get; set; }
-}
-````
-
-This is more maintainable approach although more code is written.
-
-**Exceptional Case**: There can be some exceptions for this rule: If you always want to develop two methods **in parallel**, they may share the same input DTO (by inheritance or direct reuse). For example, if you have a reporting page that has some filters and you have multiple Application Service methods (like screen report, excel report and csv report methods) use the same filters but returns different results, you may want to reuse the same filter input DTO to **couple these use cases**. Because, in this example, whenever you change a filter, you have to make the necessary changes in all the methods to have a consistent reporting system.
-
-##### Input DTO Validation Logic
-
-* Implement only **formal validation** inside the DTO. Use Data Annotation Validation Attributes or implement `IValidatableObject` for formal validation.
-* **Do not perform domain validation**. For example, don't try to check unique username constraint in the DTOs.
-
-**Example: Using Data Annotation Attributes**
-
-````csharp
-using System.ComponentModel.DataAnnotations;
-
-namespace IssueTracking.Users
-{
- public class UserCreationDto
- {
- [Required]
- [StringLength(UserConsts.MaxUserNameLength)]
- public string UserName { get; set; }
-
- [Required]
- [EmailAddress]
- [StringLength(UserConsts.MaxEmailLength)]
- public string Email { get; set; }
-
- [Required]
- [StringLength(UserConsts.MaxEmailLength,
- MinimumLength = UserConsts.MinPasswordLength)]
- public string Password { get; set; }
- }
-}
-````
-
-ABP Framework automatically validates input DTOs, throws `AbpValidationException` and returns HTTP Status `400` to the client in case of an invalid input.
-
-> Some developers think it is better to separate the validation rules and DTO classes. We think the declarative (Data Annotation) approach is practical and useful and doesn't cause any design problem. However, ABP also supports [FluentValidation integration](FluentValidation.md) if you prefer the other approach.
-
-> See the [Validation document](Validation.md) for all validation options.
-
-#### Output DTO Best Practices
-
-* Keep output **DTO count minimum**. **Reuse** where possible (exception: Do not reuse input DTOs as output DTOs).
-* Output DTOs can contain **more properties** than used in the client code.
-* Return entity DTO from **Create** and **Update** methods.
-
-The main goals of these suggestions are;
-
-* Make client code easy to develop and extend;
- * Dealing with **similar, but not same** DTOs are problematic on the client side.
- * It is common to **need to other properties** on the UI/client in the future. Returning all properties (by considering security and privileges) of an entity makes client code easy to improve without requiring to touch to the backend code.
- * If you are opening your API to **3rd-party clients** that you don't know requirements of each client.
-* Make the server side code easy to develop and extend;
- * You have less class to **understand and maintain**.
- * You can reuse the Entity->DTO **object mapping** code.
- * Returning same types from different methods make it easy and clear to create **new methods**.
-
-**Example: Returning Different DTO types from different methods**
-
-````csharp
-public interface IUserAppService : IApplicationService
-{
- UserDto Get(Guid id);
- List GetUserNameAndEmail(Guid id);
- List GetRoles(Guid id);
- List GetList();
- UserCreateResultDto Create(UserCreationDto input);
- UserUpdateResultDto Update(UserUpdateDto input);
-}
-````
-
-*(We didn't use async methods to make the example cleaner, but use async in your real world application!)*
-
-The example code above returns different DTO types for each method. As you can guess, there will be a lot of code duplications for querying data, mapping entities to DTOs.
-
-The `IUserAppService` service above can be simplified:
-
-````csharp
-public interface IUserAppService : IApplicationService
-{
- UserDto Get(Guid id);
- List GetList();
- UserDto Create(UserCreationDto input);
- UserDto Update(UserUpdateDto input);
-}
-````
-
-With a single output DTO:
-
-````csharp
-public class UserDto
-{
- public Guid Id { get; set; }
- public string UserName { get; set; }
- public string Email { get; set; }
- public DateTime CreationTime { get; set; }
- public List Roles { get; set; }
-}
-````
-
-* Removed `GetUserNameAndEmail` and `GetRoles` since `Get` method already returns the necessary information.
-* `GetList` now returns the same with `Get`.
-* `Create` and `Update` also returns the same `UserDto`.
-
-Using the same DTO has a lot of advantages as explained before. For example, think a scenario where you show a **data grid** of Users on the UI. After updating a user, you can get the return value and **update it on the UI**. So, you don't need to call `GetList` again. This is why we suggest to return the entity DTO (`UserDto` here) as return value from the `Create` and `Update` operations.
-
-##### Discussion
-
-Some of the output DTO suggestions may not fit in every scenario. These suggestions can be ignored for **performance** reasons, especially when **large data sets** returned or when you create services for your own UI and you have **too many concurrent requests**.
-
-In these cases, you may want to create **specialized output DTOs with minimal information**. The suggestions above are especially for applications where **maintaining the codebase** is more important than **negligible performance lost**.
-
-#### Object to Object Mapping
-
-Automatic [object to object mapping](Object-To-Object-Mapping.md) is a useful approach to copy values from one object to another when two objects have same or similar properties.
-
-DTO and Entity classes generally have same/similar properties and you typically need to create DTO objects from Entities. ABP's [object to object mapping system](Object-To-Object-Mapping.md) with [AutoMapper](http://automapper.org/) integration makes these operations much easier comparing to manual mapping.
-
-* **Use** auto object mapping only for **Entity to output DTO** mappings.
-* **Do not use** auto object mapping for **input DTO to Entity** mappings.
-
-There are some reasons why you **should not use** input DTO to Entity auto mapping;
-
-1. An Entity class typically has a **constructor** that takes parameters and ensures valid object creation. Auto object mapping operation generally requires an empty constructor.
-2. Most of the entity properties will have **private setters** and you should use methods to change these properties in a controlled way.
-3. You typically need to **carefully validate and process** the user/client input rather than blindly mapping to the entity properties.
-
-While some of these problems can be solved through mapping configurations (For example, AutoMapper allows to define custom mapping rules), it makes your business code **implicit/hidden** and **tightly coupled** to the infrastructure. We think the business code should be explicit, clear and easy to understand.
-
-See the *Entity Creation* section below for an example implementation of the suggestions made in this section.
-
-## Example Use Cases
-
-This section will demonstrate some example use cases and discuss alternative scenarios.
-
-### Entity Creation
-
-Creating an object from an Entity / Aggregate Root class is the first step of the lifecycle of that entity. The *Aggregate / Aggregate Root Rules & Best Practices* section suggests to **create a primary constructor** for the Entity class that guarantees to **create a valid entity**. So, whenever we need to create an instance of that entity, we should always **use that constructor**.
-
-See the `Issue` Aggregate Root class below:
-
-````csharp
-public class Issue : AggregateRoot
-{
- public Guid RepositoryId { get; private set; }
- public string Title { get; private set; }
- public string Text { get; set; }
- public Guid? AssignedUserId { get; internal set; }
-
- public Issue(
- Guid id,
- Guid repositoryId,
- string title,
- string text = null
- ) : base(id)
- {
- RepositoryId = repositoryId;
- Title = Check.NotNullOrWhiteSpace(title, nameof(title));
- Text = text; //Allow empty/null
- }
-
- private Issue() { /* Empty constructor is for ORMs */ }
-
- public void SetTitle(string title)
- {
- Title = Check.NotNullOrWhiteSpace(title, nameof(title));
- }
-
- //...
-}
-````
-
-* This class guarantees to create a valid entity by its constructor.
-* If you need to change the `Title` later, you need to use the `SetTitle` method which continues to keep `Title` in a valid state.
-* If you want to assign this issue to a user, you need to use `IssueManager` (it implements some business rules before the assignment - see the *Domain Services* section above to remember).
-* The `Text` property has a public setter, because it also accepts null values and does not have any validation rules for this example. It is also optional in the constructor.
-
-Let's see an Application Service method that is used to create an issue:
-
-````csharp
-public class IssueAppService : ApplicationService, IIssueAppService
-{
- private readonly IssueManager _issueManager;
- private readonly IRepository _issueRepository;
- private readonly IRepository _userRepository;
-
- public IssueAppService(
- IssueManager issueManager,
- IRepository issueRepository,
- IRepository userRepository)
- {
- _issueManager = issueManager;
- _issueRepository = issueRepository;
- _userRepository = userRepository;
- }
-
- public async Task CreateAsync(IssueCreationDto input)
- {
- // Create a valid entity
- var issue = new Issue(
- GuidGenerator.Create(),
- input.RepositoryId,
- input.Title,
- input.Text
- );
-
- // Apply additional domain actions
- if (input.AssignedUserId.HasValue)
- {
- var user = await _userRepository.GetAsync(input.AssignedUserId.Value);
- await _issueManager.AssignToAsync(issue, user);
- }
-
- // Save
- await _issueRepository.InsertAsync(issue);
-
- // Return a DTO represents the new Issue
- return ObjectMapper.Map(issue);
- }
-}
-````
-
-`CreateAsync` method;
-
-* Uses the `Issue` **constructor** to create a valid issue. It passes the `Id` using the [IGuidGenerator](Guid-Generation.md) service. It doesn't use auto object mapping here.
-* If the client wants to **assign this issue to a user** on object creation, it uses the `IssueManager` to do it by allowing the `IssueManager` to perform the necessary checks before this assignment.
-* **Saves** the entity to the database.
-* Finally uses the `IObjectMapper` to return an `IssueDto` that is automatically created by **mapping** from the new `Issue` entity.
-
-#### Applying Domain Rules on Entity Creation
-
-The example `Issue` entity has no business rule on entity creation, except some formal validations in the constructor. However, there maybe scenarios where entity creation should check some extra business rules.
-
-For example, assume that you **don't want** to allow to create an issue if there is already an issue with **exactly the same `Title`**. Where to implement this rule? It is **not proper** to implement this rule in the **Application Service**, because it is a **core business (domain) rule** that should always be checked.
-
-This rule should be implemented in a **Domain Service**, `IssueManager` in this case. So, we need to force the Application Layer always to use the `IssueManager` to create a new `Issue.`
-
-First, we can make the `Issue` constructor `internal`, instead of `public`:
-
-````csharp
-public class Issue : AggregateRoot
-{
- //...
-
- internal Issue(
- Guid id,
- Guid repositoryId,
- string title,
- string text = null
- ) : base(id)
- {
- RepositoryId = repositoryId;
- Title = Check.NotNullOrWhiteSpace(title, nameof(title));
- Text = text; //Allow empty/null
- }
-
- //...
-}
-````
-
-This prevents Application Services to directly use the constructor, so they will use the `IssueManager`. Then we can add a `CreateAsync` method to the `IssueManager`:
-
-````csharp
-using System;
-using System.Threading.Tasks;
-using Volo.Abp;
-using Volo.Abp.Domain.Repositories;
-using Volo.Abp.Domain.Services;
-
-namespace IssueTracking.Issues
-{
- public class IssueManager : DomainService
- {
- private readonly IRepository _issueRepository;
-
- public IssueManager(IRepository issueRepository)
- {
- _issueRepository = issueRepository;
- }
-
- public async Task CreateAsync(
- Guid repositoryId,
- string title,
- string text = null)
- {
- if (await _issueRepository.AnyAsync(i => i.Title == title))
- {
- throw new BusinessException("IssueTracking:IssueWithSameTitleExists");
- }
-
- return new Issue(
- GuidGenerator.Create(),
- repositoryId,
- title,
- text
- );
- }
- }
-}
-````
-
-* `CreateAsync` method checks if there is already an issue with the same title and throws a business exception in this case.
-* If there is no duplication, it creates and returns a new `Issue`.
-
-The `IssueAppService` is changed as shown below in order to use the `IssueManager`'s `CreateAsync` method:
-
-````csharp
-public class IssueAppService : ApplicationService, IIssueAppService
-{
- private readonly IssueManager _issueManager;
- private readonly IRepository _issueRepository;
- private readonly IRepository _userRepository;
-
- public IssueAppService(
- IssueManager issueManager,
- IRepository issueRepository,
- IRepository userRepository)
- {
- _issueManager = issueManager;
- _issueRepository = issueRepository;
- _userRepository = userRepository;
- }
-
- public async Task CreateAsync(IssueCreationDto input)
- {
- // Create a valid entity using the IssueManager
- var issue = await _issueManager.CreateAsync(
- input.RepositoryId,
- input.Title,
- input.Text
- );
-
- // Apply additional domain actions
- if (input.AssignedUserId.HasValue)
- {
- var user = await _userRepository.GetAsync(input.AssignedUserId.Value);
- await _issueManager.AssignToAsync(issue, user);
- }
-
- // Save
- await _issueRepository.InsertAsync(issue);
-
- // Return a DTO represents the new Issue
- return ObjectMapper.Map(issue);
- }
-}
-
-// *** IssueCreationDto class ***
-public class IssueCreationDto
-{
- public Guid RepositoryId { get; set; }
- [Required]
- public string Title { get; set; }
- public Guid? AssignedUserId { get; set; }
- public string Text { get; set; }
-}
-````
-
-##### Discussion: Why is the Issue not saved to the database in `IssueManager`?
-
-You may ask "**Why didn't `IssueManager` save the `Issue` to the database?**". We think it is the responsibility of the Application Service.
-
-Because, the Application Service may require additional changes/operations on the `Issue` object before saving it. If Domain Service saves it, then the *Save* operation is duplicated;
-
-* It causes performance lost because of double database round trip.
-* It requires explicit database transaction that covers both operations.
-* If additional actions cancel the entity creation because of a business rule, the transaction should be rolled back in the database.
-
-When you check the `IssueAppService`, you will see the advantage of **not saving** `Issue` to the database in the `IssueManager.CreateAsync`. Otherwise, we would need to perform one *Insert* (in the `IssueManager`) and one *Update* (after the Assignment).
-
-##### Discussion: Why is the duplicate Title check not implemented in the Application Service?
-
-We could simple say "Because it is a **core domain logic** and should be implemented in the Domain Layer". However, it brings a new question "**How did you decide** that it is a core domain logic, but not an application logic?" (we will discuss the difference later with more details).
-
-For this example, a simple question can help us to make the decision: "If we have another way (use case) of creating an issue, should we still apply the same rule? Is that rule should *always* be implemented". You may think "Why do we have a second way of creating an issue?". However, in real life, you have;
-
-* **End users** of the application may create issues in your application's standard UI.
-* You may have a second **back office** application that is used by your own employees and you may want to provide a way of creating issues (probably with different authorization rules in this case).
-* You may have an HTTP API that is open to **3rd-party clients** and they create issues.
-* You may have a **background worker** service that do something and creates issues if it detects some problems. In this way, it will create an issue without any user interaction (and probably without any standard authorization check).
-* You may have a button on the UI that **converts** something (for example, a discussion) to an issue.
-
-We can give more examples. All of these are should be implemented by **different Application Service methods** (see the *Multiple Application Layers* section below), but they **always** follow the rule: Title of the new issue can not be same of any existing issue! That's why this logic is a **core domain logic**, should be located in the Domain Layer and **should not be duplicated** in all these application service methods.
-
-### Updating / Manipulating An Entity
-
-Once an entity is created, it is updated/manipulated by the use cases until it is deleted from the system. There can be different types of the use cases directly or indirectly changes an entity.
-
-In this section, we will discuss a typical update operation that changes multiple properties of an `Issue`.
-
-This time, beginning from the *Update* DTO:
-
-````csharp
-public class UpdateIssueDto
-{
- [Required]
- public string Title { get; set; }
- public string Text { get; set; }
- public Guid? AssignedUserId { get; set; }
-}
-````
-
-By comparing to `IssueCreationDto`, you see no `RepositoryId`. Because, our system doesn't allow to move issues across repositories (think as GitHub repositories). Only `Title` is required and the other properties are optional.
-
-Let's see the *Update* implementation in the `IssueAppService`:
-
-````csharp
-public class IssueAppService : ApplicationService, IIssueAppService
-{
- private readonly IssueManager _issueManager;
- private readonly IRepository _issueRepository;
- private readonly IRepository _userRepository;
-
- public IssueAppService(
- IssueManager issueManager,
- IRepository issueRepository,
- IRepository userRepository)
- {
- _issueManager = issueManager;
- _issueRepository = issueRepository;
- _userRepository = userRepository;
- }
-
- public async Task UpdateAsync(Guid id, UpdateIssueDto input)
- {
- // Get entity from database
- var issue = await _issueRepository.GetAsync(id);
-
- // Change Title
- await _issueManager.ChangeTitleAsync(issue, input.Title);
-
- // Change Assigned User
- if (input.AssignedUserId.HasValue)
- {
- var user = await _userRepository.GetAsync(input.AssignedUserId.Value);
- await _issueManager.AssignToAsync(issue, user);
- }
-
- // Change Text (no business rule, all values accepted)
- issue.Text = input.Text;
-
- // Update entity in the database
- await _issueRepository.UpdateAsync(issue);
-
- // Return a DTO represents the new Issue
- return ObjectMapper.Map(issue);
- }
-}
-````
-
-* `UpdateAsync` method gets `id` as a separate parameter. It is not included in the `UpdateIssueDto`. This is a design decision that helps ABP to properly define HTTP routes when you [auto expose](API/Auto-API-Controllers.md) this service as an HTTP API endpoint. So, that's not related to DDD.
-* It starts by **getting** the `Issue` entity **from the database**.
-* Uses `IssueManager`'s `ChangeTitleAsync` instead of directly calling `Issue.SetTitle(...)`. Because we need to implement the **duplicate Title check** as just done in the *Entity Creation*. This requires some changes in the `Issue` and `IssueManager` classes (will be explained below).
-* Uses `IssueManager`'s `AssignToAsync` method if the **assigned user** is being changed with this request.
-* Directly sets the `Issue.Text` since there is **no business rule** for that. If we need later, we can always refactor.
-* **Saves changes** to the database. Again, saving changed entities is a responsibility of the Application Service method that coordinates the business objects and the transaction. If the `IssueManager` had saved internally in `ChangeTitleAsync` and `AssignToAsync` method, there would be double database operation (see the *Discussion: Why is the Issue not saved to the database in `IssueManager`?* above).
-* Finally uses the `IObjectMapper` to return an `IssueDto` that is automatically created by **mapping** from the updated `Issue` entity.
-
-As said, we need some changes in the `Issue` and `IssueManager` classes.
-
-First, made `SetTitle` internal in the `Issue` class:
-
-````csharp
-internal void SetTitle(string title)
-{
- Title = Check.NotNullOrWhiteSpace(title, nameof(title));
-}
-````
-
-Then added a new method to the `IssueManager` to change the Title:
-
-````csharp
-public async Task ChangeTitleAsync(Issue issue, string title)
-{
- if (issue.Title == title)
- {
- return;
- }
-
- if (await _issueRepository.AnyAsync(i => i.Title == title))
- {
- throw new BusinessException("IssueTracking:IssueWithSameTitleExists");
- }
-
- issue.SetTitle(title);
-}
-````
-
-## Domain Logic & Application Logic
-
-As mentioned before, *Business Logic* in the Domain Driven Design is spitted into two parts (layers): *Domain Logic* and *Application Logic*:
-
-
-
-Domain Logic consists of the *Core Domain Rules* of the system while Application Logic implements application specific *Use Cases*.
-
-While the definition is clear, the implementation may not be easy. You may be undecided which code should stand in the Application Layer, which code should be in the Domain Layer. This section tries to explain the differences.
-
-### Multiple Application Layers
-
-DDD helps to **deal with complexity** when your system is large. Especially, if there are **multiple applications** are being developed in a **single domain,** then the **Domain Logic vs Application Logic separation** becomes much more important.
-
-Assume that you are building a system that has multiple applications;
-
-* A **Public Web Site Application**, built with ASP.NET Core MVC, to show your products to users. Such a web site doesn't require authentication to see the products. The users login to the web site, only if they are performing some actions (like adding a product to the basket).
-* A **Back Office Application**, built with Angular UI (that uses REST APIs). This application used by office workers of the company to manage the system (like editing product descriptions).
-* A **Mobile Application** that has much simpler UI compared to the Public Web Site. It may communicate to the server via REST APIs or another technology (like TCP sockets).
-
-
-
-Every application will have different **requirements**, different **use cases** (Application Service methods), different **DTOs**, different **validation** and **authorization** rules... etc.
-
-Mixing all these logics into a single application layer makes your services contain too many `if` conditions with **complicated business logic** makes your code **harder to develop, maintain and test** and leads to potential bugs.
-
-If you've multiple applications with a single domain;
-
-* Create **separate application layers** for each application/client type and implement application specific business logic in these separate layers.
-* Use a **single domain layer** to share the core domain logic.
-
-Such a design makes it even more important to distinguish between Domain logic and Application Logic.
-
-To be more clear about the implementation, you can create different projects (`.csproj`) for each application types. For example;
-
-* `IssueTracker.Admin.Application` & `IssueTracker.Admin.Application.Contracts` projects for the Back Office (admin) Application.
-* `IssueTracker.Public.Application` & `IssueTracker.Public.Application.Contracts` projects for the Public Web Application.
-* `IssueTracker.Mobile.Application` & `IssueTracker.Mobile.Application.Contracts` projects for the Mobile Application.
-
-### Examples
-
-This section contains some Application Service and Domain Service examples to discuss how to decide to place business logic inside these services.
-
-**Example: Creating a new `Organization` in a Domain Service**
-
-````csharp
-public class OrganizationManager : DomainService
-{
- private readonly IRepository _organizationRepository;
- private readonly ICurrentUser _currentUser;
- private readonly IAuthorizationService _authorizationService;
- private readonly IEmailSender _emailSender;
-
- public OrganizationManager(
- IRepository organizationRepository,
- ICurrentUser currentUser,
- IAuthorizationService authorizationService,
- IEmailSender emailSender)
- {
- _organizationRepository = organizationRepository;
- _currentUser = currentUser;
- _authorizationService = authorizationService;
- _emailSender = emailSender;
- }
-
- public async Task CreateAsync(string name)
- {
- if (await _organizationRepository.AnyAsync(x => x.Name == name))
- {
- throw new BusinessException("IssueTracking:DuplicateOrganizationName");
- }
-
- await _authorizationService.CheckAsync("OrganizationCreationPermission");
-
- Logger.LogDebug($"Creating organization {name} by {_currentUser.UserName}");
-
- var organization = new Organization();
-
- await _emailSender.SendAsync(
- "systemadmin@issuetracking.com",
- "New Organization",
- "A new organization created with name: " + name
- );
-
- return organization;
- }
-}
-````
-
-Let's see the `CreateAsync` method step by step to discuss if the code part should be in the Domain Service, or not;
-
-* **CORRECT**: It first checks for **duplicate organization name** and and throws exception in this case. This is something related to core domain rule and we never allow duplicated names.
-* **WRONG**: Domain Services should not perform **authorization**. [Authorization](Authorization.md) should be done in the Application Layer.
-* **WRONG**: It logs a message with including the [Current User](CurrentUser.md)'s `UserName`. Domain service should not be depend on the Current User. Domain Services should be usable even if there is no user in the system. Current User (Session) should be a Presentation/Application Layer related concept.
-* **WRONG**: It sends an [email](Emailing.md) about this new organization creation. We think this is also a use case specific business logic. You may want to create different type of emails in different use cases or don't need to send emails in some cases.
-
-**Example: Creating a new `Organization` in an Application Service**
-
-````csharp
-public class OrganizationAppService : ApplicationService
-{
- private readonly OrganizationManager _organizationManager;
- private readonly IPaymentService _paymentService;
- private readonly IEmailSender _emailSender;
-
- public OrganizationAppService(
- OrganizationManager organizationManager,
- IPaymentService paymentService,
- IEmailSender emailSender)
- {
- _organizationManager = organizationManager;
- _paymentService = paymentService;
- _emailSender = emailSender;
- }
-
- [UnitOfWork]
- [Authorize("OrganizationCreationPermission")]
- public async Task CreateAsync(CreateOrganizationDto input)
- {
- await _paymentService.ChargeAsync(
- CurrentUser.Id,
- GetOrganizationPrice()
- );
-
- var organization = await _organizationManager.CreateAsync(input.Name);
-
- await _organizationManager.InsertAsync(organization);
-
- await _emailSender.SendAsync(
- "systemadmin@issuetracking.com",
- "New Organization",
- "A new organization created with name: " + input.Name
- );
-
- return organization; // !!!
- }
-
- private double GetOrganizationPrice()
- {
- return 42; //Gets from somewhere else...
- }
-}
-````
-
-Let's see the `CreateAsync` method step by step to discuss if the code part should be in the Application Service, or not;
-
-* **CORRECT**: Application Service methods should be unit of work (transactional). ABP's [Unit Of Work](Unit-Of-Work.md) system makes this automatic (even without need to add `[UnitOfWork]` attribute for the Application Services).
-* **CORRECT**: [Authorization](Authorization.md) should be done in the application layer. Here, it is done by using the `[Authorize]` attribute.
-* **CORRECT**: Payment (an infrastructure service) is called to charge money for this operation (Creating an Organization is a paid service in our business).
-* **CORRECT**: Application Service method is responsible to save changes to the database.
-* **CORRECT**: We can send [email](Emailing.md) as a notification to the system admin.
-* **WRONG**: Do not return entities from the Application Services. Return a DTO instead.
-
-**Discussion: Why don't we move the payment logic into the domain service?**
-
-You may wonder why the payment code is not inside the `OrganizationManager`. It is an **important thing** and we never want to **miss the payment**.
-
-However, **being important is not sufficient** to consider a code as a Core Business Logic. We may have **other use cases** where we don't charge money to create a new Organization. Examples;
-
-* An admin user can use a Back Office Application to create a new organization without any payment.
-* A background-working data import/integration/synchronization system may also need to create organizations without any payment operation.
-
-As you see, **payment is not a necessary operation to create a valid organization**. It is a use-case specific application logic.
-
-**Example: CRUD Operations**
-
-````csharp
-public class IssueAppService
-{
- private readonly IssueManager _issueManager;
-
- public IssueAppService(IssueManager issueManager)
- {
- _issueManager = issueManager;
- }
-
- public async Task GetAsync(Guid id)
- {
- return await _issueManager.GetAsync(id);
- }
-
- public async Task CreateAsync(IssueCreationDto input)
- {
- await _issueManager.CreateAsync(input);
- }
-
- public async Task UpdateAsync(UpdateIssueDto input)
- {
- await _issueManager.UpdateAsync(input);
- }
-
- public async Task DeleteAsync(Guid id)
- {
- await _issueManager.DeleteAsync(id);
- }
-}
-````
-
-This Application Service **does nothing** itself and **delegates all the work** to the *Domain Service*. It even passes the DTOs to the `IssueManager`.
-
-* **Do not** create Domain Service methods just for simple **CRUD** operations **without any domain logic**.
-* **Never** pass **DTOs** to or return **DTOs** from the Domain Services.
-
-Application Services can directly work with repositories to query, create, update or delete data unless there are some domain logics should be performed during these operations. In such cases, create Domain Service methods, but only for those really necessary.
-
-> Do not create such CRUD domain service methods just by thinking that they may be needed in the future ([YAGNI](https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it))! Do it when you need and refactor the existing code. Since the Application Layer gracefully abstracts the Domain Layer, the refactoring process doesn't effect the UI Layer and other clients.
-
-## Reference Books
-
-If you are more interested in the Domain Driven Design and building large-scale enterprise systems, the following books are recommended as reference books;
-
-* "*Domain Driven Design*" by Eric Evans
-* "*Implementing Domain Driven Design*" by Vaughn Vernon
-* "*Clean Architecture*" by Robert C. Martin
+https://abp.io/books/implementing-domain-driven-design
diff --git a/docs/en/Domain-Driven-Design.md b/docs/en/Domain-Driven-Design.md
index f18c1882ef..03a6232ba3 100644
--- a/docs/en/Domain-Driven-Design.md
+++ b/docs/en/Domain-Driven-Design.md
@@ -32,6 +32,6 @@ DDD mostly interest in the **Domain** and the **Application** layers, rather tha
* [Data Transfer Objects (DTOs)](Data-Transfer-Objects.md)
* [Unit of Work](Unit-Of-Work.md)
-## The Ultimate DDD Implementation Guide
+## Free E-Book: Implementing DDD
-See the [Implementing Domain Driven Design](Domain-Driven-Design-Implementation-Guide.md) guide as a **complete reference**. The Guide explains the Domain Driven Design and introduces explicit **rules and examples** to give a deep understanding of the **implementation details**.
\ No newline at end of file
+See the [Implementing Domain Driven Design book](https://abp.io/books/implementing-domain-driven-design) as a **complete reference**. This book explains the Domain Driven Design and introduces explicit **rules and examples** to give a deep understanding of the **implementation details**.
\ No newline at end of file
diff --git a/docs/en/Entity-Framework-Core.md b/docs/en/Entity-Framework-Core.md
index fcbf5d8091..f60fcfc490 100644
--- a/docs/en/Entity-Framework-Core.md
+++ b/docs/en/Entity-Framework-Core.md
@@ -604,23 +604,77 @@ ObjectExtensionManager.Instance
);
````
-If the related module has implemented this feature (by using the `ConfigureEfCoreEntity` explained below), then the new property is added to the model. Then you need to run the standard `Add-Migration` and `Update-Database` commands to update your database to add the new field.
+### MapEfCoreEntity
->`MapEfCoreProperty` method must be called before using the related `DbContext`. It is a static method. The best way is to use it in your application as earlier as possible. The application startup template has a `YourProjectNameEfCoreEntityExtensionMappings` class that is safe to use this method inside.
+`MapEfCoreEntity` is a shortcut extension method to configure the `Entity`.
-### ConfigureEfCoreEntity
+**Example**: Set the max length of `Name` to the `IdentityRole` entity:
-If you are building a reusable module and want to allow application developers to add properties to your entities, you can use the `ConfigureEfCoreEntity` extension method in your entity mapping. However, there is a shortcut extension method `ConfigureObjectExtensions` that can be used while configuring the entity mapping:
+````csharp
+ObjectExtensionManager.Instance
+ .MapEfCoreEntity(builder =>
+ {
+ builder.As>().Property(x => x.Name).HasMaxLength(200);
+ });
+````
+
+### MapEfCoreDbContext
+
+`MapEfCoreDbContext` is a shortcut extension method to configure the `DbContext`.
+
+**Example**: Set the max length of `Name` to the `IdentityRole` entity of `IdentityDbContext`:
````csharp
-builder.Entity(b =>
+ObjectExtensionManager.Instance.MapEfCoreDbContext(b =>
{
- b.ConfigureObjectExtensions();
- //...
+ b.Entity().Property(x => x.Name).HasMaxLength(200);
});
````
-> If you call `ConfigureByConvention()` extension method (like `b.ConfigureByConvention()` for this example), ABP Framework internally calls the `ConfigureObjectExtensions` method. It is a **best practice** to use the `ConfigureByConvention()` method since it also configures database mapping for base properties by convention.
+If the related module has implemented this feature(explained below), then the new property is added to the model or the DbContext/Entity configure changed. Then you need to run the standard `Add-Migration` and `Update-Database` commands to update your database to add the new field.
+
+> The `MapEfCoreProperty`, `MapEfCoreEntity` and `MapEfCoreDbContext` methods must be called before using the related `DbContext`. It is a static method. The best way is to use it in your application as earlier as possible. The application startup template has a `YourProjectNameEfCoreEntityExtensionMappings` class that is safe to use this method inside.
+
+### ConfigureEfCoreEntity, ApplyObjectExtensionMappings and TryConfigureObjectExtensions
+
+If you are building a reusable module and want to allow application developers to add properties to your entities, you can use the `ConfigureEfCoreEntity`, `ApplyObjectExtensionMappings` and `TryConfigureObjectExtensions` extension methods in your entity mapping.
+
+**Example**:
+````csharp
+public static class QADbContextModelCreatingExtensions
+{
+ public static void ConfigureQA(
+ this ModelBuilder builder,
+ Action optionsAction = null)
+ {
+ Check.NotNull(builder, nameof(builder));
+
+ var options = new QAModelBuilderConfigurationOptions(
+ QADatabaseDbProperties.DbTablePrefix,
+ QADatabaseDbProperties.DbSchema
+ );
+
+ optionsAction?.Invoke(options);
+
+ builder.Entity(b =>
+ {
+ b.ToTable(options.TablePrefix + "Questions", options.Schema);
+ b.ConfigureByConvention();
+ //...
+
+ //Call this in the end of buildAction.
+ b.ApplyObjectExtensionMappings();
+ });
+
+ //...
+
+ //Call this in the end of ConfigureQA.
+ builder.TryConfigureObjectExtensions();
+ }
+}
+````
+
+> If you call `ConfigureByConvention()` extension method (like `b.ConfigureByConvention()` for this example), ABP Framework internally calls the `ConfigureObjectExtensions` and `ConfigureEfCoreEntity` methods. It is a **best practice** to use the `ConfigureByConvention()` method since it also configures database mapping for base properties by convention.
See the "*ConfigureByConvention Method*" section above for more information.
@@ -812,4 +866,4 @@ public class MyCustomEfCoreBulkOperationProvider
## See Also
* [Entities](Entities.md)
-* [Repositories](Repositories.md)
\ No newline at end of file
+* [Repositories](Repositories.md)
diff --git a/docs/en/Index.md b/docs/en/Index.md
index de88e2f2f8..8483d61612 100644
--- a/docs/en/Index.md
+++ b/docs/en/Index.md
@@ -29,8 +29,9 @@ ABP has a **comprehensive documentation** that not only explains the ABP Framewo
ABP offers a complete, modular and layered software architecture based on [Domain Driven Design](Domain-Driven-Design.md) principles and patterns. It also provides the necessary infrastructure to implement this architecture.
* See the [Modularity](Module-Development-Basics.md) document to understand the module system.
-* [Implementing Domain Driven Design](Domain-Driven-Design-Implementation-Guide.md) document is an ultimate guide for who want to understand and implement the DDD.
+* [Implementing Domain Driven Design book](https://abp.io/books/implementing-domain-driven-design?ref=doc) is an ultimate guide for who want to understand and implement the DDD with the ABP Framework.
* [Microservice Architecture](Microservice-Architecture.md) document explains how ABP helps to create a microservice solution.
+* [Multi-Tenancy](Multi-Tenancy.md) document introduces multi-tenancy and explores the ABP multi-tenancy infrastructure.
### Infrastructure
@@ -55,6 +56,14 @@ See the [Application Modules](Modules/Index.md) document for all pre-built modul
The [Startup templates](Startup-Templates/Index.md) are pre-built Visual Studio solution templates. You can create your own solution based on these templates to **immediately start your development**.
+## Free E-Book: Implementing Domain Driven Design
+
+
+
+A **practical guide** for implementing Domain Driven Design (DDD). While the implementation details are **based on the ABP Framework** infrastructure, the basic concepts, principles and models can be applied to any solution, even if it is not a .NET solution.
+
+[Click here to get your free copy](https://abp.io/books/implementing-domain-driven-design?ref=doc).
+
## ABP Community
### The Source Code
diff --git a/docs/en/Modules/Setting-Management.md b/docs/en/Modules/Setting-Management.md
index dff8da3f8e..255efc9a5f 100644
--- a/docs/en/Modules/Setting-Management.md
+++ b/docs/en/Modules/Setting-Management.md
@@ -83,4 +83,192 @@ Setting Management module is extensible, just like the [setting system](../Setti
* `TenantSettingManagementProvider`: Gets or sets the setting value for a tenant.
* `UserSettingManagementProvider`: Gets the setting value for a user.
-`ISettingManager` uses the setting management providers on get/set methods. Typically, every setting management provider defines extension methods on the `ISettingManagement` service (like `SetForUserAsync` defined by the user setting management provider).
\ No newline at end of file
+`ISettingManager` uses the setting management providers on get/set methods. Typically, every setting management provider defines extension methods on the `ISettingManagement` service (like `SetForUserAsync` defined by the user setting management provider).
+
+## Setting Management UI
+
+Setting Mangement module provided the email setting UI by default, and it is extensible; You can add your tabs to this page for your application settings.
+
+### MVC UI
+
+#### Create a setting View Component
+
+Create `MySettingGroup` folder under the `Components` folder. Add a new view component. Name it as `MySettingGroupViewComponent`:
+
+
+
+Open the `MySettingGroupViewComponent.cs` and change the whole content as shown below:
+
+```csharp
+public class MySettingGroupViewComponent : AbpViewComponent
+{
+ public virtual IViewComponentResult Invoke()
+ {
+ return View("~/Components/MySettingGroup/Default.cshtml");
+ }
+}
+```
+
+> You can also use the `InvokeAsync` method, In this example, we use the `Invoke` method.
+
+#### Default.cshtml
+
+Create a `Default.cshtml` file under the `MySettingGroup` folder.
+
+Open the `Default.cshtml` and change the whole content as shown below:
+
+```html
+
+
My setting group page
+
+```
+
+#### BookStoreSettingPageContributor
+
+Create a `BookStoreSettingPageContributor.cs` file under the `Settings` folder:
+
+
+
+The content of the file is shown below:
+
+```csharp
+public class BookStoreSettingPageContributor : ISettingPageContributor
+{
+ public Task ConfigureAsync(SettingPageCreationContext context)
+ {
+ context.Groups.Add(
+ new SettingPageGroup(
+ "Volo.Abp.MySettingGroup",
+ "MySettingGroup",
+ typeof(MySettingGroupViewComponent)
+ )
+ );
+
+ return Task.CompletedTask;
+ }
+
+ public Task CheckPermissionsAsync(SettingPageCreationContext context)
+ {
+ // You can check the permissions here
+ return Task.FromResult(true);
+ }
+}
+```
+
+Open the `BookStoreWebModule.cs` file and add the following code:
+
+```csharp
+Configure(options =>
+{
+ options.Contributors.Add(new BookStoreSettingPageContributor());
+});
+```
+
+#### Run the Application
+
+Navigate to `/SettingManagement` route to see the changes:
+
+
+
+### Blazor UI
+
+#### Create a Razor Component
+
+Create `MySettingGroup` folder under the `Pages` folder. Add a new razor component. Name it as `MySettingGroupComponent`:
+
+
+
+Open the `MySettingGroupComponent.razor` and change the whole content as shown below:
+
+```csharp
+
+
my setting group
+
+```
+
+#### BookStoreSettingComponentContributor
+
+Create a `BookStoreSettingComponentContributor.cs` file under the `Settings` folder:
+
+
+
+The content of the file is shown below:
+
+```csharp
+public class BookStoreSettingComponentContributor : ISettingComponentContributor
+{
+ public Task ConfigureAsync(SettingComponentCreationContext context)
+ {
+ context.Groups.Add(
+ new SettingComponentGroup(
+ "Volo.Abp.MySettingGroup",
+ "MySettingGroup",
+ typeof(MySettingGroupComponent)
+ )
+ );
+
+ return Task.CompletedTask;
+ }
+
+ public Task CheckPermissionsAsync(SettingComponentCreationContext context)
+ {
+ // You can check the permissions here
+ return Task.FromResult(true);
+ }
+}
+```
+
+Open the `BookStoreBlazorModule.cs` file and add the following code:
+
+```csharp
+Configure(options =>
+{
+ options.Contributors.Add(new BookStoreSettingComponentContributor());
+});
+```
+
+#### Run the Application
+
+Navigate to `/setting-management` route to see the changes:
+
+
+
+### Angular UI
+
+#### Create a Component
+
+Create a component with the following command:
+
+```bash
+yarn ng generate component my-settings
+```
+
+Open the `app.component.ts` and modify the file as shown below:
+
+```js
+import { Component } from '@angular/core';
+import { SettingTabsService } from '@abp/ng.core'; // imported SettingTabsService
+import { MySettingsComponent } from './my-settings/my-settings.component'; // imported MySettingsComponent
+
+@Component(/* component metadata */)
+export class AppComponent {
+ constructor(private settingTabs: SettingTabsService) // injected MySettingsComponent
+ {
+ // added below
+ settingTabs.add([
+ {
+ name: 'MySettings',
+ order: 1,
+ requiredPolicy: 'policy key here',
+ component: MySettingsComponent,
+ },
+ ]);
+ }
+}
+```
+
+#### Run the Application
+
+Navigate to `/setting-management` route to see the changes:
+
+
\ No newline at end of file
diff --git a/docs/en/Modules/Tenant-Management.md b/docs/en/Modules/Tenant-Management.md
index 73e16aee8e..dca6ea3d1e 100644
--- a/docs/en/Modules/Tenant-Management.md
+++ b/docs/en/Modules/Tenant-Management.md
@@ -1,3 +1,107 @@
# Tenant Management Module
-TODO
\ No newline at end of file
+[Multi-Tenancy](../Multi-Tenancy.md) is one of the core features of ABP Framework. It provides the fundamental infrastructure to build your own SaaS (Software-as-a-Service) solution. ABP's multi-tenancy system abstracts where your tenants are stored, by providing the `ITenantStore` interface. All you need to do is to implement that interface.
+
+**The Tenant Management module is an implementation of the the `ITenantStore` interface. It stores tenants in a database. It also provides UI to manage your tenants and their [features](../Features.md).**
+
+> Please **refer to the [Multi-Tenancy](../Multi-Tenancy.md) documentation** to understand the multi-tenancy system of the ABP Framework. This document focuses on the Tenant Management module.
+
+### About the ABP Commercial SaaS Module
+
+The [SaaS Module](https://commercial.abp.io/modules/Volo.Saas) is an alternative implementation of this module with more features and possibilities. It is distributed as a part of the [ABP Commercial](https://commercial.abp.io/) subscription.
+
+## How to Install
+
+This module comes as pre-installed (as [NuGet/NPM packages](NuGet/NPM packages)) when you [create a new solution](https://abp.io/get-started) with the ABP Framework. You can continue to use it as package and get updates easily, or you can include its source code into your solution (see `get-source` [CLI](../CLI.md) command) to develop your custom module.
+
+### The Source Code
+
+The source code of this module can be accessed [here](https://github.com/abpframework/abp/tree/dev/modules/tenant-management). The source code is licensed with [MIT](https://choosealicense.com/licenses/mit/), so you can freely use and customize it.
+
+## User Interface
+
+This module adds "*Administration -> Tenant Management -> Tenants*" menu item to the main menu of the application, which opens the page shown below:
+
+
+
+In this page, you see the all the tenants. You can create a new tenant as shown below:
+
+
+
+In this modal;
+
+* **Name**: The unique name of the tenant. If you use subdomains for your tenants (like https://some-tenant.your-domain.com), this will be the subdomain name.
+* **Admin Email Address**: Email address of the admin user for this tenant.
+* **Admin Password**: The password of the admin user for this tenant.
+
+When you click to *Actions* button near to a tenant, you will see the actions you can take:
+
+
+
+### Managing the Tenant Features
+
+The Features action opens a modal to enable/disable/set [features](../Features.md) for the related tenant. Here, an example modal:
+
+
+
+### Managing the Host Features
+
+*Manage Host features* button is used to set features for the host side, if you use the features of your application also in the host side.
+
+## Internals
+
+This section can be used as a reference if you want to [customize](../Customizing-Application-Modules-Guide.md) this module without changing [its source code](https://github.com/abpframework/abp/tree/dev/modules/tenant-management).
+
+### Domain Layer
+
+#### Aggregates
+
+* `Tenant`
+
+#### Repositories
+
+* `ITenantRepository`
+
+#### Domain Services
+
+* `TenantManager`
+
+### Application Layer
+
+#### Application Services
+
+* `TenantAppService`
+
+#### Permissions
+
+- `AbpTenantManagement.Tenants`: Tenant management.
+- `AbpTenantManagement.Tenants.Create`: Creating a new tenant.
+- `AbpTenantManagement.Tenants.Update`: Editing an existing tenant.
+- `AbpTenantManagement.Tenants.Delete`: Deleting an existing tenant.
+- `AbpTenantManagement.Tenants.ManageFeatures`: Manage features of the tenants.
+
+### Entity Framework Core Integration
+
+* `TenantManagementDbContext` (implements `ITenantManagementDbContext`)
+
+**Database Tables:**
+
+* `AbpTenants`
+* `AbpTenantConnectionStrings`
+
+### MongoDB Integration
+
+* `TenantManagementMongoDbContext` (implements `ITenantManagementMongoDbContext`)
+
+**Database Collections:**
+
+* `AbpTenants` (also includes the connection string)
+
+## Notices
+
+ABP Framework allows to use *database per tenant* approach that allows a tenant can have a dedicated database. This module has the fundamental infrastructure to make that implementation possible (see its source code), however it doesn't implement the application layer and UI functionalities to provide it as an out of the box implementation. You can implement these features yourself, or consider to use the [ABP Commercial Saas Module](https://docs.abp.io/en/commercial/latest/modules/saas) that fully implements it and provides much more business features.
+
+## See Also
+
+* [Multi-Tenancy](../Multi-Tenancy.md)
+* [ABP Commercial SaaS Module](https://docs.abp.io/en/commercial/latest/modules/saas)
\ No newline at end of file
diff --git a/docs/en/Road-Map.md b/docs/en/Road-Map.md
index f57e35c863..26de749096 100644
--- a/docs/en/Road-Map.md
+++ b/docs/en/Road-Map.md
@@ -8,11 +8,9 @@ This document provides a road map, release schedule and planned features for the
This version will focus on **documentation** and **improvements** of current features. In addition, the following features are planned:
-* Publishing distributed events as transactional ([#6126](https://github.com/abpframework/abp/issues/6126))
* Revisit the microservice demo solution ([#8385](https://github.com/abpframework/abp/issues/8385))
* A new UI Theme alternative to the Basic Theme ([#6132](https://github.com/abpframework/abp/issues/6132))
* Improvements and new features to the [CMS Kit](Modules/Cms-Kit.md) module ([#8380](https://github.com/abpframework/abp/issues/8380) [#8381](https://github.com/abpframework/abp/issues/8381))
-* Pre-configured test project for the [Blazor UI](UI/Blazor/Overall.md) ([#5516](https://github.com/abpframework/abp/issues/5516))
* Razor engine support for text templating ([#8373](https://github.com/abpframework/abp/issues/8373))
**Planned release date**: End of Quarter 2, 2021. See the [4.4 milestone](https://github.com/abpframework/abp/milestone/52) to track the progress.
@@ -25,6 +23,7 @@ We planned to focus on the ABP Framework v5.0 after the 4.4 release. This versio
* Upgrading to Bootstrap 5.x ([#8922](https://github.com/abpframework/abp/issues/8922))
* Alternative to IdentityServer4 ([#7221](https://github.com/abpframework/abp/issues/7221))
* Dapr integration ([#2183](https://github.com/abpframework/abp/issues/2183))
+* Publishing distributed events as transactional ([#6126](https://github.com/abpframework/abp/issues/6126))
* Resource based authorization system ([#236](https://github.com/abpframework/abp/issues/236))
* API Versioning system: finalize & document ([#497](https://github.com/abpframework/abp/issues/497))
* Performance optimizations; Enabling .NET Trimming, using source generators and reducing reflection, etc.
diff --git a/docs/en/Tutorials/Todo/Index.md b/docs/en/Tutorials/Todo/Index.md
index e71749544e..64cbca13f3 100644
--- a/docs/en/Tutorials/Todo/Index.md
+++ b/docs/en/Tutorials/Todo/Index.md
@@ -135,7 +135,7 @@ namespace TodoApp
}
````
-`BasicAggregateRoot` is one the simplest base class to create root entities, and `Guid` is the primary key (`Id`) of the entity here.
+`BasicAggregateRoot` is the simplest base class to create root entities, and `Guid` is the primary key (`Id`) of the entity here.
## Database Integration
@@ -214,7 +214,7 @@ Now, we can use ABP repositories to save and retrieve todo items, as we'll do in
## Application Layer
-An [Application Service](../../Application-Services.md) is used to perform use cases of the application. We need to perform the following use cases;
+An [Application Service](../../Application-Services.md) is used to perform use cases of the application. We need to perform the following use cases:
* Get the list of todo items
* Create a new todo item
@@ -243,7 +243,7 @@ namespace TodoApp
### Data Transfer Object
-`GetListAsync` and `CreateAsync` methods return `TodoItemDto`. Applications Services typically gets and returns DTOs ([Data Transfer Objects](../../Data-Transfer-Objects.md)) instead of entities. So, we should define the DTO class here. Create a new `TodoItemDto` class inside the *TodoApp.Application.Contracts* project:
+`GetListAsync` and `CreateAsync` methods return `TodoItemDto`. `ApplicationService` typically gets and returns DTOs ([Data Transfer Objects](../../Data-Transfer-Objects.md)) instead of entities. So, we should define the DTO class here. Create a new `TodoItemDto` class inside the *TodoApp.Application.Contracts* project:
````csharp
using System;
@@ -465,9 +465,9 @@ $(function () {
});
````
-In the first part, we are registering to click events of the trash icons near to the todo items, deleting the related item on the server and showing a notification on the UI. Also, we are removing the deleted item from DOM, so we don't need to refresh the page.
+In the first part, we are subscribing to click events of the trash icons near to the todo items, deleting the related item on the server and showing a notification on the UI. Also, we are removing the deleted item from DOM, so we don't need to refresh the page.
-In the second part, we are creating a new todo item on the server. If it succeed, we are then manipulating DOM to insert a new `
` element to the todo list. In this way, no need to refresh the whole page after creating a new todo item.
+In the second part, we are creating a new todo item on the server. If it succeeds, we are then manipulating DOM to insert a new `
` element to the todo list. This way we don't need to refresh the whole page after creating a new todo item.
The interesting part here is how we communicate with the server. See the *Dynamic JavaScript Proxies & Auto API Controllers* section to understand how it works. But now, let's continue and complete the application.
@@ -504,13 +504,13 @@ As the final touch, open the `Index.css` file in the `Pages` folder of the *Todo
This is a simple styling for the todo page. We believe that you can do much better :)
-Now, you can run the application again to see the result.
+Now, you can run the application again and see the result.
### Dynamic JavaScript Proxies & Auto API Controllers
In the `Index.js` file, we've used `todoApp.todo.delete(...)` and `todoApp.todo.create(...)` functions to communicate with the server. These functions are dynamically created by the ABP Framework, thanks to the [Dynamic JavaScript Client Proxy](../../UI/AspNetCore/Dynamic-JavaScript-Proxies.md) system. They perform HTTP API calls to the server and return a promise, so you can register a callback to the `then` function as we've done above.
-However, you may ask that we haven't created any API Controller, so how server handles these requests? This question brings us the [Auto API Controller](../../API/Auto-API-Controllers.md) feature of the ABP Framework. It automatically converts the application services to API Controllers by conventions.
+However, you may notice that we haven't created any API Controller, so how server handles these requests? This question brings us the [Auto API Controller](../../API/Auto-API-Controllers.md) feature of the ABP Framework. It automatically converts the application services to API Controllers by convention.
If you open the [Swagger UI](https://swagger.io/tools/swagger-ui/) by entering the `/swagger` URL in your application, you can see the Todo API:
@@ -559,7 +559,7 @@ namespace TodoApp.Blazor.Pages
}
````
-This class uses the `ITodoAppService` to perform operations for the todo items. It manipulates the `TodoItems` list after create and delete operations. In this way, we don't need to refresh the whole todo list from the server.
+This class uses the `ITodoAppService` to perform operations for the todo items. It manipulates the `TodoItems` list after create and delete operations. This way, we don't need to refresh the whole todo list from the server.
{{if UI=="Blazor"}}
@@ -653,7 +653,7 @@ In the `Index.razor.cs` file, we've injected (with the `[Inject]` attribute) and
The magic is done by the ABP Framework's [Dynamic C# Client Proxy](../../API/Dynamic-CSharp-API-Clients.md) system. It uses the standard `HttpClient` and performs HTTP API requests to the remote server. It also handles all the standard tasks for us, including authorization, JSON serialization and exception handling.
-However, you may ask that we haven't created any API Controller, so how server handles these requests? This question brings us the [Auto API Controller](../../API/Auto-API-Controllers.md) feature of the ABP Framework. It automatically converts the application services to API Controllers by conventions.
+However, you may ask that we haven't created any API Controller, so how server handles these requests? This question brings us the [Auto API Controller](../../API/Auto-API-Controllers.md) feature of the ABP Framework. It automatically converts the application services to API Controllers by convention.
If you run the `TodoApp.HttpApi.Host` application, you can see the Todo API:
@@ -669,7 +669,7 @@ ABP provides a handy feature to automatically create client-side services to eas
You first need to run the `TodoApp.HttpApi.Host` project since the proxy generator reads API definitions from the server application.
-> **Warning**: There is a problem with IIS Express; it doesn't allow to connect to the application from another process. If you are using Visual Studio, select the `TodoApp.HttpApi.Host` instead of IIS Express in the run button drop-down list, as shown in the figure below:
+> **Warning**: There is an issue with IIS Express: it doesn't allow to connect to the application from another process. If you are using Visual Studio, select the `TodoApp.HttpApi.Host` instead of IIS Express in the run button drop-down list, as shown in the figure below:

@@ -813,7 +813,7 @@ Now, you can run the application again to see the result.
## Conclusion
-In this tutorial, we've build a very simple application to warm up to the ABP Framework. If you are looking to build a serious application, please check the [web application development tutorial](../Part-1.md) which covers all the aspects of a real-life web application development.
+In this tutorial, we've built a very simple application to warm up to the ABP Framework. If you are looking to build a serious application, please check the [web application development tutorial](../Part-1.md) which covers all the aspects of a real-life web application development.
## Source Code
@@ -821,4 +821,4 @@ You can find source code of the completed application [here](https://github.com/
## See Also
-* [Web Application Development Tutorial](../Part-1.md)
\ No newline at end of file
+* [Web Application Development Tutorial](../Part-1.md)
diff --git a/docs/en/UI/Angular/Account-Module.md b/docs/en/UI/Angular/Account-Module.md
index 9496eb95c5..1b6a15d149 100644
--- a/docs/en/UI/Angular/Account-Module.md
+++ b/docs/en/UI/Angular/Account-Module.md
@@ -120,6 +120,4 @@ export const environment = {
} as Config.Environment;
```
-> Note: The resource owner password flow does not support the two-factor authentication for some technical reasons.
-
See the [Authorization in Angular UI](./Authorization.md) document for more details.
diff --git a/docs/en/UI/Angular/Authorization.md b/docs/en/UI/Angular/Authorization.md
index 54850e4569..1bde885180 100644
--- a/docs/en/UI/Angular/Authorization.md
+++ b/docs/en/UI/Angular/Authorization.md
@@ -52,5 +52,3 @@ export const environment = {
```
According to this flow, the user is redirected to the login page in the account module.
-
-> Note: The resource owner password flow does not support the two-factor authentication for some technical reasons.
\ No newline at end of file
diff --git a/docs/en/UI/Angular/Custom-Setting-Page.md b/docs/en/UI/Angular/Custom-Setting-Page.md
deleted file mode 100644
index 9a17f6ad7b..0000000000
--- a/docs/en/UI/Angular/Custom-Setting-Page.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# Custom Setting Page
-
-There are several settings tabs from different modules. You can add a custom setting page to your project.
-
-1. Create a component with the following command:
-
-```bash
-yarn ng generate component my-settings
-```
-
-2. Open the `app.component.ts` and modify the file as shown below:
-
-```js
-import { Component } from '@angular/core';
-import { SettingTabsService } from '@abp/ng.core'; // imported SettingTabsService
-import { MySettingsComponent } from './my-settings/my-settings.component'; // imported MySettingsComponent
-
-@Component(/* component metadata */)
-export class AppComponent {
- constructor(private settingTabs: SettingTabsService) // injected MySettingsComponent
- {
- // added below
- settingTabs.add([
- {
- name: 'MySettings',
- order: 1,
- requiredPolicy: 'policy key here',
- component: MySettingsComponent,
- },
- ]);
- }
-}
-```
-
-Navigate to `/setting-management` route to see the changes:
-
-
diff --git a/docs/en/UI/Blazor/Overall.md b/docs/en/UI/Blazor/Overall.md
index a249dd354b..112dfec8cc 100644
--- a/docs/en/UI/Blazor/Overall.md
+++ b/docs/en/UI/Blazor/Overall.md
@@ -93,6 +93,8 @@ These libraries are selected as the base libraries and available to the applicat
> Bootstrap's JavaScript part is not used since the Blazorise library already provides the necessary functionalities to the Bootstrap components in a native way.
+> Beginning from June, 2021, the Blazorise library has dual licenses; open source & commercial. Based on your yearly revenue, you may need to buy a commercial license. See [this post](https://blazorise.com/news/blazorise-commercial-going-live/) for the announcement.
+
### The Layout
The themes provide the layout. So, you have a responsive layout with the standard features already implemented. The screenshot below has taken from the layout of the [Basic Theme](Basic-Theme.md):
diff --git a/docs/en/docs-nav.json b/docs/en/docs-nav.json
index 8abfddd251..6615cbce1b 100644
--- a/docs/en/docs-nav.json
+++ b/docs/en/docs-nav.json
@@ -543,8 +543,8 @@
]
},
{
- "text": "Guide: Implementing DDD",
- "path": "Domain-Driven-Design-Implementation-Guide.md"
+ "text": "E-Book: Implementing DDD",
+ "path": "https://abp.io/books/implementing-domain-driven-design"
}
]
},
@@ -1027,10 +1027,6 @@
"text": "Component Replacement",
"path": "UI/Angular/Component-Replacement.md"
},
- {
- "text": "Custom Setting Page",
- "path": "UI/Angular/Custom-Setting-Page.md"
- },
{
"text": "Extensions",
"items": [
diff --git a/docs/en/UI/Angular/images/custom-settings.png b/docs/en/images/custom-settings.png
similarity index 100%
rename from docs/en/UI/Angular/images/custom-settings.png
rename to docs/en/images/custom-settings.png
diff --git a/docs/en/images/implementing-domain-driven-design-book.png b/docs/en/images/implementing-domain-driven-design-book.png
new file mode 100644
index 0000000000..6568b46f66
Binary files /dev/null and b/docs/en/images/implementing-domain-driven-design-book.png differ
diff --git a/docs/en/images/module-tenant-management-actions.png b/docs/en/images/module-tenant-management-actions.png
new file mode 100644
index 0000000000..d1f01c2e93
Binary files /dev/null and b/docs/en/images/module-tenant-management-actions.png differ
diff --git a/docs/en/images/module-tenant-management-new-tenant.png b/docs/en/images/module-tenant-management-new-tenant.png
new file mode 100644
index 0000000000..ab9ee6ed56
Binary files /dev/null and b/docs/en/images/module-tenant-management-new-tenant.png differ
diff --git a/docs/en/images/module-tenant-management-page.png b/docs/en/images/module-tenant-management-page.png
new file mode 100644
index 0000000000..563c64aac8
Binary files /dev/null and b/docs/en/images/module-tenant-management-page.png differ
diff --git a/docs/en/images/my-setting-group-blazor.png b/docs/en/images/my-setting-group-blazor.png
new file mode 100644
index 0000000000..0e685ff186
Binary files /dev/null and b/docs/en/images/my-setting-group-blazor.png differ
diff --git a/docs/en/images/my-setting-group-component-contributor.png b/docs/en/images/my-setting-group-component-contributor.png
new file mode 100644
index 0000000000..3ca6dbedfb
Binary files /dev/null and b/docs/en/images/my-setting-group-component-contributor.png differ
diff --git a/docs/en/images/my-setting-group-component.png b/docs/en/images/my-setting-group-component.png
new file mode 100644
index 0000000000..edcf315b2a
Binary files /dev/null and b/docs/en/images/my-setting-group-component.png differ
diff --git a/docs/en/images/my-setting-group-page-contributor.png b/docs/en/images/my-setting-group-page-contributor.png
new file mode 100644
index 0000000000..3be3737e6f
Binary files /dev/null and b/docs/en/images/my-setting-group-page-contributor.png differ
diff --git a/docs/en/images/my-setting-group-ui.png b/docs/en/images/my-setting-group-ui.png
new file mode 100644
index 0000000000..b9d3f1b403
Binary files /dev/null and b/docs/en/images/my-setting-group-ui.png differ
diff --git a/docs/en/images/my-setting-group-view-component.png b/docs/en/images/my-setting-group-view-component.png
new file mode 100644
index 0000000000..02843f968e
Binary files /dev/null and b/docs/en/images/my-setting-group-view-component.png differ
diff --git a/docs/zh-Hans/CLI.md b/docs/zh-Hans/CLI.md
index 262f546bf2..4325ee1f07 100644
--- a/docs/zh-Hans/CLI.md
+++ b/docs/zh-Hans/CLI.md
@@ -39,6 +39,7 @@ dotnet tool update -g Volo.Abp.Cli
* **`translate`**: 当源代码控制存储库中有多个JSON[本地化](Localization.md文件时,可简化翻译本地化文件的过程.
* **`login`**: 使用你在[abp.io](https://abp.io/)的用户名和密码在你的计算机上认证.
* **`logout`**: 在你的计算机注销认证.
+* **`install-libs`**: 为 MVC / Razor Pages 和 Blazor Server UI 类型安装NPM包.
### help
@@ -339,3 +340,19 @@ abp login -p -o # You can enter both your
```
abp logout
```
+
+### install-libs
+
+为 MVC / Razor Pages 和 Blazor Server UI 类型安装NPM包, 它的 **执行目录** 或者传递的 ```--working-directory``` 目录必须包含一个项目文件(*.csproj).
+
+`install-libs` 命令读取 `abp.resourcemapping.js` 来管理包. 参阅[客户端包管理](UI/AspNetCore/Client-Side-Package-Management.md)了解更多细节.
+
+用法:
+
+````bash
+abp install-libs [options]
+````
+
+#### Options
+
+* ```--working-directory``` 或 ```-wd```: 指定工作目录, 当执行目录不包含项目文件时会很有用.
\ No newline at end of file
diff --git a/docs/zh-Hans/Modules/Setting-Management.md b/docs/zh-Hans/Modules/Setting-Management.md
index fd87dd734c..acb4469fea 100644
--- a/docs/zh-Hans/Modules/Setting-Management.md
+++ b/docs/zh-Hans/Modules/Setting-Management.md
@@ -83,4 +83,194 @@ namespace Demo
* `TenantSettingManagementProvider`: 获取或设定租户的设置值.
* `UserSettingManagementProvider`: 获取或设定用户的设置值.
-`ISettingManager` 在 `get/set` 方法中使用设置管理提供程序. 通常每个设置程序提供程序都在 `ISettingManagement` 服务上定义了模块方法 (比如用户设置管理程序提供定义了 `SetForUserAsync` 方法).
\ No newline at end of file
+`ISettingManager` 在 `get/set` 方法中使用设置管理提供程序. 通常每个设置程序提供程序都在 `ISettingManagement` 服务上定义了模块方法 (比如用户设置管理程序提供定义了 `SetForUserAsync` 方法).
+
+## Setting Management UI.
+
+设置管理模块默认提供了邮件设置页面并且它是可扩展的; 你可以为你的应用程序设置添加设置标签到设置页面.
+
+### MVC UI
+
+#### 创建视图组件
+
+在 `Components` 目录下创建 `MySettingGroup` 文件夹, 添加一个名为 `MySettingGroupViewComponent` 的视图组件:
+
+
+
+打开 `MySettingGroupViewComponent.cs` 替换为以下内容:
+
+```csharp
+public class MySettingGroupViewComponent : AbpViewComponent
+{
+ public virtual IViewComponentResult Invoke()
+ {
+ return View("~/Components/MySettingGroup/Default.cshtml");
+ }
+}
+```
+
+> 你还可以使用 `InvokeAsync` 方法,在这个示例中我们使用 `Invoke` 方法.
+
+#### Default.cshtml
+
+在 `MySettingGroup` 目录下创建 `Default.cshtml` 文件.
+
+打开 `Default.cshtml` 替换为以下内容:
+
+```html
+