I should have made a thread about this a long time ago, but it seems that the compile-force option doesn't seem to work. The reason this was implemented, if I recall correctly, was that in the event of launching a process as admin, all environment variables were lost. I believe compile-force was an attempt to fix this, but the variables still do not show up in the properties of the admin processes.
Environment variables are supposed to be lost as you switch contexts. Compile-force has nothing to do with that at all. Compile-force is for apps that do not behave correctly when the launcher asks for admin after it has been run and then passes that to the actual app. It's required most of the time as most utilities don't work properly when the launcher isn't set to require admin and advertise it to the OS.
Sometimes, the impossible can become possible, if you're awesome!
I remember Chris asking me to test if it fixed the issues I was having back when he implemented that feature (the issues in question being the issues I'm mentioning now), so I couldn't remember if it was specifically for that or if he wanted to see if it killed two birds with one stone.
Now that that's been clarified, is language switching officially considered not working for apps that require admin privileges then?
That's correct. We'll have to pass it all through using command line switches or something similar. I may come up with something at the platform level instead.
I have several admin apps that have the switching in place, though, for when it works.
Sometimes, the impossible can become possible, if you're awesome!
Most of mine are set to use language switching as well, so as soon as this is sorted my apps will use it without requiring any updates.