Feature Request: Restart button in settings window

[karpovv-boris]

When you change the app language, you see this notice:

But some of you expected this:

Given that the application has a host we could tweak a little in the code to implement this for restarting the client.

[karpovv-boris]

So, I was trying to implement this, but stuck in RegisterApplicationRestart(...).
Which by the way works in this context (as it shows rmlogotest.exe):

How can I use RegisterApplicationRestart using pinvoke?

[Samuel12321]

This is something I have wanted to see for a while. Thanks @karpovv-boris for your help.

[Samuel12321]

Should we move this button to beside the language change selection like powertoys?

[karpovv-boris]

@Samuel12321 it seems logical. Other settings are 'reactive'.
Right now this notice note says that there are other items in the settings that may also require you to restart the app. Which is not.

[Samuel12321]

Any Updates @karpovv-boris, don't mean to bother you, just trying to plan the next few releases.

[karpovv-boris]

Still no cracking this. I'm stuck at dllmain.LoadCLR() in ModernFlyoutBridge and I don't quite understand how this is called.

[ShankarBUS]

Why do you go there? It is not necessary to look into the C++ side of the project. Everything you need is in the C# project.

[karpovv-boris]

I mean, it literally says // But the process will exit after .NET CoreCLR shuts down anyway so... *shrug*. Am I at wrong direction?

[ShankarBUS]

The C++ should be left untouch. It's purpose is only for loading the .NET project into a Microsoft Windows signed application.

You shouldn't modify it.

[Samuel12321]

@ShankarBUS perhaps instead of telling him where not to look, you could give him some direction on the best way to do this. 😉

[ShankarBUS]

Honestly, I am not sure. That's why I dropped the idea in first place.

I thought he might know something. I was just trying to tell him that the C++ project is not the right place.

[Samuel12321]

Google seems to suggest:

using System.Diagnostics;
using System.Windows;
...
Process.Start(Process.GetCurrentProcess().MainModule.FileName);
Application.Current.Shutdown();

CommonCommands.ExitAppCommand
May also work

[ShankarBUS]

Well wait a minute! Now I remember why I left this unimplemented. It is because every method that we know of start the application as unpackaged (like a normal exe), so, the app loses certain functionalities that require packaged privileges.

I tried every method I know, even the methods you two suggested. None of them will start the app as packaged.

[ShankarBUS]

We depend on certain WinRT APIs that require a package identity such APIs are app data, startup task and some others. Starting the app as unpackaged will result in serious issues such as unavailability of app data and etc.

[Samuel12321]

We may have to wait for reunion to make this possible, it seems like they are looking into solutions for this as part of their new lifecycle api's microsoft/WindowsAppSDK#111

[ShankarBUS]

Yeah, let's hope so