You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was stumbling across the problem, that CLI-parameters (or the one defined within the launchsettings.json) do not get reported via the OnLaunched LaunchActivatedEventArgs.Argument-Property. Couldn't this be streamlined?
Otherwise I have to check args.Arguments and Environment.GetCommandLineArgs() for possible provided arguments. This is espacially necessary together with Uno Plattoform, as WASM provides the parameters via args.Argument but WinUI does not.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I was stumbling across the problem, that CLI-parameters (or the one defined within the launchsettings.json) do not get reported via the OnLaunched
LaunchActivatedEventArgs.Argument
-Property. Couldn't this be streamlined?Otherwise I have to check
args.Arguments
andEnvironment.GetCommandLineArgs()
for possible provided arguments. This is espacially necessary together with Uno Plattoform, as WASM provides the parameters via args.Argument but WinUI does not.Beta Was this translation helpful? Give feedback.
All reactions