Hello,
- ABP Framework version: v7.0
- UI type: Blazor Server
- DB provider: EF Core
- **Tiered: Yes
- Exception message and stack trace:
- Steps to reproduce the issue:"
- 1 - Create a new project using the app-pro template. DbMigrator. Run. Everything is fine.
- 2 - Use ABP Suite, add the CmsKit Pro Module. The solution will not compile due to these errors about CmsKitProAdminBlazorServerModule and the namespace Volo.CmsKit.Pro.Admin.Blazor.Server.
By the way, during the process of adding the module... there is a prompt in background (command line window) asking to scroll and choose the version of the CmsKit pro... Why I should pick the version ?!?! Is this a default behavior of NuGet ?!?!
Thanks
I did another test using --with-public-website when creating my initial project, and then CmsKit Pro was already installed with all the needed package referenced.
But, let's say I don't want or need the public web site project in my solution...but still want to use some features of the CmsKit... Let's say I just want to use the UrlShorting feature in my Blazor project... Why adding the CmsKit Pro module is not worlking if my inital project don't have the public web part ? Should it work anyway ? I think so...
Any advice are welcome, thanks.
4 Answer(s)
-
0
Hi @FrancoisLabelle,
Sorry for the late reply. I will try to test it during the day and get back to you. Thank you for your understanding.
-
0
First of all, thank you for the detailed information you provided.
I've looked into your issue. Here are my findings:
2 - Use ABP Suite, add the CmsKit Pro Module. The solution will not compile due to these errors about CmsKitProAdminBlazorServerModule and the namespace Volo.CmsKit.Pro.Admin.Blazor.Server.
I could not reproduce this problem, so no build errors occurred. Maybe you are encountering a temporary problem because the package cannot be restored. That's why I recommend you to build the project. In addition,
SuiteandABP CLImust be the same as the version of the project you created. Could you please check them?By the way, during the process of adding the module... there is a prompt in background (command line window) asking to scroll and choose the version of the CmsKit pro... Why I should pick the version ?!?! Is this a default behavior of NuGet ?!?!
I had this problem too. If I do not choose the version while installing the client-side packages, the Suite cannot progress and users may not be aware of this situation because it does not give any warnings. I will open an issue to improve this situation.
But, let's say I don't want or need the public web site project in my solution...but still want to use some features of the CmsKit... Let's say I just want to use the UrlShorting feature in my Blazor project... Why adding the CmsKit Pro module is not worlking if my inital project don't have the public web part ? Should it work anyway ? I think so...
Yes, it should work as expected. See more: https://docs.abp.io/en/commercial/latest/modules/cms-kit/index
-
0
I did have the same exact questions about version selector but i think it's good to have an option to choose just in case you need an older version.
The public website and the CMS Kit, it's kinda related so i guess. you should keep it both in your project even if you don't need it, you can just publish one of them. I faced the same issue when i was trying the Blazor Server Version.
-
0
Hi @rafael.gonzales,
Thanks for the additional information.
I did have the same exact questions about version selector but i think it's good to have an option to choose just in case you need an older version.
Unfortunately, I do not agree with this. We always recommend that the packages be of the same version, as there can be breaking changes between the two versions, that may prevent the application from working as expected. Therefore, by default, the version of the project and the version of the packages to be added must be the same.
The problem will be solved in the next patch version of
7.0.*. Here is the relevant PR.
