1

I noticed that even the most basic Winform application (ie. just a window, with no extra modules) still takes several seconds to load after creating its machine code equivalent through Ngen. I guess then that the bottleneck is loading the .Net framework from disk.

Microsoft's CacheSet doesn't allow managing the actual contents of the disk cache.

Is there an application that can force Windows to keep the main .Net files in its disk cache, as a work-around to slower startup time for .Net applications?

Thank you.

Edit: Here's the screenshot of Process Monitor's Process Timeline: enter image description here

Chenmunka
  • 3,264
OverTheRainbow
  • 5,779

1 Answers1

0

The .NET framework does have a slight lag the first time the framework is loaded into memory, but nothing of the scale you speak of. Are you running with a debugger?

Alternatively you can see whether signed .NET assemblies are trying to get to crl.microsoft.com, which can introduce a delay depending on network conditions. Use Process Monitor for this.

In fact, Process Monitor will identify for you, step by step, what's happening when you run something, and you can narrow down the problem much easier than guessing.