Interesting though, that it happens only when I run unit tests from VS 2005
with JetBrain's UnitRun. The same tests ran with FitNesse, or ran on "Vista
on Mac" run just fine. Seems like it might be an issue of a configuration,
rather then WPF.
Any ides what I could use to profile the process?
"Iniialization" part takes about 10 seconds.
"Laurent Bugnion, MVP" wrote:
> Roman wrote:
> > My unit test uses XamlReader.Load to load a XAML document from embedded
> > resource, it takes about 5 seconds before first test is executed - following
> > test cases are executed fast. It seems as if it takes long time for WPF
> > components to get loaded/initialized.
> > Where can I get more info on this process?
> > What can I do to optimize that?
> Is your embedded resource XAML or BAML? Set the "content" to Page in
> Visual Studio to compile the XAML in BAML and speed the loading process.
> Laurent Bugnion [MVP ASP.NET]
> Software engineering, Blog: http://www.galasoft.ch
> PhotoAlbum: http://www.galasoft.ch/pictures
> Support children in Calcutta: http://www.calcutta-espoir.ch