Why is wpf so slow

I have a super simple project for you right here. The command tries to open a WPF window in Rhino. However on my machine the first time the command it run it takes seconds for the window to appear, then every other time it is nearly instantaneous. I have noticed the delay as well, although in my case with an SSD it is only a couple of seconds at most, and have always attributed it to that.

If you watch your output window in Visual Studio , you will need a number of DLLs loaded when your command is run which is probably the delay you are seeing. Are you seeing this only when running in the Visual Studio debugger?

If that is the case, you may be waiting for symbols downloading from Microsoft. Or just click the Rhino icon on your desktop or from your start menu like any normal user would do. Then you are certain not to run the debugger. I can make a video if that helps. FrameworkContentElement fce, System. GetChildValueHelper System. DependencyProperty dp, System. DependencyObject container, MS. FrameworkObject child, int childIndex, bool styleLookup, ref System.

EffectiveValueEntry entry, out System. ValueLookupType sourceType, System. GetChildValue System. DependencyObject container, int childIndex, MS. FrameworkObject child, System. DependencyProperty dp, ref MS. FrameworkObject fo, System. DependencyProperty dp, ref System.

GetRawValue System. PropertyMetadata metadata, ref System. EvaluateBaseValueCore System. EvaluateEffectiveValue System. EntryIndex entryIndex, System. PropertyMetadata metadata, System. EffectiveValueEntry oldEntry, System. EffectiveValueEntry newEntry, System. UpdateEffectiveValue System. EffectiveValueEntry oldEntry, ref System. InvalidateProperty System. InvalidateContainerDependents System.

DependencyObject container, ref MS. DoStyleInvalidations System. Style oldStyle, System. Style newStyle Unbekannt PresentationFramework. UpdateStyleCache System. Style newStyle, ref System. Style styleCache Unbekannt PresentationFramework. OnStyleChanged System. DependencyObject d, System. OnPropertyChanged System. NotifyPropertyChange System. InvalidateStyleAndReferences System. The method ICommand. CanExecute is called by WPF to check if a bound command is available on the view.

Typical examples are context menu entries or buttons that call ICommand. Execute when clicked. If a command is not available, the corresponding button or context menu entry is disabled and cannot be pressed by the user.

It becomes problematic if a large number of commands are bound and there is code in the method ICommand. CanExecute that performs intensive operations, e. CanExecute is called very often, also when building and updating interfaces, so expensive CanExecute calls can make the interface very sluggish.

You can see this best by using a performance profiler. Here it depends on the application how you optimise the performance. For example, you can. In part 2 of the performance optimisation of WPF applications I take a look at unnecessary visuals and the optimisation of the VisualTree by the custom control with OnRender. Furthermore, it is about reducing ResourceDictionary lookups and relieving UI threads. Click here for part 2. Peter Friedland has published further articles here in the t2informatik Blog, including.

Peter Friedland works at t2informatik GmbH as a software consultant. In various customer projects he develops innovative solutions in close cooperation with partners and local contact persons. And from time to time he also blogs. What does t2informatik actually do?