Build the WDF driver using VS2010

NTDEV
1

Hi All,

I’m trying to build my WDF driver using VS2010. After finishing several project settings, I can compile the driver successfully and the binary is generated to the target directory. However, once being installed, it causes the BSOD in the DriverEntry when calling the WdfDriverCreate. It never happens if I compile it with the NTBuild in WDK enviroment.

I know it may be caused by my dumb project setting in the VS2010 but I don’t know which setting can be wrong. Can anyone here shed me a light? For your convinience, I paste the output of the !analyze -v in the windbg for your reference.

ADDITIONAL_DEBUG_TEXT:
Use ‘!findthebuild’ command to search for the target build information.
If the build information is available, run ‘!findthebuild -s ; .reload’ to set symbol path and load symbols.

FAULTING_MODULE: 82e0d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ec5c50e

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
+c00f9
00000000 ?? ???

EXCEPTION_RECORD: 8ad2352c – (.exr 0xffffffff8ad2352c)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000000
Attempt to execute non-executable address 00000000

CONTEXT: 8ad23110 – (.cxr 0xffffffff8ad23110)
eax=85002000 ebx=00000000 ecx=84deb5d8 edx=00000000 esi=84deb5d8 edi=85002000
eip=00000000 esp=8ad235f4 ebp=8ad23610 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 9b8919a4 to 00000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8ad235f0 9b8919a4 00000000 84deb5d8 85002000 0x0
8ad23610 9b89a671 84deb5d8 85002000 8ad23660 RzFilter!WdfDriverCreate+0x24 [e:\winddk\7600.16385.1\inc\wdf\kmdf\1.9\wdfdriver.h @ 219]
8ad23698 82fb0740 84deb5d8 85002000 c000035f RzFilter!DriverEntry+0x161 [e:\work\heidi\rig\overlay\rzfilter\rzfilter.c @ 120]
8ad2387c 82fb7fff 00000000 00000001 8ad238a4 nt+0x1a3740
8ad23928 82ffce13 9e6ae180 00000001 9e6ae154 nt+0x1aafff
8ad23960 830050f8 00000007 8ad23a2c c0000034 nt+0x1efe13
8ad239cc 82fb527d 40000000 800009c0 8ad23a48 nt+0x1f80f8
8ad23aa8 82fb488e 866cb460 8ad23cd0 84e24e18 nt+0x1a827d
8ad23ca4 82fbd681 866cb460 84e24e18 8ad23cd0 nt+0x1a788e
8ad23cd8 82e20f56 82f70e80 84caf798 82f475bc nt+0x1b0681
8ad23d00 82e7af3b 00000000 00000000 84caf798 nt+0x13f56
8ad23d50 8301b6d3 00000001 a3fac2de 00000000 nt+0x6df3b
8ad23d90 82ecd0f9 82e7ae2e 00000001 00000000 nt+0x20e6d3
00000000 00000000 00000000 00000000 00000000 nt+0xc00f9

FOLLOWUP_IP:
RzFilter!WdfDriverCreate+24 [e:\winddk\7600.16385.1\inc\wdf\kmdf\1.9\wdfdriver.h @ 219]
9b8919a4 5d pop ebp

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: RzFilter!WdfDriverCreate+24

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RzFilter

IMAGE_NAME: RzFilter.sys

STACK_COMMAND: .cxr 0xffffffff8ad23110 ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

Thanks,
Marshall

2

EIP=0. Driver is trying to execute code at a function pointer that is NULL.

The best thing to do is to look at the data structures your driver is
creating in memory using the debugger and verify they are correct. If you
want to develop a driver using VS, use VS11 because that is designed for
creating drivers, whereas VS10 does not support that. Also you should load
proper symbols.

Sam Tertzakian
www.zorsoft.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Thursday, November 17, 2011 7:03 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Build the WDF driver using VS2010

Hi All,

I’m trying to build my WDF driver using VS2010. After finishing several
project settings, I can compile the driver successfully and the binary is
generated to the target directory. However, once being installed, it causes
the BSOD in the DriverEntry when calling the WdfDriverCreate. It never
happens if I compile it with the NTBuild in WDK enviroment.

I know it may be caused by my dumb project setting in the VS2010 but I don’t
know which setting can be wrong. Can anyone here shed me a light? For your
convinience, I paste the output of the !analyze -v in the windbg for your
reference.

