(1) This would be a parsing error in the 1.1 framework. Probably an
unwanted side effect of the built-in feature where \" is interpreted as
an escape sequence, combined with the fact that users don't usually
bother to specify a path with a trailing slash.
(2) This would be a parsing error introduced in the 2.0 framework.
--Bob
[quoted text, click to view] Mike Harrington wrote:
> Two-part question:
>
> 1) Why does the .NET 1.1 framework treat \" as an escape character, but
> does not recoginize any other characters?
>
> Example:
>
> a commandline argument of:
>
> MyProgram "C:\Program Files\"
>
> would process the token as:
>
> args[0] C:\Program Files"
>
> My second question is....
>
> Why does the .NET 2.0 framework process command-line arguments differently
> than the 1.1 framework?
>
> In the .NET 1.1 framework an argument of:
>
> MyProgram -test:"C:\Program Files"
>
> would be
>
> args[0] -test:C:\Program Files
>
> whereas .NET 2.0 is:
>
> args[0] -test:"C:\Program
> args[1] files"
>
>
>
>
> Anyone have any clues?
>
