The current version is 10.5 and I think they're close to releasing v11.0 they are using angular version +12.1
There is a chance what you're talking about was an issue but that has likely since been corrected over past 4-5 years (looks like version 4.6 was around June 2017)
Check https://github.com/aspnetzero/aspnet-zero-core to see if there is an issue opened for that failure or upgrade to 10.5
can you open the package.json file in the angular solution and tell me what "version" it lists?
What version of the accplication are you using, ASPNetZero 10.5? Or something older?
I have not done it in a while but reviewing contents of the Account directory, yes - you should only need that one file out of the auth directory - and all the others (email-activation, login, password, and shared) are not needed for what you are doing
I wouldn't feel confortable with that, but you don't need it really
Just follow this:
Your idea is how I did exactly what you're asking with one exception - "...and name it public..." - I wouldnt use 'public' as a folder identifier but that's just my personal preference
look at account-routing.module.ts file - based on what you said your expected result is, you're just going to have to modify that page as well as the account.component.html accordingly
Depending on how closely you want to integrate your new page changes where you chose to bounce out of the application to go to the other page you're referring to
First thing you might need to look into is possibly root-routing.module.ts - that's usually where I've been adding that functionality and then adding my modules and components under src/{here} I think to save time you can consider copying the entire DIR 'account' and ripping out about 90% of it so you're just left with:
and then modify root-routing to just be:
{
path: 'account',
loadChildren: () => import('account/account.module').then(m => m.AccountModule), //Lazy load account module
data: { preload: true }
},
{
path: 'landing',
loadChildren: () => import('landing/landing.module').then(m => m.LandingModule), //Lazy load landing module
data: { preload: true }
},
set a breakpoint on the canActivate method in your new Landing route guard to verify expected behavior
Done - should I now close this ticket?
https://github.com/aspnetzero/aspnet-zero-core/issues/4017
We were having performance issues and I found this ticket
one of the first comments didnt seem to make sense: "4.4 mb and it is a bit high."
After some investigation I found we were having a compression issue. Our files now range about 1MB down from ~4.5MB
For more info see: https://docs.microsoft.com/en-us/iis/extensions/iis-compression/iis-compression-overview
I wanted to comment because I recently ran into this issue
When you update the installed Node, Angular, and Angular CLI software on your computer you can gain better processing and bundling
As far as sizes are concerned if you already updated Node/Angular, when you build in production mode your files should be optimized
If you are seeing that there is large file sizes loading to the browser which is causing performance issues, look into compression.
If you're on IIS: https://docs.microsoft.com/en-us/iis/extensions/iis-compression/iis-compression-overview
@sagaracorp
Are you running on IIS? If so you can set your API so that it never has downtime and then the application should always "Be Fast" on any attempt What we've seen is the default settings set the API to sleep and then the first person to hit the page will have to wait until everything is online
https://forums.asp.net/t/1950241.aspx?ASP+NET+MVC+website+goes+to+sleep+How+to+nake+it+always+awake+