ADDITIONAL_DEBUG_TEXT:
Use ‘!findthebuild’ command to search for the target build information.
If the build information is available, run ‘!findthebuild -s ; .reload’ to
set symbol path and load symbols.

FAULTING_MODULE: 82e0d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ec5c50e

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx
referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
+c00f9
00000000 ?? ???

EXCEPTION_RECORD: 8ad2352c – (.exr 0xffffffff8ad2352c)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000000
Attempt to execute non-executable address 00000000

CONTEXT: 8ad23110 – (.cxr 0xffffffff8ad23110)
eax=85002000 ebx=00000000 ecx=84deb5d8 edx=00000000 esi=84deb5d8
edi=85002000
eip=00000000 esp=8ad235f4 ebp=8ad23610 iopl=0 nv up ei ng nz ac po
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010292
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 9b8919a4 to 00000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8ad235f0 9b8919a4 00000000 84deb5d8 85002000 0x0
8ad23610 9b89a671 84deb5d8 85002000 8ad23660 RzFilter!WdfDriverCreate+0x24
[e:\winddk\7600.16385.1\inc\wdf\kmdf\1.9\wdfdriver.h @ 219]
8ad23698 82fb0740 84deb5d8 85002000 c000035f RzFilter!DriverEntry+0x161
[e:\work\heidi\rig\overlay\rzfilter\rzfilter.c @ 120] 8ad2387c 82fb7fff
00000000 00000001 8ad238a4 nt+0x1a3740
8ad23928 82ffce13 9e6ae180 00000001 9e6ae154 nt+0x1aafff
8ad23960 830050f8 00000007 8ad23a2c c0000034 nt+0x1efe13 8ad239cc 82fb527d
40000000 800009c0 8ad23a48 nt+0x1f80f8
8ad23aa8 82fb488e 866cb460 8ad23cd0 84e24e18 nt+0x1a827d
8ad23ca4 82fbd681 866cb460 84e24e18 8ad23cd0 nt+0x1a788e
8ad23cd8 82e20f56 82f70e80 84caf798 82f475bc nt+0x1b0681
8ad23d00 82e7af3b 00000000 00000000 84caf798 nt+0x13f56
8ad23d50 8301b6d3 00000001 a3fac2de 00000000 nt+0x6df3b
8ad23d90 82ecd0f9 82e7ae2e 00000001 00000000 nt+0x20e6d3
00000000 00000000 00000000 00000000 00000000 nt+0xc00f9

FOLLOWUP_IP:
RzFilter!WdfDriverCreate+24
[e:\winddk\7600.16385.1\inc\wdf\kmdf\1.9\wdfdriver.h @ 219]
9b8919a4 5d pop ebp

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: RzFilter!WdfDriverCreate+24

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RzFilter

IMAGE_NAME: RzFilter.sys

STACK_COMMAND: .cxr 0xffffffff8ad23110 ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

Thanks,
Marshall

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

Building drivers is not natively supported in Visual Studio unless
you’re fine with running preview version of VS2011. The only way of
making it work on VS2010 and earlier is to create makefile project and
use ddkbuild script (either from Hollistech or OSR) - the driver still
won’t be built by VS compiler/linker but you have nice integration of
WDK build and VS IDE.

Btw. not that it matters much in this case but next time you should
fix your symbols before posting !analyze -v output.

Kris

