1

I have an application written in native c++ (MFC). Some dialogs in this application are written in C# and WPF. when I start the dialog for the first time (cold start) - it takes a very long time, but another run is already fast (warm start). Is it possible to improve performance by loading the appropriate assemblies when the splash screen is viewing, but not when the dialog is started for the first time? If so, in what way?

rgb
  • 1,750
  • 1
  • 20
  • 35
  • 1
    The [link](http://blogs.msdn.com/b/jgoldb/archive/2007/10/10/improving-wpf-applications-startup-time.aspx) on the first answer of that question tells you all you need to know. – Justin Mar 01 '13 at 14:11
  • This advice works for managed applications. If aplication is mixed (c++ and c#), above approach doesn't work. – rgb Sep 17 '13 at 12:39
  • Can you be more specific? What aspects of the linked question/answer don't apply and why? If you edit your question with these details then the question may be re-opened. – Justin Sep 17 '13 at 13:14

1 Answers1

0

Process your managed assemblies with ngen.exe during the installation of your software.

Native Image Generator

Ronnix
  • 310
  • 4
  • 12
  • This can help, but its only 1 of many options and probably not the one I'd investigate first. – Justin Mar 01 '13 at 14:11