3 ms·
ngen had a lot of problems though. It was very easy to accidentally invalidate it. There was no easy reliable way to "ship" an ngen output. There was no easy wa
by eddythompson80 3y ago
ngen had a lot of problems though. It was very easy to accidentally invalidate it. There was no easy reliable way to "ship" an ngen output. There was no easy way to even check if its even loading. your best option was to run ngen on the target machine, which is fine for services as a deployment step. But it's not like you could build and publish an AOT .NET cli for example.
- pjmlp 3y agoSure, as mentioned its key cases was fast startup for desktop applications. The installation was supposed to take care of calling into ngen.
- marwis 3y agoI think not shipping ngen output was desired. There was an NGen Optimization Service that would reoptimize code when net framework was updated and possibly with new profiling data.
- pjmlp 3y agoIt is still there for those of us that have to deal with .NET Framework.