On Fri, Nov 18, 2011 at 3:02 AM, wrote:
> Hi All,
>
> I’m trying to build my WDF driver using VS2010. After finishing several project settings, I can compile the driver successfully and the binary is generated to the target directory. However, once being installed, it causes the BSOD in the DriverEntry when calling the WdfDriverCreate. It never happens if I compile it with the NTBuild in WDK enviroment.
>
> I know it may be caused by my dumb project setting in the VS2010 but I don’t know which setting can be wrong. Can anyone here shed me a light? For your convinience, I paste the output of the !analyze -v in the windbg for your reference.
>
> ADDITIONAL_DEBUG_TEXT:
> Use ‘!findthebuild’ command to search for the target build information.
> If the build information is available, run ‘!findthebuild -s ; .reload’ to set symbol path and load symbols.
>
> FAULTING_MODULE: 82e0d000 nt
>
> DEBUG_FLR_IMAGE_TIMESTAMP: ?4ec5c50e
>
> EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
>
> FAULTING_IP:
> +c00f9
> 00000000 ?? ? ? ? ? ? ? ???
>
> EXCEPTION_RECORD: ?8ad2352c – (.exr 0xffffffff8ad2352c)
> ExceptionAddress: 00000000
> ? ExceptionCode: c0000005 (Access violation)
> ?ExceptionFlags: 00000000
> NumberParameters: 2
> ? Parameter[0]: 00000008
> ? Parameter[1]: 00000000
> Attempt to execute non-executable address 00000000
>
> CONTEXT: ?8ad23110 – (.cxr 0xffffffff8ad23110)
> eax=85002000 ebx=00000000 ecx=84deb5d8 edx=00000000 esi=84deb5d8 edi=85002000
> eip=00000000 esp=8ad235f4 ebp=8ad23610 iopl=0 ? ? ? ? nv up ei ng nz ac po nc
> cs=0008 ?ss=0010 ?ds=0023 ?es=0023 ?fs=0030 ?gs=0000 ? ? ? ? ? ? efl=00010292
> 00000000 ?? ? ? ? ? ? ? ???
> Resetting default scope
>
> CUSTOMER_CRASH_COUNT: ?1
>
> DEFAULT_BUCKET_ID: ?VISTA_DRIVER_FAULT
>
> BUGCHECK_STR: ?0x7E
>
> CURRENT_IRQL: ?0
>
> LAST_CONTROL_TRANSFER: ?from 9b8919a4 to 00000000
>
> STACK_TEXT:
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> 8ad235f0 9b8919a4 00000000 84deb5d8 85002000 0x0
> 8ad23610 9b89a671 84deb5d8 85002000 8ad23660 RzFilter!WdfDriverCreate+0x24 [e:\winddk\7600.16385.1\inc\wdf\kmdf\1.9\wdfdriver.h @ 219]
> 8ad23698 82fb0740 84deb5d8 85002000 c000035f RzFilter!DriverEntry+0x161 [e:\work\heidi\rig\overlay\rzfilter\rzfilter.c @ 120]
> 8ad2387c 82fb7fff 00000000 00000001 8ad238a4 nt+0x1a3740
> 8ad23928 82ffce13 9e6ae180 00000001 9e6ae154 nt+0x1aafff
> 8ad23960 830050f8 00000007 8ad23a2c c0000034 nt+0x1efe13
> 8ad239cc 82fb527d 40000000 800009c0 8ad23a48 nt+0x1f80f8
> 8ad23aa8 82fb488e 866cb460 8ad23cd0 84e24e18 nt+0x1a827d
> 8ad23ca4 82fbd681 866cb460 84e24e18 8ad23cd0 nt+0x1a788e
> 8ad23cd8 82e20f56 82f70e80 84caf798 82f475bc nt+0x1b0681
> 8ad23d00 82e7af3b 00000000 00000000 84caf798 nt+0x13f56
> 8ad23d50 8301b6d3 00000001 a3fac2de 00000000 nt+0x6df3b
> 8ad23d90 82ecd0f9 82e7ae2e 00000001 00000000 nt+0x20e6d3
> 00000000 00000000 00000000 00000000 00000000 nt+0xc00f9
>
>
> FOLLOWUP_IP:
> RzFilter!WdfDriverCreate+24 [e:\winddk\7600.16385.1\inc\wdf\kmdf\1.9\wdfdriver.h @ 219]
> 9b8919a4 5d ? ? ? ? ? ? ?pop ? ? ebp
>
> SYMBOL_STACK_INDEX: ?1
>
> SYMBOL_NAME: ?RzFilter!WdfDriverCreate+24
>
> FOLLOWUP_NAME: ?MachineOwner
>
> MODULE_NAME: RzFilter
>
> IMAGE_NAME: ?RzFilter.sys
>
> STACK_COMMAND: ?.cxr 0xffffffff8ad23110 ; kb
>
> BUCKET_ID: ?WRONG_SYMBOLS
>
> Followup: MachineOwner
> ---------
>
> Thanks,
> Marshall
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>

–
Kris

4

Thanks for the suggestion.

It looks the VS2010 doesn’t natively support building the driver but I see one project setting in the Linker->System->Drivers. What is this setting for? Isn’t it for building the driver?

Thanks,
Marshall

5

