Activities of "hitaspdotnet"

And the interface ICmsKitProDbContext have not NewsletterRecords prop

Some of entities uses ModuleDbContext instead of using IModuleDbContext https://github.com/abpframework/abp/blob/4495d7a3b1cb6a4aa816f29e2f8e5405ed68a6d5/modules/cms-kit/src/Volo.CmsKit.EntityFrameworkCore/Volo/CmsKit/Blogs/EfCoreBlogPostRepository.cs#L19

is this fixed? can I close it?

I have this problem too. Using cms-kit in adminService ---> Volo.Abp.AbpException: No configuration found for Microsoft.EntityFrameworkCore.DbContext, Microsoft.EntityFrameworkCore, Version=5.0.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60! Use services.Configure<AbpDbContextOptions>(...) to configure it.

any answer?

and add Cms-Kit to your new service.

This is my question! How? In my scenario I need cms features for our clients as remote service and should avaible for tenant admin to manage it. What about UI for public and admin web.

Check the EasyCrm sample from commercial doc website

This issue is becuase template version 'common.props' which is 1.0.0.0 and the abp framework version is '5.0.0.0' and the downloaded packages version is 4.4.0! I changed them to 4.4.0 and issue solved.

How to force licensing modules to use local framework references?

Any solution?

hi

Then we got packages dublicated. How to fix?

Can you share your steps and error messages?

1. Download framework (git repo)
2. Download all modules (+pro) with get-source abp cli
3. Create template pro using abp cli
4. reviewing project references for pro modules (cli bug with local framework reference)
5. Run

System.IO.FileLoadException: Could not load file or assembly 'Volo.Abp.Core, Version=4.4.0.0, Culture=neutral, PublicKeyToken=null'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)