I can't provide a way that works perfectly in any situation. Each module has different parts and extensions (maybe), the current version of CLI cant guarantee your module will be installed properly if you replace the cache, but it's a way to try.
For the current version (v5.0), the best way to install module is manual installation. Adding dependencies to .csproj files and
[DepensOn(typeof(...))]attribute over module class manually is the most consistent way.
@enisn Can you please explain the steps. I hardly understood what you said. I am new to abp.io framework. How to manually install a module? From where? There are 2 ways to install a module? Which way is appropriate for what? abp add-module abp new -t module Also there is a way to install a module using abp.io suite. How is that different from these 2 above.
I really think that apb.io should provide a template for microservices in community based abp.io version
I asked this question on stackoverflow: Extending IdentityUser (AppUser) in a DDD based abp.io application Now (after version 4.4+) that EntityFrameworkCore.DbMigrations was removed and AppUser custom class is removed or discouraged, I was wondering how to conveniently extend User profile/identity to have all kid of sorts of relationships: 1 to 1 1 to many many to 1 (+ extra simple property types) ... with IdentityUser so that EF migration works well, enable easy retrieval and updates to extra properties from GUI.
The documentation only mentioned a simple string type SSN and it is spread across many extensibility topics. It is not quite clear about GUI and EF migration adjustments to accommodate simple types, navigation properties, collections to other entities. I would like to see a more complex example following good DDD practice in the version 4.4/5+ involving these cases above. I am aware of many questions/answers about using AppUser, but there are hardly any decent examples on how to do it after removal of EF migration project. I would prefer to have a custom AppUser class where I can add extra properties and relationships.
Maybe I need to have 1 to 1 relationship between IdenityUser class and this new AppUser class. What if I want to have several classes of user that need to inherit from IdentityUser class? Thanks Rad
@enisn,
I really expected this flag to be part of add-module command.
What can I do in the meantime. I can certainly change a cached version of the zip.
What feature are you planning?
I noticed that add-modules adds its own common.props file per module on the solution level that each project uses. I expected these projects to use a common common.props on applicaton level which is ../../../.. away from module projects. I didn't see how to automate deploymnet for SaaS application based on abp.io and automated billing for resources used.
Rad
I want to have a total control over what my startup templates (app and module) migh look, so I can make my own changes to abp provided templates. For example I can successfully create a new application where I explicitly have app-4.4.4.zip inside D:/AbpStartupTemplates/rel-4.4/templates/app (with my change). Let's say I have a readme.file inside that Zipfile in asp.net-core folder.
abp correctly picks my local templated packaged in app-4.4.4.zip file: abp new Acme.Bookstore --template app --create-solution-folder true --ui mvc --tiered true --mobile none --dbms SqlServer --database-provider ef --connection-string Server=localhost;Database=AcmeBookstore;Trusted_Connection=True --no-random-port true --template-source D:/AbpStartupTemplates/rel-4.4/templates/app --version 4.4.4 --local-framework-ref --abp-path D:/abpdev --preview false
It seems that the add-module command doesn't have that option to select custom local --template-source argument. It is ignored. D:\TestApps\Ravco.Rstate> abp add-module Acme.Bookstore.Author --new --version 4.4.4 --template-source "D:/AbpStartupTemplates/rel-4.4/templates/module
I think that this is missing feature as it is needed to allow local template for module which might be modified from the original.
[06:06:45 INF] Creating your project... [06:06:45 INF] Project name: Acme.Bookstore. [06:06:45 INF] Template: module [06:06:45 INF] Version: 4.4.4 [06:06:45 INF] Output folder: D:\TestApps\Acme.Bookstore\modules\Acme.Bookstore.Author [06:06:46 INF] Using cached template: module, version: 4.4.4 [06:06:49 INF] Check out the documents at https://docs.abp.io/en/abp/latest/Startup-Templates/Module [06:06:50 INF] 'Acme.Bookstore.Author' has been successfully created to 'D:\TestApps\Acme.Bookstore\modules\Acme.Bookstore.Author'