Why do you care, if you don’t build the driver with BUILD (potentially
with VS and ddkbuild), you are going to get a disaster. A number of us
have had to debug the messes of people who tried to build a driver with
VS directly, the subtle bug that can occur can cost a fortune to find,
and the bottom line when it is done is change the environment to one
that works.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@hotmail.com” wrote in message
news:xxxxx@ntdev:

> Thanks for the suggestion.
>
> It looks the VS2010 doesn’t natively support building the driver but I see one project setting in the Linker->System->Drivers. What is this setting for? Isn’t it for building the driver?
>
> Thanks,
> Marshall

6

It is there because it is a linker flag and the UI is showing all flags, applicable or not. There is more to compiling a driver than setting the driver linker flag

d

debt from my phone

From: xxxxx@hotmail.com
Sent: 11/19/2011 6:57 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Build the WDF driver using VS2010

Thanks for the suggestion.

It looks the VS2010 doesn’t natively support building the driver but I see one project setting in the Linker->System->Drivers. What is this setting for? Isn’t it for building the driver?

Thanks,
Marshall

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

7

Doron said that there’re more setting to compile a driver using Visual Studio 2010. It seems that it’s possible to do so, doesn’t it?

Now I can build the driver successfully using VS 2010 but the driver causes BSOD when it calls the WdfCreateDriver in the DriverEntry so I guess there muse be something wrong with my project setting because I made bunch of changes to the settings. I have no idea how I can share the entir project file here for your reference so I desribe it here as much as I can:

General:
Target Extension -> .sys
Configuration Type -> Dynamic Library(.dll)

VC++ Directoies:
Include Directories -> $(DDKROOT)\inc\api;$(DDKROOT)\inc\ddk;$(DDKROOT)\inc\wdf\kmdf\1.9;$(DDKROOT)\inc\crt;$(IncludePath)
Library Directories -> $(DDKROOT)\lib\wxp\i386;$(DDKROOT)\lib\wdf\kmdf\i386\1.9;$(DDKROOT)\lib\Crt\i386;$(LibraryPath)

C/C++:

  • General
    Debug Information Format-> Program Database(/Zi)
  • Preprocessor
    Preprocessor Definitions->
    X86=1;i386=1;STD_CALL;DLL=1;CONDITION_HANDLING=1;NT_INST=0;WIN32=100;NT1X=100;WINNT=1;WINVER=_WIN32_WINNT_WINXP;_WIN32_IE=0x0603;WIN32_LEAN_AND_MEAN=1;DEVL=1;BUILDMACHINE=WinDDK;FPO=0;NTDDI_VERSION=NTDDI_WINXP;DBG=1;_WIN32_WINNT=_WIN32_WINNT_WINXP
  • Code Generation
    Enable String Pooling -> Yes(/GF)
    Enable Minimal Rebuild -> No(/Gm-)
    Basic Runtime Checks -> Default
    Runtime Library -> Multi-threaded(/MT)
    Struct Member Alignment -> 8Bytes(/Zp8)
    Enable Function-Level Linking -> Yes(/Gy)
  • Language
    Enable Run-Time Type Information -> No(/GR-)
  • Advanced
    Calling Convention -> __stdcall(/Gz)
    Omit Default Library Name -> Yes(/ZI)

Linker:

  • General
    Version -> 6.0
    Ignore Import Library -> Yes
  • Input
    Additional Dependencies -> BufferOverflowK.lib;ntoskrnl.lib;hal.lib;wmilib.lib;sehupd.lib;nt.lib;wdmsec.lib;wdfdriverentry.lib;wdfldr.lib;%(AdditionalDependencies)
    Ignore All Default Libraries -> Yes(/NODEFAULTLIB)
  • Manifest File
    Generate Manifest -> No(/MANIFEST:NO)
    Enable User Account Control(UAC) -> No(/MANIFESTUAC:NO)
  • System
    SubSystem -> Not Set
    Stack Reserved Size -> 262144
    Stack Commit Size -> 4096
    Driver -> Driver(/Driver)
  • Embedded IDL
    Ignore Embedded IDL -> Yes(/IGNOREIDL)
  • Advanced
    Entry Point -> GsDriverEntry%408
    Set Checksum -> Yes(/RELEASE)
    Base Address -> 0x10000
    Fixed Base Address -> No(/FIXED:NO)
    Unload delay loaded DLL -> No
  • Command Line
    Additional Options -> /functionpadmin:5 /safeseh /subsystem:native,5.01 /align:0x80 /stub:$(DDKROOT)\lib\wxp\stub512.com /osversion:6.0 /SECTION:INIT,d /IGNORE:4198,4010,4037,4039,4065,4070,4078,4087,4089,4221,4324

