Missing --template-source parameter when creating a module using abp add-module command #2225

5 Answer(s)

• 

  0

  enisn created 3 years ago

  Support Team .NET Developer

  Hi @Radoslav

  You're right, we can't support custom source while adding module right now.

  We're working some amazing feature that solves that problem but it'll take a little bit more time and won't be shipped with v5.0

  Save Cancel
• 

  0

  Radoslav created 3 years ago

  @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

  Save Cancel
• 

  0

  enisn created 3 years ago

  Support Team .NET Developer

  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 [DependsOn(typeof(...))] attribute over module class manually is the most consistent way.

  Save Cancel
• 

  0

  Radoslav created 3 years ago

  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

  Save Cancel
• 

  0

  enisn created 3 years ago

  Support Team .NET Developer

  You need to add project references first.

  Same project layers should be referenced by same project layer. For example:

  • YourApp.Domain -> YourModule.Domain

  • YourApp.Domain.Shared -> YourModule.Domain.Shared

  • YourApp.Application -> YourModule.Application

  • YourApp.Application.Contracts -> YourModule.Application.Contracts

  • YourApp.HttpApi -> YourModule.HttpApi

  • YourApp.HttpApi.Client -> YourModule.HttpApi.Client

  • YourApp.Web -> YourModule.Web

  ...

  To do that operation, go to your .csproj file, for example YourApp.Domain.csproj and add following reference:

    <ItemGroup>
    
      ...
    
      <!-- Place correct path to your module -->
      <ProjectReference Include="..\..\modules\YourModule.Domain\YourModule.Domain.csproj" />
    <ItemGroup>
  

  Then you should add the DependsOn attribute over your YourAppDomainModule class:

  [DependsOn(typeof(YourModuleDomainModule))] // <-- Add this line.
  public class YourAppDomainModule : AbpModule
  {
      // ...
  }
  

  And make this step for each layer.

  Save Cancel