2

We'd like to show one splash screen for Customer A and one for Customer B.

According to a stackoverflow answer, the splash screen can't be set at runtime, but I'd like to be sure.

I read an excellent article here on how to do it using build configurations. The problem is that my colleagues and I don't have faith in this method (though it works in my test app). If the system is copying files at runtime, something could go wrong.

A colleague suggested I could switch the splash screen at runtime by packaging it up in a dll. Please can someone tell me if this is possible?

I think it might be possible to amend the Package.appxmanifest at runtime, but this could be very difficult and risky to implement. (Discussed here.)

At the moment I have a separate Package.appxmanifest that I copy manually when I wish to switch from Customer A to Customer B. I think I'll have to carry on doing this.

Gail Foad
  • 623
  • 10
  • 22

1 Answers1

3

You can implement an "extended splash screen" which is configurable by the app at runtime, here is the MSDN doc on how to do this:

https://learn.microsoft.com/en-us/windows/uwp/launch-resume/create-a-customized-splash-screen

Stefan Wick MSFT
  • 13,600
  • 1
  • 32
  • 51
  • See as well https://stackoverflow.com/questions/47201701/removing-splash-screen-from-uwp-app-in-fcu which indicates how to make a splash screen optional unless Windows decides to display it anyway. – Richard Chambers Mar 14 '18 at 15:52
  • Thank you, Stefan. I've now got two splash screens. The first one can be generic for all customers. The second is customer-specific. – Gail Foad Mar 14 '18 at 16:58