If it’s impossible to do so, how can I integrate the WDK build into the Visual Studio? There’re 10+ projects in the solution and we can build the solution simply using the VS’s build env.

Thanks,
Marhsall

Doron Holan
xxxxx@microsoft.com Join Date: 08 Sep 2005
Posts To This List: 6431

RE: Build the WDF driver using VS2010

It is there because it is a linker flag and the UI is showing all flags,
applicable or not. There is more to compiling a driver than setting the driver
linker flag

d

debt from my phone

8

On 21-Nov-2011 05:12, xxxxx@hotmail.com wrote:

Doron said that there’re more setting to compile a driver using Visual Studio 2010.
> It seems that it’s possible to do so, doesn’t it?

Yes, possible. Like someone from the same company wrote, everything is
possible.
But it is unsupported. Which means - no support. Because your BSOD is
self-inflicted, please help yourself.

Regards,
– pa

9

Isnt’ using Visual DDK an option as well? It has some templates that
seem to build a Kernel Mode driver(BazisLib RAMDISK driver template). It
also seems to have a nice way to debug on a virtual machine straight
from Visual Studio.
We are trying to get all this to work right now, and we are struggling
with the same question – how to properly build the driver in Visual
Studio 2010.
When creating a new Driver project, one gets to pick the toolchain –
BUILD and WDK vs. Visual Studio project system. We picked BUILD and WDK,
and it seems to build and attempt to transfer the .sys to the Virtual
Machine target. We will have to add signing manually though, as the
build does not do that automatically.
Is anyone using Visual DDK, how is it wokring out for you?
Thanks
Rachel

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Saturday, November 19, 2011 9:10 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Build the WDF driver using VS2010

Why do you care, if you don’t build the driver with BUILD (potentially
with VS and ddkbuild), you are going to get a disaster. A number of us
have had to debug the messes of people who tried to build a driver with
VS directly, the subtle bug that can occur can cost a fortune to find,
and the bottom line when it is done is change the environment to one
that works.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@hotmail.com” wrote in message
news:xxxxx@ntdev:

> Thanks for the suggestion.
>
> It looks the VS2010 doesn’t natively support building the driver but I
see one project setting in the Linker->System->Drivers. What is this
setting for? Isn’t it for building the driver?
>
> Thanks,
> Marshall

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

10

There are two ways to use VisualDDK one generates a DDKBUILD script and
works great. The other generates a build with VS and your mileage may
vary. At least some of my customers found differing behavior in their
drivers when building with both methods. At this point I view the build
directly with VS as still being a problem, it may work 98% of the time,
but you can lose the other times.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“Michelson Rachel-CRK007” wrote
in message news:xxxxx@ntdev:

> Isnt’ using Visual DDK an option as well? It has some templates that
> seem to build a Kernel Mode driver(BazisLib RAMDISK driver template). It
> also seems to have a nice way to debug on a virtual machine straight
> from Visual Studio.
> We are trying to get all this to work right now, and we are struggling
> with the same question – how to properly build the driver in Visual
> Studio 2010.
> When creating a new Driver project, one gets to pick the toolchain –
> BUILD and WDK vs. Visual Studio project system. We picked BUILD and WDK,
> and it seems to build and attempt to transfer the .sys to the Virtual
> Machine target. We will have to add signing manually though, as the
> build does not do that automatically.
> Is anyone using Visual DDK, how is it wokring out for you?
> Thanks
> Rachel
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> Sent: Saturday, November 19, 2011 9:10 AM
> To: Windows System Software Devs Interest List
> Subject: RE:[ntdev] Build the WDF driver using VS2010
>
> Why do you care, if you don’t build the driver with BUILD (potentially
> with VS and ddkbuild), you are going to get a disaster. A number of us
> have had to debug the messes of people who tried to build a driver with
> VS directly, the subtle bug that can occur can cost a fortune to find,
> and the bottom line when it is done is change the environment to one
> that works.
>
>
> Don Burn
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
>
>
>
> “xxxxx@hotmail.com” wrote in message
> news:xxxxx@ntdev:
>
> > Thanks for the suggestion.
> >
> > It looks the VS2010 doesn’t natively support building the driver but I
> see one project setting in the Linker->System->Drivers. What is this
> setting for? Isn’t it for building the driver?
> >
> > Thanks,
> > Marshall
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

