Possible PowerTools problem #9949

8 Answer(s)

• 

  0

  ismcagdas created 3 years ago

  Support Team

  Hi @murphymj5209

  Thanks, we are checking this problem.

  Save Cancel
• 

  0

  musa.demir created 3 years ago

  Hi @murphymj5209

  I could not reproduce the problem. Can you please share a project that contains that problem. You can send it to [email protected]

  Save Cancel
• 

  0

  murphymj5209 created 3 years ago

  Can you let me know how to send? a) i would like to zip the file because of propietary work effort; I have 7-zip which can encrypt but then i would publish my password in this forum or in a seperate email b) how to 'just' send code, assuming that is what you are asking for; meaning no binaries and other dirs.Thanks.

  Question: I have the current PowerTools and it shows 2.7.6 but is there a way i can look at one or more of the RadTool files to make sure this is current? When the 'new' RadTools was installed, since I am using Github, i expected my RadTool Template files to be showm in an update. I do not remember seeing this happen.

  Save Cancel
• 

  0

  ismcagdas created 3 years ago

  Support Team

  Hi @murphymj5209

  You can check latest version of Power Tools on https://marketplace.visualstudio.com/items?itemName=Volosoft.AspNetZeroPowerTools. Power Tools automatically updates itself when you open Visual Studio. But, as you said, templates in your project is not updated automatically. In order to do that, best way is to follow this document https://docs.aspnetzero.com/en/common/latest/Version-Updating.

  For sharing your code, yes, please zip your solution without binaries (bin and obj folders) and also without node_modules folder. You can send this zip file to [email protected]. If you project your zip, you also need to send its password to [email protected].

  Thanks,

  Save Cancel
• 

  0

  autumn created 3 years ago

  I'm seeing the same problems even when using the latest version.

  eg: The latest version of PartialTemplates.txt contains import { LazyLoadEvent } from 'primeng/public_api'; but it should be import { LazyLoadEvent } from 'primeng/api';

  There a number of similar issues. To replicate, create a new entity using the RAD Tool, and verify the resulting client code is broken in ~40 places with errors like: 'sub-header' is not a known element Can't bind to 'description' since it isn't a known property of 'sub-header'. Can't bind to 'busyIf' since it isn't a known property of 'div'. No pipe found with name 'localize'. Can't bind to 'breadcrumbs' since it isn't a known property of 'sub-header'. 'validation-messages' is not a known element

  

  Save Cancel
• 

  0

  autumn created 3 years ago

  Update: Creating the entity under the Root menu works fine, so the admin module is probably missing some references...

  Save Cancel
• 

  0

  autumn created 3 years ago

  Add the following to admin.module.ts:

  import { CommonModule } from '@angular/common';
  import { FormsModule } from '@angular/forms';
  import { AppCommonModule } from '@app/shared/common/app-common.module';
  import { UtilsModule } from '@shared/utils/utils.module';
  

  and in the module imports below:

  @NgModule({
      imports: [
      ...,
      UtilsModule,
      AppCommonModule.forRoot(),
      CommonModule,
      FormsModule,
  

  Save Cancel
• 

  0

  murphymj5209 created 2 years ago

  closing problem

  Save Cancel