Home/ Questions/Q 7033063
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T01:00:52+00:00

Is there a clean way to access the commandline arguments passed as part of

  • 0

Is there a clean way to access the commandline arguments passed as part of an AppDomain.ExecuteAssembly call that starts a WPF application?

I’m spinning up a WPF application in a separate app domain and passing arguments to the application like so:

AppDomain moduleDomain = AppDomain.CreateDomain("Friendly Name");
moduleDomain.ExecuteAssembly(path, new[] { "arg1", "arg2" });

There’s a work-around to access these arguments, since both Environment.GetCommandLineArgs() and StartupEventArgs return the commandline arguments for the original application, not the one spun up with ExecuteAssembly().

I would like to access the arguments passed to the WPF application without having to manually define a Main method, preferably using StartupEventArgs. Is there a way to do so?

Starting the WPF application in a separate process works, but has performance penalties and complicates debugging.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Tigran’s comment lead me to a solution that I’m happy with, using AppDomain.SetData instead of using command line arguments. The basic outline looks like this:

    AppDomain moduleDomain = AppDomain.CreateDomain("Friendly Name");
moduleDomain.SetData("arg1", "arg1Value");
moduleDomain.SetData("arg2", "arg2Value");
moduleDomain.ExecuteAssembly(path);

    Then, to access the ‘arguments’ in the WPF app:

    string arg1Value = AppDomain.CurrentDomain.GetData("arg1");
string arg2Value = AppDomain.CurrentDomain.GetData("arg2");

    This works well for my use case.

    • 0