11

Why not use and invest in the supported workflow with the win8 wdk?

d

debt from my phone

From: Michelson Rachel-CRK007
Sent: 11/21/2011 7:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Isnt’ using Visual DDK an option as well? It has some templates that
seem to build a Kernel Mode driver(BazisLib RAMDISK driver template). It
also seems to have a nice way to debug on a virtual machine straight
from Visual Studio.
We are trying to get all this to work right now, and we are struggling
with the same question – how to properly build the driver in Visual
Studio 2010.
When creating a new Driver project, one gets to pick the toolchain –
BUILD and WDK vs. Visual Studio project system. We picked BUILD and WDK,
and it seems to build and attempt to transfer the .sys to the Virtual
Machine target. We will have to add signing manually though, as the
build does not do that automatically.
Is anyone using Visual DDK, how is it wokring out for you?
Thanks
Rachel

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Saturday, November 19, 2011 9:10 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Build the WDF driver using VS2010

Why do you care, if you don’t build the driver with BUILD (potentially
with VS and ddkbuild), you are going to get a disaster. A number of us
have had to debug the messes of people who tried to build a driver with
VS directly, the subtle bug that can occur can cost a fortune to find,
and the bottom line when it is done is change the environment to one
that works.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@hotmail.com” wrote in message
news:xxxxx@ntdev:

> Thanks for the suggestion.
>
> It looks the VS2010 doesn’t natively support building the driver but I
see one project setting in the Linker->System->Drivers. What is this
setting for? Isn’t it for building the driver?
>
> Thanks,
> Marshall

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

12

Legacy equipment reasons beyond my control. My device has to work in a
Win7 environment.

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, November 21, 2011 10:27 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Why not use and invest in the supported workflow with the win8 wdk?

d

debt from my phone

From: Michelson Rachel-CRK007
Sent: 11/21/2011 7:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Isnt’ using Visual DDK an option as well? It has some templates that
seem to build a Kernel Mode driver(BazisLib RAMDISK driver template). It
also seems to have a nice way to debug on a virtual machine straight
from Visual Studio.
We are trying to get all this to work right now, and we are struggling
with the same question – how to properly build the driver in Visual
Studio 2010.
When creating a new Driver project, one gets to pick the toolchain –
BUILD and WDK vs. Visual Studio project system. We picked BUILD and WDK,
and it seems to build and attempt to transfer the .sys to the Virtual
Machine target. We will have to add signing manually though, as the
build does not do that automatically.
Is anyone using Visual DDK, how is it wokring out for you?
Thanks
Rachel

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Saturday, November 19, 2011 9:10 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Build the WDF driver using VS2010

Why do you care, if you don’t build the driver with BUILD (potentially
with VS and ddkbuild), you are going to get a disaster. A number of us
have had to debug the messes of people who tried to build a driver with
VS directly, the subtle bug that can occur can cost a fortune to find,
and the bottom line when it is done is change the environment to one
that works.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@hotmail.com” wrote in message
news:xxxxx@ntdev:

> Thanks for the suggestion.
>
> It looks the VS2010 doesn’t natively support building the driver but I
see one project setting in the Linker->System->Drivers. What is this
setting for? Isn’t it for building the driver?
>
> Thanks,
> Marshall

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

13

And the win8 wdk supports targeting w7

d

debt from my phone

From: Michelson Rachel-CRK007
Sent: 11/21/2011 8:39 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Legacy equipment reasons beyond my control. My device has to work in a Win7 environment.

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, November 21, 2011 10:27 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Why not use and invest in the supported workflow with the win8 wdk?

d

debt from my phone

