You can check the following document https://docs.microsoft.com/en-us/azure/devops/pipelines/packages/nuget-restore?view=azure-devops#restore-packages-with-nuget-restore-build-task
Hi @Tony_Albutt,
Commercial ABP Packages are not listed on NuGet.org, but nuget.abp.io .
You need to add this package source (to your NuGet sources). Example:
<add key="ABP Commercial NuGet Source" value="https://nuget.abp.io/{Your-Key}/v3/index.json" />
You can find this line in NuGet.Config file in your project. Check it to see {Your-Key} value.
I've refunded a credit.
Also,
We'll consider to SweetAlert2 https://github.com/abpframework/abp/issues/9413
Hi @viswajwalith,
ABP Framework uses SweetAlert, not SweetAlert2. Sorry for confusion.
I updated the documentation https://github.com/abpframework/abp/pull/9414/files
Hi,
Edit button only works if documents are received from GitHub.
I created an issue https://github.com/abpframework/abp/issues/9407
Hi @Leonardo.Willrich,
I'll review this PR again https://github.com/abpframework/abp/pull/8900
Hi,
You can create a new Blazor WebAssembly project with Same name as your MVC app. And then copy Blazor and Host projects to your MVC app. So you can keep current Application Layer & Domain Layer of your app and also have blazor UI of ABP Commercial modules.
However, new blazor project won't have your custom pages or changes. You have to manually make any pages or changes you had done for MVC app.
Volo.Docs.GitHub.Documents dependency injection problem and I soved this problem by added "typeof(DocsDomainModule)" to DependsOn attribute in DocsWebModule.cs. And also, I tried this way on our project and it also works. But, I'm not sure about thats a best solution.
For now, what you have done is a good way to make Docs module work on tiered template. It is not a best practice, but there are some issues with layer separation of this module and therefore you can continue this way. We'll check this issues.
You need to create new a Application Layer and a HttpApi Layer as well. So, you can move Book Api related code to new projects and keep module-related api's in old projects. Then reference just new projects from Acme.BookStore.WebApi.