🚀 go-pugleaf

"KLinZ" <klinz@NOSPAMMERTSzenobits.com> schreef in bericht
news:bqnmou$2sv$1@hermes.castel.nl...
> Muse wrote:
>
> > Ik probeer een bestand te openen van uit een listbox. Het path kopmt
> > prima door, maar ik krijg het maar niet voor elkaar op het te openen.
> > Een .exe lukt prima. Maar als ik een doc of pdf wil openen, dan werkt
> > het niet. Het gaat dus om een willekeurig bestand.
>
> Hoe ziet de code eruit die het bestand opent? Gebruik je
> System.Diagnostics.Process.Start()? Staat UseShellExecute op true?
>
> -- 
> www.zenobits.com
>

Voor de volledigheid, ofwel je gebruikt :
Shell("c:\winnt\notepad.exe", AppWinStyle.MaximizedFocus, False, -1)

Ofwel je gebruikt :
Dim p As System.Diagnostics.Process = New Process()
p.StartInfo.FileName = "c:\winnt\notepad.exe"
p.StartInfo.WindowStyle = ProcessWindowStyle.Maximized
p.StartInfo.UseShellExecute = False
p.Start()
The code shown above would still launch Notepad without changing
UseShellExecute but p.Start() would call ShellExecuteEx rather than
CreateProcess as called by Shell.

Although more coding is required to use it, the Process class is more
powerful than the Shell method. Like its Visual Basic 6 precursor,
Microsoft.VisualBasic.Interaction.Shell is only capable of launching files
that are executable files (such as .exe and .bat files). Its call chain
leads to CreateProcess in the Win32 API. The Process class also calls
CreateProcess when Process.StartInfo.UseShellExecute is explicitly set to
False. Otherwise Process.Start uses the operating system shell to launch the
specified file. If the file is non-executable or a URI, the OS shell opens
the file or resource using the default action for that file or URI type
(that is, the default verb-usually open). Using the operating system shell
in Visual Basic 6 requires a Declare statement to call the API function
directly.

Using the Process class with UseShellExecute = False is sometimes slightly
faster than the Shell method but the very slight performance gain is
negligible and insignificant against the overhead of loading a new process
unless you are launching dozens of short-lived processes from the UI thread.

Recommendation: For launching only executable files, there is no compelling
performance reason to choose Process over Shell, and Shell is often more
productive. Use Process when features not provided by Shell are required
(for example, I/O redirection or UseShellExecute).

Aldus de MSDN library...