what is wrong with help system?

[kathy]

I am trying to build a help system for my CE.NET device using
Studio.NET 2003. In my program(VB.NET), I declared:

<DllImport("Coredll.dll", CallingConvention:=CallingConvention.Winapi)>
Public Shared Function CreateProcess(ByVal moduleName As
String, ByVal fileName As String, ByVal para1 As IntPtr, ByVal para2 As
IntPtr, ByVal hWnd As Int32, ByVal para3 As Int32, ByVal para4 As
IntPtr, ByVal para5 As IntPtr, ByVal para6 As
IntPtr, ByVal info As PROCESS_INFORMATION) As Int32
End Function

Then call this function:

CreateProcess("\windows\peghelp.exe", "\windows\my_help.htm",
IntPtr.Zero, IntPtr.Zero, 0, 0, IntPtr.Zero, IntPtr.Zero,
IntPtr.Zero,info)

When I run program, I got the CE.NET device system help, not
my_help.htm.

Why?

 

[Peter Foot [MVP]]

You have double checked that the path exists? for example the extension is
htm not html

Peter

 

[kathy]

Yes, I ckeck it.

There is "" exsisted in \windows directory.

 

[kathy]

In fact, the same code works on Pocket PC, but failed on CE.NET device.

 

[kathy]

By the way, I try to use OpenNETCF Core.CreateProcess. But it seems the
CreateProcess does not exsist. Where I can find it?

 

[Peter Foot [MVP]]

Use OpenNETCF.Diagnostics.Process.Start("peghelp.exe",
"\windows\my_help.htm") - this provides a consistent model with the desktop
and .NETCF v2.0 functionality, so will make it easier to reuse your code
between versions.
I'm not familiar with the Windows CE version of peghelp, having used it only
on Windows Mobile devices, therefore this may be a limitation on the
platform.

Peter

 

[Paul G. Tobey [eMVP]]

OpenNETCF.Diagnostics.Process.

Paul T.