tguillor
asked on
Command line arguments
VS 2005
We have a Windows app we inherited that has the following logic:
It's meant to be run from the console, with command line args. If no args are entered, then a form opens that allows the user to input the args. Since this app runs as a scheduled job, we'd like to be able to include the args in the job.
No matter what we enter at the command prompt, the form opens. It appears to be ignoring the args.
Is there anything we need to do within C# to signal the compiled version that args are expected?
We have a Windows app we inherited that has the following logic:
It's meant to be run from the console, with command line args. If no args are entered, then a form opens that allows the user to input the args. Since this app runs as a scheduled job, we'd like to be able to include the args in the job.
No matter what we enter at the command prompt, the form opens. It appears to be ignoring the args.
Is there anything we need to do within C# to signal the compiled version that args are expected?
Show us how you are reading the args in and processing them...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Small correction: you cam leave two lines
Application.EnableVisualSt yles();
Application.SetCompatibleT extRenderi ngDefault( false);
Application.EnableVisualSt
Application.SetCompatibleT