[Bug 1574] New: Shellexecute, bug 22, and MSDN

[Wine Bugs]

http://bugs.winehq.com/show_bug.cgi?id=1574

Summary: Shellexecute, bug 22, and MSDN
           Product: Wine
           Version: unspecified
          Platform: All
               URL: http://msdn.microsoft.com/library/default.asp?url=/libra
                    ry/en-
                    us/shellcc/platform/shell/reference/functions/shellexecu
                    te.asp
        OS/Version: Linux
            Status: NEW
          Keywords: conformance
          Severity: normal
          Priority: P2
         Component: wine-kernel
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
OtherBugsDependingO 22
             nThis:

Looking at the URL above and then looking at our shlexec.c, I noticed one small 
difference between the 2.

In the MSDN docs, it says that if lpOperation is null:

"For systems prior to Microsoft Windows 2000, the default verb is used if it
is valid and available in the registry. If not, the "open" verb is used.

For Windows 2000 and later systems, the default verb is used if available. If
not, the "open" verb is used. If neither verb is available, the system uses
the first verb listed in the registry."

In wine's shlexec.c, if lpOperation is null, we only use the open verb, like
so:

if (lpOperation == NULL) /* default is open */
        lpOperation = "open";

I think this could hinder certain programs, especially if someone would like
it to do something besides open the file (like in the case of bug 22, where
it is a link, not a file)..  This could also be a problem if there is no
application associated with the file, since we have no window/tool allowing
the user to choose the app (also in the case of bug 22, where we have nothing 
to open links yet)...

I guess I should add that in the code for shlexec.c we do have handling for
links, but it appears to not make it that far as of right now..

I am also waiting on a tracelog from andy for bug 22 to see exactly where it 
stops