From: Michelson Rachel-CRK007
Sent: 11/21/2011 7:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010
Isnt’ using Visual DDK an option as well? It has some templates that
seem to build a Kernel Mode driver(BazisLib RAMDISK driver template). It
also seems to have a nice way to debug on a virtual machine straight
from Visual Studio.
We are trying to get all this to work right now, and we are struggling
with the same question – how to properly build the driver in Visual
Studio 2010.
When creating a new Driver project, one gets to pick the toolchain –
BUILD and WDK vs. Visual Studio project system. We picked BUILD and WDK,
and it seems to build and attempt to transfer the .sys to the Virtual
Machine target. We will have to add signing manually though, as the
build does not do that automatically.
Is anyone using Visual DDK, how is it wokring out for you?
Thanks
Rachel

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Saturday, November 19, 2011 9:10 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Build the WDF driver using VS2010

Why do you care, if you don’t build the driver with BUILD (potentially
with VS and ddkbuild), you are going to get a disaster. A number of us
have had to debug the messes of people who tried to build a driver with
VS directly, the subtle bug that can occur can cost a fortune to find,
and the bottom line when it is done is change the environment to one
that works.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@hotmail.com” wrote in message
news:xxxxx@ntdev:

> Thanks for the suggestion.
>
> It looks the VS2010 doesn’t natively support building the driver but I
see one project setting in the Linker->System->Drivers. What is this
setting for? Isn’t it for building the driver?
>
> Thanks,
> Marshall

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

14

What do I need then, will it work with Studio 2010?

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, November 21, 2011 10:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

And the win8 wdk supports targeting w7

d

debt from my phone

From: Michelson Rachel-CRK007
Sent: 11/21/2011 8:39 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Legacy equipment reasons beyond my control. My device has to work in a
Win7 environment.

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, November 21, 2011 10:27 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Why not use and invest in the supported workflow with the win8 wdk?

d

debt from my phone

From: Michelson Rachel-CRK007
Sent: 11/21/2011 7:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Isnt’ using Visual DDK an option as well? It has some templates that
seem to build a Kernel Mode driver(BazisLib RAMDISK driver template). It
also seems to have a nice way to debug on a virtual machine straight
from Visual Studio.
We are trying to get all this to work right now, and we are struggling
with the same question – how to properly build the driver in Visual
Studio 2010.
When creating a new Driver project, one gets to pick the toolchain –
BUILD and WDK vs. Visual Studio project system. We picked BUILD and WDK,
and it seems to build and attempt to transfer the .sys to the Virtual
Machine target. We will have to add signing manually though, as the
build does not do that automatically.
Is anyone using Visual DDK, how is it wokring out for you?
Thanks
Rachel

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Saturday, November 19, 2011 9:10 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Build the WDF driver using VS2010

Why do you care, if you don’t build the driver with BUILD (potentially
with VS and ddkbuild), you are going to get a disaster. A number of us
have had to debug the messes of people who tried to build a driver with
VS directly, the subtle bug that can occur can cost a fortune to find,
and the bottom line when it is done is change the environment to one
that works.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@hotmail.com” wrote in message
news:xxxxx@ntdev:

> Thanks for the suggestion.
>
> It looks the VS2010 doesn’t natively support building the driver but I
see one project setting in the Linker->System->Drivers. What is this
setting for? Isn’t it for building the driver?
>
> Thanks,
> Marshall

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

15

You need VS11 and the win8 wdk

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Michelson Rachel-CRK007
Sent: Monday, November 21, 2011 9:27 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

What do I need then, will it work with Studio 2010?

From: xxxxx@lists.osr.commailto:xxxxx [mailto:xxxxx@lists.osr.com]mailto: On Behalf Of Doron Holan
Sent: Monday, November 21, 2011 10:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

And the win8 wdk supports targeting w7

d

debt from my phone

From: Michelson Rachel-CRK007
Sent: 11/21/2011 8:39 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010
Legacy equipment reasons beyond my control. My device has to work in a Win7 environment.

From: xxxxx@lists.osr.commailto:xxxxx [mailto:xxxxx@lists.osr.com]mailto: On Behalf Of Doron Holan
Sent: Monday, November 21, 2011 10:27 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Why not use and invest in the supported workflow with the win8 wdk?

d

debt from my phone

From: Michelson Rachel-CRK007
Sent: 11/21/2011 7:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010
Isnt’ using Visual DDK an option as well? It has some templates that
seem to build a Kernel Mode driver(BazisLib RAMDISK driver template). It
also seems to have a nice way to debug on a virtual machine straight
from Visual Studio.
We are trying to get all this to work right now, and we are struggling
with the same question – how to properly build the driver in Visual
Studio 2010.
When creating a new Driver project, one gets to pick the toolchain –
BUILD and WDK vs. Visual Studio project system. We picked BUILD and WDK,
and it seems to build and attempt to transfer the .sys to the Virtual
Machine target. We will have to add signing manually though, as the
build does not do that automatically.
Is anyone using Visual DDK, how is it wokring out for you?
Thanks
Rachel

