Activities of "MILLENNIUM"

This solution still have problems, when you have both lepton theme source code and account source code, you cannot change the style of the theme, (you still read the value from node module)

Hi Paul

1. The theme-lepton library gets style files from node_modules/@volo/abp.ng.theme.lepton/dist folder. You should overwrite the CSS files after building. So you can use a command to achieve this like the following:

yarn ng build theme-lepton && cp -r packages/theme-lepton/dist dist/theme-lepton 

Then check the styles in dist/theme-lepton/dist/styles folder. You will see your edited styles there.

2. You should add a variable named appInfo. This custom footer component works:

import { EnvironmentService } from '@abp/ng.core'; 
import { Component } from '@angular/core'; 
 
@Component({ 
  selector: 'app-footer', 
  template: ` 
    <footer class="lp-footer"> 
      <div class="d-flex"> 
        <div class="mr-auto"> 
          <span>2019 - {{ currentYear }} © {{ appInfo.name }}</span 

> ><br />

    </div> 
  </div> 
</footer> 

`, styleUrls: ['./footer.component.scss'], }) export class FooterComponent { currentYear = new Date().getFullYear();

get appInfo() { return this.environment.getEnvironment().application; }

constructor(private environment: EnvironmentService) {} }

 
3. Here is the `tsconfig.prod.json`:  
 

{ "compileOnSave": false, "compilerOptions": { "baseUrl": "./", "outDir": "./dist/out-tsc", "sourceMap": true, "declaration": false, "downlevelIteration": true, "experimentalDecorators": true, "module": "esnext", "moduleResolution": "node", "importHelpers": true, "target": "es2015", "typeRoots": ["node_modules/@types"], "lib": ["es2018", "dom"], "types": ["jest"] }, "angularCompilerOptions": { "fullTemplateTypeCheck": true, "strictInjectionParameters": true } }

 
`tsconfig.json`: 
 

{ "extends": "./tsconfig.prod.json", "compilerOptions": { "paths": { "@volo/abp.commercial.ng.ui": ["packages/commercial-ui/src/public-api.ts"], "@volo/abp.ng.account": ["packages/account/src/public-api.ts"], "@volo/abp.ng.account/config": ["packages/account/config/src/public-api.ts"], "@volo/abp.ng.account/admin": ["packages/account/admin/src/public-api.ts"], "@volo/abp.ng.audit-logging": ["packages/audit-logging/src/public-api.ts"], "@volo/abp.ng.audit-logging/config": ["packages/audit-logging/config/src/public-api.ts"], "@volo/abp.ng.identity-server": ["packages/identity-server/src/public-api.ts"], "@volo/abp.ng.identity-server/config": ["packages/identity-server/config/src/public-api.ts"], "@volo/abp.ng.identity": ["packages/identity/src/public-api.ts"], "@volo/abp.ng.identity/config": ["packages/identity/config/src/public-api.ts"], "@volo/abp.ng.saas": ["packages/saas/src/public-api.ts"], "@volo/abp.ng.saas/config": ["packages/saas/config/src/public-api.ts"], "@volo/abp.ng.theme.lepton": ["packages/theme-lepton/src/public-api.ts"], "@volo/abp.ng.theme.lepton/": ["packages/theme-lepton/src/lib/"], "@volo/abp.ng.language-management": ["packages/language-management/src/public-api.ts"], "@volo/abp.ng.language-management/config": [ "packages/language-management/config/src/public-api.ts" ], "@volo/abp.ng.language-management/locale": ["packages/language-management/locale/src/public-api.ts"], "@volo/abp.ng.text-template-management": [ "packages/text-template-management/src/public-api.ts" ], "@volo/abp.ng.text-template-management/config": [ "packages/text-template-management/config/src/public-api.ts" ] } } }

Thank you Mehmet, This worked!

Hi @MILLENNIUM, @bqabani

