opening mspaint

[Tam]

Having problems with this code.

ProcessStartInf o info = new ProcessStartInf o();
info.FileName = ("mspaint.exe") ;
info.Arguments = image.getFileNa me; // returns full path and name
info.ShellExecu te = false;
Process p1 = ProcessStart(in fo);

Problem arises on complicated pathnames. If the string returned in
info.Arguments is in say c:\pics\pic1.bm p then it loads fine. Only when
cming from say the desktop is there a problem, it doesnt load the file and
informs me it cant find c:\Documents.bm p (regardless of contents of
getFileName();

Whats happening?

[Peter Rilling]

Spaces can throw any path out-of-whack. Try wrapping the path to the
document in quotation marks before launching the process. The shell thinks
the path ends after the first space. Although a nuisance, it does make
sense when you think about it. Applications can accept any number of
parameters and if spaces are used to separate them, it is difficult for the
system to know what is a delimiter and what is a valid character within the
parameter.

"Tam" <jo***********@ btclick.com> wrote in message
news:bm******** **@titan.btinte rnet.com...

Having problems with this code.

ProcessStartInf o info = new ProcessStartInf o();
info.FileName = ("mspaint.exe") ;
info.Arguments = image.getFileNa me; // returns full path and name
info.ShellExecu te = false;
Process p1 = ProcessStart(in fo);

Problem arises on complicated pathnames. If the string returned in
info.Arguments is in say c:\pics\pic1.bm p then it loads fine. Only when
cming from say the desktop is there a problem, it doesnt load the file and
informs me it cant find c:\Documents.bm p (regardless of contents of
getFileName();

Whats happening?

[Juan Gabriel Del Cid]

Remember that spaces are delimiters. So, if you run:

mspaint.exe C:\Documents and Settings\Deskto p\MyAss.bmp

you are sending 3 arguments to mspaint.exe (separated by spaces). What you
want to do is group them into one argument with double quotes:

mspaint.exe "C:\Documen ts and Settings\Deskto p\MyAss.bmp"

So, in your code you would have:

info.Arguments = "\"" + image.getFileNa me + "\"";

That should work,
-JG

[Tam]

Ok, sure, should have got that one. DOH

Thanks fellas, workred a treat ;-)

"Peter Rilling" <pe***@nospam.r illing.net> wrote in message
news:Ot******** ********@TK2MSF TNGP09.phx.gbl. ..

Spaces can throw any path out-of-whack. Try wrapping the path to the
document in quotation marks before launching the process. The shell thinks the path ends after the first space. Although a nuisance, it does make
sense when you think about it. Applications can accept any number of
parameters and if spaces are used to separate them, it is difficult for the system to know what is a delimiter and what is a valid character within the parameter.

"Tam" <jo***********@ btclick.com> wrote in message
news:bm******** **@titan.btinte rnet.com...

Having problems with this code.

ProcessStartInf o info = new ProcessStartInf o();
info.FileName = ("mspaint.exe") ;
info.Arguments = image.getFileNa me; // returns full path and name
info.ShellExecu te = false;
Process p1 = ProcessStart(in fo);

Problem arises on complicated pathnames. If the string returned in
info.Arguments is in say c:\pics\pic1.bm p then it loads fine. Only when
cming from say the desktop is there a problem, it doesnt load the file and informs me it cant find c:\Documents.bm p (regardless of contents of
getFileName();

Whats happening?