Re: Writing Device Drivers in Visual Studio

I'll try to look at those settings in more detail or maybe someone else will
spot the problem, but to answer the easy question, no, you can deploy a DLL
to a device without any problem (you can't run it, obviously, without
setting the Debug settings to specify what program is the user).

Can you tell my why you'd deploy a driver to a location other than \windows?

Paul T.

"Michael H" <MichaelH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5A7D9FDE-7E76-4EEA-8CEF-10E6A0B7C3E6@xxxxxxxxxxxxxxxx
Hello Paul,

sorry for the less information but I hoped someone can give me a general
proceeding.

The target is connected via Ethernet.
The Target Settings are:
Transport: TCP ->Static IP address

The project settings are:
in PCIDriver.vcproj
...
<DeploymentTool
ForceDirty="-1"
RemoteDirectory="%CSIDL_PROGRAM_FILES%\PCIDriver"
RegisterOutput="0"
AdditionalFiles=""
/>
...

in PCIDriver.vcproj.<Domain>.<User>
...
<DebuggerTool
RemoteExecutable="%CSIDL_PROGRAM_FILES%\PCIDriver\PCIDriver.dll"
Arguments=""
/>
...

I made this procedure several times in the same kind -always working fine.
I compared the setting of the DLL project with these working projects -
there are no differences in the settings!

Is it a problem that I only want to copy the dll to my target - without
any
application (.exe)?

"Paul G. Tobey [eMVP]" wrote:

"All settings aren't working" means nothing. You'll have to tell us how
you
have VS connected to the device, what settings you're using that are not
the
defaults, etc.

Paul T.

"Michael H" <MichaelH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3855275E-8316-4293-92EA-37D8F6B2F308@xxxxxxxxxxxxxxxx
Hello Paul,

thanks for your reply. Now it is working. I forgot to make the settings
for
the module definition.
But i still have a problem with the deploy of the dll. How can I deploy
(copy) the dll to the target system with Visual Studio tools? All
settings
i
change (Deploypath...) aren't working.

Michael

"Paul G. Tobey [eMVP]" wrote:

Yes, in theory. A device driver is just a DLL with a specific set of
exported functions defined. If you build such a DLL in VS2005, it
will
work. "Something failed" isn't of much use... Make sure that the
exported
functions are declared extern 'C', if you're writing in C++, or use a
DEF
file to remove the decorations from the names.

Paul T.

"Michael H" <MichaelH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:144577FD-C8AF-4EF8-BDC7-A5E5F51685B7@xxxxxxxxxxxxxxxx
Hello CE World,

is it possible to write Stream Device Drivers for WindowsCE 5.00
with
Visual
Studio 2005?
I tried by creating a Projekt with a DLL Wizard for intelligent
Devices
but
something failed.

Thank for your answers.








.

Relevant Pages

  • Re: VS2005 compatibility
    ... Paul T. ... I know the Link have the Heap and Stack memory settings. ... The EXE could really be bad. ... You say "I can download the program to the target device to run ...
    (microsoft.public.windowsce.app.development)
  • Re: VS2005 compatibility
    ... Thanks for your info, Paul. ... I know the Link have the Heap and Stack memory settings. ... The EXE could really be bad. ... You say "I can download the program to the target device to run it". ...
    (microsoft.public.windowsce.app.development)
  • Re: VB6 runtime is supported on Windows 7
    ... The settings window was fairly extensive ... DLL and the settings are organized into a UDT rather ...
    (microsoft.public.vb.general.discussion)
  • Re: Writing Device Drivers in Visual Studio
    ... With this, you can put the reg keys for you driver into the image, but not include the driver DLL in any .bib file. ... I change the driver and deploy it to the target via network folder (the ... setting the Debug settings to specify what program is the user). ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Writing Device Drivers in Visual Studio
    ... The target is connected via Ethernet. ... The project settings are: ... Is it a problem that I only want to copy the dll to my target - without any ... exported functions defined. ...
    (microsoft.public.windowsce.platbuilder)