Re: About "ActivateDevice"
- From: "<ctacke/>" <ctacke[@]opennetcf[dot]com>
- Date: Thu, 1 Jun 2006 11:02:26 -0400
Since I'm curious, you're saying your platform by default doesn't have the
drivers loaded? Why not simply adjust the registry for the capbilities of
the driver (setting the driver's Flags entry to not start for example)
rather than doing it at the app level?
Again, I'm not sure I agree with the design, but then it's not my platform.
For P/Invoke there are a couple good introductory articles in MSDN - that's
the best place to start.
For this specific case, here's the definition:
[DllImport("coredll.dll", SetLastError=true)]
public extern static IntPtr ActivateDevice(string lpszDevKey, int
dwClientInfo);
Chris Tacke
OpenNETCF Consulting
www.opennetcf.com
<jamesa@xxxxxxxxxxxx> wrote in message
news:1149147118.524443.63320@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Chris,
To be honest, I am simply trying to simplify my platform deployment.
I have a 'standard' platform that includes all the drivers & registry
entries for all the possible hardware supported on my device, and I aim
to customise the capabilities of the device simply by starting the
required drivers...
Do you have any good examples of using P/Invoke? I've never needed to
play with the API from C# before...
Thanks,
James
.
- References:
- Re: About "ActivateDevice"
- From: jamesa
- Re: About "ActivateDevice"
- Prev by Date: Re: Installer
- Next by Date: Re: Installer
- Previous by thread: Re: About "ActivateDevice"
- Next by thread: Re: Custom transparency not working on Win CE device
- Index(es):
Relevant Pages
|
