I am a software engineer. I have been working with C++, MFC, and .net technologies for 15 years. I like video games and reading books.
We know that functions will sometimes take parameters and process it. Similarly, executable applications also take parameters and switches and it behaves based on the parameters passed to it. In this article, we will see how do we pass command line parameters to an MFC Dialog based applications. The approach is same for other applications like single document and multi-document applications.
2. Creating a dialog based application
First, we will create a dialog-based application and name it as CommandLineDlg. That is the name we had chosen but we are not restricting one to keep the same name.
Once the application is created, using the class view add a class to the solution. We are naming the class as CCommandParse. Make this class derived from CCommandLineInfo. This class declaration is shown below:
Creating the dialog based application is shown in the below video (No Audio):
Creating MFC Dialog Based Application (No Audio)
3. The CCommandLineInfo Derived class
We have two MFC string Arrays declared in this class. One will hold command line data and another one will hold command line switches. Switches will tell how the application should behave based on the information passed for processing. The Get functions will receive reference parameters and copies the String Array values from the class’s member variable.
We override the ParseParam function of the base class CCommandLineInfo. Because of this, we will get the opportunity to process every param passed from the command line.
Below is the Full Class definition:
The application calls ParseParam function for each command line parameters (data and switches) and this function will store the command line arguments to m_params or m_switches flags, which is the second parameter to the function. Below is the overridden function:
AS already told, the get functions will copy the command line arguments to the corresponding local member variables. The code is straightforward, and it is given below:
That all the changes we need for the CCommandParse class. Now, we will move to the Application Instance and make the changes. We will use the class which we defined just now.
4. Application Instance Parsing Params & Switches
We discussed about the custom parser in In the previous section. In the application class, we use it to parse the command-line arguments. We declare the GetCommandLinePasrser in the CWinApp class to receive the command line parameters. It takes references to the CStringArray instances to know the command-line parameters and parameter switches. Finally, we declare our custom parser written in the previous section as the member variable. The entire header file is shown below:
The Application calls the InitInstance function when it initializes the application and other resources. From InitInstance, we call the ParseCommandLine function and pass our custom parser to it as an argument.
Now, the MFC Framework is aware of the extended functionality offered by our Custom Parser. For each command line arguments passed, MFC will now call our overridden ParseParam member function CCommandParse. Note that we derived it from the class CCommandLineInfo. Below is the piece of code:
We will make a call to GetCommandLineParser from OnInitDialog handler of our dialog class. We have not written the call so for. First, let is write what the GetCommandLineParser of the dialog class do.
The GetCommandLineParser which is implemented in the Application class will copy the Parameters and switches to the internal members of our Custom Parser. This is done through the Getter Functions. Below is the code:
5. The Dialog class
In the dialog, we just have two list boxes. The dialog template edited by IDE is shown below:
The dialog will get the application instance and passes two string arrays by reference to the member function exposed by it. The application instance will make a call to our custom command line parser to copy the parameters and switches to its member variables. Once the dialog knows the parameters and switches, it will display it in the corresponding list boxes.
All the above said stuff is done in the OnInitDialog member function of the dialog. Look at the below piece of code:
First, we make a call to the GetCommandLinePasrser of Application instance. The function will fill the passed CStringArray with parameters and switches. Once the dialog has the information, it displays those by adding it to the corresponding m_lst_params, m_lst_switches by iterating through the CStringArray instances.
After the call, our dialog has the command line information in the CStringArray instances. Using a for loops, we iterate through each CStringArray and display the content in the CListBox instances. The AddString function of the CListBox instance is used to display the Parameters and Switches.
6. Testing the Example
The attached sample can be tested in two different ways. The first way is going to the command prompt and executing the exe by passing the command line argument. The second way is passing the static parameters by setting the debug property of the project. The second method is useful when we want to debug the sample.
Below video shows passing the command line argument (with switches) from the command prompt.
Video: Testing the Example from Command Line Window (No Audio)
Below video shows perform debugging with command line arguments.
Video: Debugging the MFC Example with Command-Line Arguments (No Audio)
Source Code: DownLoad
© 2018 sirama
Andrew Truckle on May 14, 2020:
Hi. Thanks for the article. What about where you want to support both? Eg:
In other words, extracts all command line flags and any file passed. See: