Command Line Arguments

[Brian Scott]

Is it possible to get the full command line argument string that was used to
launch your current process other than using the args[]. I would like to see
the original string before the args are interpreted.

Thanks.

[Dennis Myrén]

System.Environment.CommandLine
--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"Brian Scott" <Br***@MosaicSoftware.co.uk> wrote in message
news:d3*******************@news.demon.co.uk...

Is it possible to get the full command line argument string that was used
to
launch your current process other than using the args[]. I would like to
see
the original string before the args are interpreted.

Thanks.

[James Curran]

the Environment.CommandLine property.

"Brian Scott" <Br***@MosaicSoftware.co.uk> wrote in message
news:d3*******************@news.demon.co.uk...

Is it possible to get the full command line argument string that was used to launch your current process other than using the args[]. I would like to see the original string before the args are interpreted.

Thanks.

[Brian Scott]

Cheers, that helped.

"James Curran" <ja*********@mvps.org> wrote in message
news:e7*************@TK2MSFTNGP15.phx.gbl...

the Environment.CommandLine property.

"Brian Scott" <Br***@MosaicSoftware.co.uk> wrote in message
news:d3*******************@news.demon.co.uk...

Is it possible to get the full command line argument string that was

used to

launch your current process other than using the args[]. I would like to

see

the original string before the args are interpreted.

Thanks.

[FriscoSoxFan]

string arguments = String.Join(" ", args);

[Brian Scott]

Frisco,

That is what i was using prior but using the Environment variable seems
better as we can also see the execution path. I was trying to debug invalid
user enterred arguments.

Thanks

"FriscoSoxFan" <ju**@kreusch.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...

string arguments = String.Join(" ", args);

[Dennis Myrén]

You cant however rely on that the execution path is in that string.

The user might have changed directory prior to start your application:
cd c:\dev
YourApp "An Argument"
or he might not:
c:\dev\YourApp.exe "An Argument"

but you are probably aware of that already.

--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"Brian Scott" <Br***@MosaicSoftware.co.uk> wrote in message
news:d3*******************@news.demon.co.uk...

Frisco,

That is what i was using prior but using the Environment variable seems
better as we can also see the execution path. I was trying to debug
invalid
user enterred arguments.

Thanks

"FriscoSoxFan" <ju**@kreusch.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...

string arguments = String.Join(" ", args);

[Brian Scott]

No I wasn't aware, thanks for pointing that out.
"Dennis Myrén" <de****@oslokb.no> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

You cant however rely on that the execution path is in that string.

The user might have changed directory prior to start your application:
cd c:\dev
YourApp "An Argument"
or he might not:
c:\dev\YourApp.exe "An Argument"

but you are probably aware of that already.

--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"Brian Scott" <Br***@MosaicSoftware.co.uk> wrote in message
news:d3*******************@news.demon.co.uk...

Frisco,

That is what i was using prior but using the Environment variable seems
better as we can also see the execution path. I was trying to debug
invalid
user enterred arguments.

Thanks

"FriscoSoxFan" <ju**@kreusch.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...

string arguments = String.Join(" ", args);

[Dennis Myrén]

If you want the path to your application at runtime, you can do:
string fullPath =
System.Reflection.Assembly.GetExecutingAssembly(). Location;

--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"Brian Scott" <Br***@MosaicSoftware.co.uk> wrote in message
news:d3*******************@news.demon.co.uk...

No I wasn't aware, thanks for pointing that out.
"Dennis Myrén" <de****@oslokb.no> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

You cant however rely on that the execution path is in that string.

The user might have changed directory prior to start your application:
cd c:\dev
YourApp "An Argument"
or he might not:
c:\dev\YourApp.exe "An Argument"

but you are probably aware of that already.

--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"Brian Scott" <Br***@MosaicSoftware.co.uk> wrote in message
news:d3*******************@news.demon.co.uk...

> Frisco,
>
> That is what i was using prior but using the Environment variable seems
> better as we can also see the execution path. I was trying to debug
> invalid
> user enterred arguments.
>
> Thanks
>
> "FriscoSoxFan" <ju**@kreusch.com> wrote in message
> news:11**********************@g14g2000cwa.googlegr oups.com...
>> string arguments = String.Join(" ", args);
>>
>
>