What’s new in WPF 3.5 SP1: Splash Screen to improve perceived startup perf

a-foton » What???s new in WPF 3.5 SP1: Splash Screen to improve perceived startup perf

Tue, 12 Aug 2008 23:29:17 GMT

PingBack from http://blog.a-foton.ru/2008/08/what%e2%80%99s-new-in-wpf-35-sp1-splash-screen-to-improve-perceived-startup-perf/

re: What’s new in WPF 3.5 SP1: Splash Screen to improve perceived startup perf

lvovan — Wed, 13 Aug 2008 02:59:01 GMT

Hi Josef, for the "Does not support earlier versions of VS" caveat, isn't it just for Approach A?

WPF SplashScreen Template

Lester's WPF blog — Thu, 14 Aug 2008 17:33:46 GMT

The Splashscreen feature was part of SP1. However, there was no VS template to get it done fast. We have

re: What’s new in WPF 3.5 SP1: Splash Screen to improve perceived startup perf

jgoldb — Thu, 14 Aug 2008 21:49:00 GMT

WRT "Does not support earlier versions of VS" caveat. Yes, you should still be able to use the SplashScreen APIs (e.g. Approach C)

[WPF] SplashScreen pour WPF en .NET 3.5 sp1

Frédéric Hamel — Tue, 19 Aug 2008 08:20:01 GMT

Le démarrage des applications .NET et notamment WPF surtout à froid peut parfois être un problème car

re: What’s new in WPF 3.5 SP1: Splash Screen to improve perceived startup perf

robburke — Fri, 12 Sep 2008 23:56:22 GMT

Thank you very much for a thorough description of how to use the Splashscreen!

I have tried using Approach A and Approach C, and in both instances my application sometimes throws a Win32Exception on the Close(timeSpan) method if I switch focus from my app to another app while it is loading.

This sometimes happens to me, for instance, if I go back to Visual Studio during a debug session, or when I answer OneCare's question about allowing my app to access the internet. Here is the top of the exception's stack trace:

Unhandled Exception in application AppDomain: System.ComponentModel.Win32Exception: The operation completed successfully

at MS.Win32.UnsafeNativeMethods.SetActiveWindow(HandleRef hWnd)

at System.Windows.SplashScreen.Close(TimeSpan fadeoutDuration)

... could I trouble you for any advice for how to resolve this?

I am working around the issue for now by using Approach C, and my call to Close(timeSpan) is wrapped in a try/catch block to get the Win32Exception. If the exception is thrown, I try again to close the SplashScreen whenever my application's main window is activated.

re: What’s new in WPF 3.5 SP1: Splash Screen to improve perceived startup perf

jgoldb — Sat, 13 Sep 2008 01:01:04 GMT

to robburke :

I was wondering, are you closing the SpalshScreen Window from another thread (you should close it from the UI thread) ?

If not:

Do you see this on XP & Vista?

Can you send me a little sample with the repro ?

Thanks

Jossef

re: What’s new in WPF 3.5 SP1: Splash Screen to improve perceived startup perf

frenk — Wed, 17 Sep 2008 11:08:04 GMT

I'm having the same problem as robburke.

The exception comes now and then, maybe once every 10 startups.

I used approach A), now I'm testing with C).

[WPF] SplashScreen pour WPF en .NET 3.5 sp1

Frédéric Hamel — Sun, 21 Sep 2008 23:57:53 GMT

Le démarrage des applications .NET et notamment WPF surtout à froid peut parfois être un problème car

Win32 Exception: "The operation completed successfully"

teknohippy — Wed, 24 Sep 2008 10:09:00 GMT

I'm also having the same problem as robburke.

This is on Vista.

I'm using the API with an AutoClose. I'm also forcing a single instance of my App, not sure if that's got anything to do with it.

re: What’s new in WPF 3.5 SP1: Splash Screen to improve perceived startup perf

robburke — Fri, 03 Oct 2008 06:28:18 GMT

Hi jgoldb -- at first, using approach A, I was closing from whatever thread it "automatically" gets closed from, and getting this exception.

Now, using approach C, I am closing from the UI thread, in an event handler hooked up to my main window's Activated event. Still getting the exception using this technique.

Like the other respondants above, this happens maybe once out of every ten times I run the app, but I am able to repro it quite reliably by running in the debugger, and, when the splashscreen is displayed but before my main window has loaded and become visible, I click on Visual Studio to bring the focus away from the splashscreen and to Visual Studio.

This is on Vista SP1.

I can't send you the repro right now as the project is massive (and contains my clients' IP). Have you managed to repro this? Sounds like I am not the only one experiencing the issue. Please drop me mail if I can help somehow.

Synchronizing splashscreen fade away with main window

e28makaveli — Wed, 17 Dec 2008 07:38:42 GMT

Silly question but is there a way for one to synchronize complete fade away of splash screen with main window launch?

Now, before the splash screen completely fades away my main window launches. I want the main window to launch only after the splash screen has completely faded away.

Any ideas?