Hello,
Because of bug and performance issues associated with the default WPF splash screen, the recommended solution across multiple forums seems to be to create a Native C++ application that displays the splash screen and then loads the WPF executable. There are certainly no shortages of examples online.
I've implemented an example located here http://www.olsonsoft.com/blogs/stefanolson/post/A-better-WPF-splash-screen.aspx (seems to be a pretty popular example). The example I've implemented works pretty well.
Now it's time to deploy these executables to the clients. I've been using ClickOnce all along, and this has been fine as there's only ever been one WPF project to deploy. With the addition of this Native C++ splash screen executable, I'm not sure how I'll go about deploying this app.
Ideally I'd like to have:
A) The splash screen exe be installed on the client's desktop. B) The WPF executable installed under Program Files.
(It is the splash screen exe that runs the WPF executable)
I'd like to do this with one installation. Under this scenario, how would the ClickOnce deploy handle checking for application updates for both the Native C++ AND WPF applications? Seems tricky to me.
If you have any ideas of have any better recommendations for me I'd like to hear them.
Thanks all!
Mike