Angular run multiple apps in 1 project, Optionality bootstrap components

most posts you'll find talk about actually managing 2 totally different apps under 1 project, and that's best described here: https://yakovfain.com/2017/04/06/angular-cli-multiple-apps-in-the-same-project/ .

but what i really want to achieve is behavior more close to angular 1.x where you could write like 50 directives / components and put just set the ng-app attribute in your Aspx master page and it would just catch whatever is in, so in each page there were 2-10 directives and all was good.

with the angular-cli today its not native possible, but kouasda found a solution, where you test the page for the your angular tags and bootstrap them accordingly, as told in this issue and shown in this plnk.

eventually your app.module should look like this



import {BrowserModule, DOCUMENT} from '@angular/platform-browser'
import {NgModule, Inject, ApplicationRef} from '@angular/core'

import {AppRootOne} from './app-root-one.component'
import {AppRootTwo} from './app-root-two.component'



@NgModule({
  imports: [ BrowserModule ],
  declarations: [ AppRootOne, AppRootTwo ],
  entryComponents: [ AppRootOne, AppRootTwo ]
})
export class AppModule {


  private browser_document;


  ngDoBootstrap(appRef:ApplicationRef){
    if(this.browser_document


         .getElementsByTagName('app-root-one').length > 0){




       appRef.bootstrap(AppRootOne);


    }
    if(this.browser_document


         .getElementsByTagName('app-root-two').length > 0){




       appRef.bootstrap(AppRootTwo);


    }
  }


  constructor(@Inject(DOCUMENT) private document: any){
    this.browser_document = document;
  }
}










































Comments











Post a Comment































Popular posts from this blog









OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS





















game portal: http://overthewire.org/wargames/natas/  PASSWORDS for each level are stored in /etc/natas_webpass/natasX   I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all  the information needed to pass each level, yet not the solution.   For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st.    Natas  The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning.   If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the ...








Read more










Asp.Net Ending Response options, Response.End() vs CompleteRequest()





















this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement.   i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case.   the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it.   see this short article ab...








Read more










SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem





















if you got an error like this    The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 )   as well as these:   The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD )  the solution for me was to clear configuration cache (PS)  and then restart SP Search Services.   THX ...








Read more