-----Original Message-----
From: xxxxx@lists.osr.commailto:xxxxx
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Saturday, November 19, 2011 9:10 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Build the WDF driver using VS2010

Why do you care, if you don’t build the driver with BUILD (potentially
with VS and ddkbuild), you are going to get a disaster. A number of us
have had to debug the messes of people who tried to build a driver with
VS directly, the subtle bug that can occur can cost a fortune to find,
and the bottom line when it is done is change the environment to one
that works.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@hotmail.commailto:xxxxx” > wrote in message
news:xxxxx@ntdev:

> Thanks for the suggestion.
>
> It looks the VS2010 doesn’t natively support building the driver but I
see one project setting in the Linker->System->Drivers. What is this
setting for? Isn’t it for building the driver?
>
> Thanks,
> Marshall

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx></mailto:></mailto:xxxxx></mailto:></mailto:xxxxx>

16

No, not with the VS 2010 compiler. You can use VS from 2005 to 2010 to build a driver by using a MakeFile project and then invoking DDKBUILD. But then I believe you’ve been told that a couple of times.

Gary Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

On Nov 21, 2011, at 11:27 AM, Michelson Rachel-CRK007 wrote:

What do I need then, will it work with Studio 2010?

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, November 21, 2011 10:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

And the win8 wdk supports targeting w7

d

debt from my phone
From: Michelson Rachel-CRK007
Sent: 11/21/2011 8:39 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Legacy equipment reasons beyond my control. My device has to work in a Win7 environment.

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, November 21, 2011 10:27 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Why not use and invest in the supported workflow with the win8 wdk?

d

debt from my phone
From: Michelson Rachel-CRK007
Sent: 11/21/2011 7:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Isnt’ using Visual DDK an option as well? It has some templates that
seem to build a Kernel Mode driver(BazisLib RAMDISK driver template). It
also seems to have a nice way to debug on a virtual machine straight
from Visual Studio.
We are trying to get all this to work right now, and we are struggling
with the same question – how to properly build the driver in Visual
Studio 2010.
When creating a new Driver project, one gets to pick the toolchain –
BUILD and WDK vs. Visual Studio project system. We picked BUILD and WDK,
and it seems to build and attempt to transfer the .sys to the Virtual
Machine target. We will have to add signing manually though, as the
build does not do that automatically.
Is anyone using Visual DDK, how is it wokring out for you?
Thanks
Rachel

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Saturday, November 19, 2011 9:10 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Build the WDF driver using VS2010

Why do you care, if you don’t build the driver with BUILD (potentially
with VS and ddkbuild), you are going to get a disaster. A number of us
have had to debug the messes of people who tried to build a driver with
VS directly, the subtle bug that can occur can cost a fortune to find,
and the bottom line when it is done is change the environment to one
that works.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@hotmail.com” wrote in message
> news:xxxxx@ntdev:
>
> > Thanks for the suggestion.
> >
> > It looks the VS2010 doesn’t natively support building the driver but I
> see one project setting in the Linker->System->Drivers. What is this
> setting for? Isn’t it for building the driver?
> >
> > Thanks,
> > Marshall
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

17

>Isnt’ using Visual DDK an option as well?

No, unless you want to fix a huge numbers of this software’s bugs.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

18

I assume it’s against the license to currently SHIP drivers built with the
Win8 wdk? For many of us that implies the win8 wdk is not viable until next
summer/fall, when it releases.

Jan

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, November 21, 2011 8:27 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Why not use and invest in the supported workflow with the win8 wdk?

d

19

Correct, you cannot yet ship a binary built with the w8 kit

d

debt from my phone

From: Jan Bottorff
Sent: 11/23/2011 12:58 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

I assume it?s against the license to currently SHIP drivers built with the Win8 wdk? For many of us that implies the win8 wdk is not viable until next summer/fall, when it releases.

Jan

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, November 21, 2011 8:27 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build the WDF driver using VS2010

Why not use and invest in the supported workflow with the win8 wdk?

d

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer