Is the IIS (8) application Initialization really a better alternate then having a PowerShell script running as an scheduled task to keep the loading times down after an IISreset / server restart / application pool timeout ?
I'm looking into if this can replace a PowerShell script.
I have yet to find some really good arguments for using the IIS extension instead of a script. Are there any possible consequences of running the application initialization in a production environment? Could there be any impact to the performance?
The PowerShell cmdlet
Invoke-WebRequest works great for warming up SharePoints HTML/CSS but we have some custom apps developed that still takes a very long time to load after an application pool has been restarted.