Warning: Entry point '@volo/abp.ng.account/config' contains deep imports into '......./angular/projects/account/admin/src/public-api.ts'. This is probably not a problem, but may cause the compilation of entry points to be out of order. Error: Failed to compile entry-point @volo/abp.ng.account/config (es2015 as esm2015) due to compilation errors: projects/account/admin/src/account-settings.module.ts:28:14 - error NG6002: Appears in the NgModule.imports of AccountConfigModule, but could not be resolved to an NgModule class. Is it missing an @NgModule annotation? 28 export class AccountSettingsModule {}

To resolve the problem above, first, you should add a file named tsconfig.prod.json with the below content to angular folder.

{ 
  "compileOnSave": false, 
  "compilerOptions": { 
    "baseUrl": "./", 
    "outDir": "./dist/out-tsc", 
    "sourceMap": true, 
    "declaration": false, 
    "downlevelIteration": true, 
    "experimentalDecorators": true, 
    "module": "esnext", 
    "moduleResolution": "node", 
    "importHelpers": true, 
    "target": "es2015", 
    "typeRoots": ["node_modules/@types"], 
    "lib": ["es2018", "dom"], 
    "types": ["jest"] 
  }, 
  "angularCompilerOptions": { 
    "fullTemplateTypeCheck": true, 
    "strictInjectionParameters": true 
  } 
} 

Then open the package.json and add the following scripts:

"scripts": { 
 ... 
 "compile:ivy": "yarn ngcc --properties es2015 browser module main --first-only --create-ivy-entry-points --tsconfig './tsconfig.prod.json' --source node_modules", 
 "postinstall": "npm run compile:ivy" 
  }, 

After this configuration, you should remove yarn.lock and run the yarn command.

There is a problem with ngcc. It can not resolve the paths in tsconfig.json correctly. The solution above is just a trick.

Hi @Mehmet,

I tried, I don't think so, the issue occures after you create a new application with the latest version, and then install both lepton source code and account pro source code (replace packages with source code)

The ngcc compiler must use the library from 'project' folder in angular app, but looks there is some missing configuration in the project, Now I did a small change to make the project run (cause I have to work on my tasks, unitl I find a solution) , I commented out importing the Account Config module, and it worked successfuly, but the menu in admin menu is missing some links now

After creating new project with Lepton theme source code embeded and account module source code embeded, I got the folloing error:

Warning: Entry point '@volo/abp.ng.account/config' contains deep imports into 'FOLDER/angular/projects/account/admin/src/public-api.ts'. This is probably not a problem, but may cause the compilation of entry points to be out of order.

Error: Failed to compile entry-point @volo/abp.ng.account/config (es2015 as esm2015) due to compilation errors: projects/account/admin/src/account-settings.module.ts:11:14 - error NG6002: Appears in the NgModule.imports of AccountConfigModule, but could not be resolved to an NgModule class.

Is it missing an @NgModule annotation?

11 export class AccountSettingsModule {} ~~~~~~~~~~~~~~~~~~~~~ projects/account/admin/src/account-settings.module.ts:11:14 - error NG6003: Appears in the NgModule.exports of AccountConfigModule, but could not be resolved to an NgModule, Component, Directive, or Pipe class.

Is it missing an Angular annotation?

11 export class AccountSettingsModule {} ~~~~~~~~~~~~~~~~~~~~~

Dears, I think the issue was because I was publishing the system with microservices to localhost, and they was an exception because of use self-signed certificate on my local server, I managed to solve the issue by changing the following code:

context.Services.AddAuthentication() .AddJwtBearer(options => { options.Authority = configuration["AuthServer:Authority"]; options.RequireHttpsMetadata = Convert.ToBoolean(configuration["AuthServer:RequireHttpsMetadata"]); ; options.Audience = "WorkflowDemo"; options.BackchannelHttpHandler = new HttpClientHandler() { ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator }; });

Dears, Any update on this? we cannot publish any abp project, event if it is autogenerated by suite!

No You cannot, You can only access templates and edit them.

The abp suite is published at this location, name may be differency according to your versions:

C:\Users*USERNAME*.dotnet\tools.store\volo.abp.suite*4.1.2*\volo.abp.suite*4.1.2*\tools\net5.0\any