Developing Windows Drivers With Visual Studio

re: Developing Windows Drivers With Visual Studio

strik — Wed, 30 Jan 2008 09:56:41 GMT

Hello,

just a small note: There are two versions of DDKBUILD available, the one from OSR (http://www.osronline.com/article.cfm?article=43) as well as the one from Hollistech (http://www.hollistech.com/Resources/ddkbuild/ddkbuild.htm). From my experience, the Hollistech one seems to be "one step in front" of the OSR one, but this is just my own experience.

Both versions are written from the same person, Mark Roddy. When he left OSR, he took the tool with him. However, OSR is also doing updates on it, but - as it seems - with a slower pace.

re: Developing Windows Drivers With Visual Studio

strik — Wed, 30 Jan 2008 09:57:40 GMT

Sorry, forgot my name in the previous posting. ;)

Spiro

re: Developing Windows Drivers With Visual Studio

hs2 — Wed, 30 Jan 2008 14:54:19 GMT

Consider to use Visual Slickedit (http://www.slickedit.com/) for driver development incl. symbol tagging ('Intellisense'), easy integration of any commandline based build tool with error parsing, etc.

IMHO it's more than just an alternative.

re: Developing Windows Drivers With Visual Studio

Stephen Paterson — Wed, 30 Jan 2008 17:19:37 GMT

Ok, you've got to convince Patrick to let us know what voodoo is required to to get WDK help to integrate with VS2005.

re: Developing Windows Drivers With Visual Studio

Kumar — Thu, 17 Apr 2008 01:11:49 GMT

Try sourceinsight from www.sourceinsight.com. Combined with ddkbuild its the best!

re: Developing Windows Drivers With Visual Studio

fat_boy — Sat, 14 Jun 2008 16:20:48 GMT

I have been using VS6 to develop drivers for 10 years. I like it because of intelisense, browse info (OK, it doesnt work if you use the 6000 compiler but it does with the 3790 and earlier compilers, and, you can develope Vista drivers with the 3790 compiler) and the general layout of the editor. It also easier to fix the usual code errors with VS than with the build env.

Wheh it compiles cleanly in VS I then use the build env to make a build for testing, and for release drivers of course I always use the build env.

re: Developing Windows Drivers With Visual Studio

rcohn — Tue, 20 Jan 2009 09:36:30 GMT

In my previous company, I used VS for years to develop kernel drivers by ensuring that the necessary build environment variables were set and the necessary compile and link flags were set into the project. The drivers seemed to work just fine.

However, more recently in my current company, I was easily able to use VS to use the DDK build executable and build the driver by creating a "Makefile" type project.

I invoke VS from a script that first calls the DDK setenv script for CHK or FRE to set the environment and then launch VS on the driver solution. This works fine, and I don't have to worry about setting all the DDK compile and link flags myself. And I get all of the Intellisense and other IDE tools. So when we go from Vista to Windows 7, I won't have to worry about making discrete build flag changes; that all comes along with the new DDK.