Handle file activation and init boostraping

[mfe-]

Opening a prism uwp app by the file type association, results in a hanging app (You only see the splash screen, no view will be loaded)

Steps to reproduce:

1. Open Package.appxmanifest
2. Go to Declarations and add File Type association
3. Association for example a jpg file
4. call contextmenue in windows explorer on a jpg file. select open with. select your app.
5. Only spash screen will be displayed.

This is behavior is caused by not calling InitializeShell.

Changes proposed in this pull request:

Override OnFileActivated and call OnActivated to initiate the "bootstrapping" process of prism.

[dnfclas]

Hi @mfe-, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

[dnfclas]

@mfe-, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, DNFBOT;

[bartlannoeye]

What triggered the change of this file?

[mfe-]

Sry, I dont know. I modified the PrismApplication.cs and did a rebuild.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.