Traditionally, handling command-line args in an app has been a simple case of reading arguments from the “int main()” function (or equivalent). In WPF this changes somewhat.
The usual setup is that you have your App.xaml.cs, which loads your initial window. While it’s the former that has access to the arguments, it’s the latter that is likely to use them. So the steps are:
Here’s one way to do it (demonstrating a single argument). Firstly, in App.xaml.cs:
1: protected override void OnStartup(StartupEventArgs e)
3: if (e.Args != null && e.Args.Count() > 0)
5: this.Properties["ArbitraryArgName"] = e.Args;
Then in the main window, you can access Application.Current.Properties to get at your args. However, if this happens to be the name of a file you want to load, you should probably wait until after your window has finished loading so that you can react to that file load (eg; give an error, display data, etc):
1: public MainContainer()
5: // Make sure we handle command line args:
6: this.Loaded += new RoutedEventHandler(MainContainer_Loaded);
9: void MainContainer_Loaded(object sender, RoutedEventArgs e)
11: if (Application.Current.Properties["ArbitraryArgName"] != null)
13: string fname = Application.Current.Properties["ArbitraryArgName"].ToString();
14: // Act on the file...
Launching via a double-click on a custom file type.
I created an application that supports a custom document format and I wanted a double-click on that document to open my application. I assumed that the application would open normally with the document presented as a command-line arg, but that’s not the case. Instead, it’s stored in the following tongue-twister:
So, if you revisit the OnStartup method in App.xaml.cs, you can query this location and store it in the same way you did the command-line arg:
3: // Check if this was launched by double-clicking a doc. If so, use that as the
4: // startup file name.
5: if (AppDomain.CurrentDomain.SetupInformation
6: .ActivationArguments.ActivationData != null
7: && AppDomain.CurrentDomain.SetupInformation
8: .ActivationArguments.ActivationData.Length > 0)
10: string fname = "No filename given";
13: fname = AppDomain.CurrentDomain.SetupInformation
16: // It comes in as a URI; this helps to convert it to a path.
17: Uri uri = new Uri(fname);
18: fname = uri.LocalPath;
20: this.Properties["ArbitraryArgName"] = fname;
23: catch (Exception ex)
25: // For some reason, this couldn't be read as a URI.
26: // Do what you must...
Notice the little trick with using the “Uri” class; this is because the string you’ll see will look like this: