Peter Viscarola wrote:
It is absolutely, positively, professionally irresponsible to RECOMMEND that
anybody build a driver for Windows XP or .NET 2003 using anything other than
the compiler and linker shipped in the DDK.
That’s not actually what he’s recommending. As best I can tell,
DriverStudio uses the DDK compiler and linker. I know I do, and I do all
of my development work from Visual Studio. There’s just one trick to
this, and that’s to launch MSDEV with the /USEENV option and the path
set to the DDK’s BIN directory. The /USEENV option causes builds to use
tools from the environment path instead of the Tools/Options/Directories
settings.
Many developers, including me, have a strong preference for using an IDE
with all of its ancillary tools. I would estimate that we’re currently
partway through a transition period that will see all of using some
flavor of Visual Studio, and perhaps some C++ class library, for driver
development a few years down the road. It’s a bit painful for the
pioneers, but we’re coping.
–
Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Now teaming with John Hyde for USB Device Engineering Seminars
Check out our schedule at http://www.oneysoft.com