Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

Monthly Seminars at OSR Headquarters

East Coast USA
Windows Internals and SW Drivers, Dulles (Sterling) VA, 13 November 2017

Kernel Debugging & Crash Analysis for Windows, Nashua (Amherst) NH, 4 December 2017

Writing WDF Drivers I: Core Concepts, Nashua (Amherst) NH, 8 January 2018

WDF Drivers II: Advanced Implementation Techniques, Nashua (Amherst) NH, 15 January 2018


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 11  
13 Jan 18 03:19
makrurisan makkeln
xxxxxx@x-publisher.com
Join Date: 12 Jan 2018
Posts To This List: 8
Development Environment to build WDF driver

Hi All, I want to develop a wdf driver and want to know what the best environment is to do it. At the moment I installed Windows 10 in Virtual Box (VirtualKD-3.0) and use WinDbg. Sometimes I have problem loading the symbols and I think it can be easier. I have VS 2017 and I have seen that it is also possible to debug directly from VS with WinDbg. Thanks for your help.
  Message 2 of 11  
14 Jan 18 10:54
Mark Roddy
xxxxxx@gmail.com
Join Date: 25 Feb 2000
Posts To This List: 4048
Development Environment to build WDF driver

VS2015 for building drivers. Windbg for debugging. You don't really need VirtualKD. A W10 target can use network debug ports on virtual box. Symbol problems are almost always because you have not set your symbols up correctly. Mark Roddy On Sat, Jan 13, 2018 at 3:18 AM, xxxxx@x-publisher.com < xxxxx@lists.osr.com> wrote: > Hi All, > > I want to develop a wdf driver and want to know what the best environment > is to do it. > At the moment I installed Windows 10 in Virtual Box (VirtualKD-3.0) and > use WinDbg. Sometimes I have problem loading the symbols and I think it can > be easier. > I have VS 2017 and I have seen that it is also possible to debug directly > from VS with WinDbg. > <...excess quoted lines suppressed...> --
  Message 3 of 11  
14 Jan 18 13:27
makrurisan makkeln
xxxxxx@x-publisher.com
Join Date: 12 Jan 2018
Posts To This List: 8
Development Environment to build WDF driver

Can you tell me how you do set the symbols, image and source path? Do you use this _NT* environment variables and when how? Why using VS 2015? VS2017 is stable and have some great features for developing drivers. I like it to use one environment for coding ,debugging and testing. Manfred From: <xxxxx@lists.osr.com> on behalf of "xxxxx@gmail.com" <xxxxx@lists.osr.com> Reply-To: Windows System Software Devs Interest List <xxxxx@lists.osr.com> Date: Sunday 14 January 2018 at 16:53 To: Windows System Software Devs Interest List <xxxxx@lists.osr.com> Subject: Re: [ntdev] Development Environment to build WDF driver VS2015 for building drivers. Windbg for debugging. You don't really need VirtualKD. A W10 target can use network debug ports on virtual box. Symbol problems are almost always because you have not set your symbols up correctly. Mark Roddy On Sat, Jan 13, 2018 at 3:18 AM, xxxxx@x-publisher.com <xxxxx@lists.osr.com> wrote: > Hi All, > > I want to develop a wdf driver and want to know what the best environment is > to do it. > At the moment I installed Windows 10 in Virtual Box (VirtualKD-3.0) and use > WinDbg. Sometimes I have problem loading the symbols and I think it can be > easier. > I have VS 2017 and I have seen that it is also possible to debug directly from > VS with WinDbg. > <...excess quoted lines suppressed...> --- NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers! Details at To unsubscribe, visit the List Server section of OSR Online at --
  Message 4 of 11  
14 Jan 18 18:56
Daniel Kulas
xxxxxx@gmail.com
Join Date: 08 Nov 2017
Posts To This List: 1
Development Environment to build WDF driver

Follow the instructions here for setting up your symbols: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/symbol-path On Sun, Jan 14, 2018 at 10:26 AM, xxxxx@x-publisher.com < xxxxx@lists.osr.com> wrote: > Can you tell me how you do set the symbols, image and source path? Do you > use this _NT* environment variables and when how? > > Why using VS 2015? > VS2017 is stable and have some great features for developing drivers. I > like it to use one environment for coding ,debugging and testing. > > Manfred > > From: <xxxxx@lists.osr.com> on behalf of " <...excess quoted lines suppressed...> --
  Message 5 of 11  
14 Jan 18 23:55
Tim Roberts
xxxxxx@probo.com
Join Date: 28 Jan 2005
Posts To This List: 11741
Development Environment to build WDF driver

On Jan 14, 2018, at 10:26 AM, xxxxx@x-publisher.com <xxxxx@lists.osr.com> wrote: > > Why using VS 2015? > VS2017 is stable and have some great features for developing drivers. Like what? It has been my experience that driver developers rarely want to be on the bleeding edge of their tools. We want something that's well-established. VS2017 is still pretty new. I don't actually use the IDE. I edit in "gvim", and then run "msbuild" from the command line. I've heard there may be glitzy new features in the IDE, but the sad fact is that I can bring up a file in gvim, make a change, build it, copy it to my test machine, test it, and bring up the editor again before the IDE has even displayed its first window. I just don't have the patience. ??? Tim Roberts, xxxxx@probo.com Providenza & Boekelheide, Inc. --
  Message 6 of 11  
15 Jan 18 14:45
Mark Roddy
xxxxxx@gmail.com
Join Date: 25 Feb 2000
Posts To This List: 4048
Development Environment to build WDF driver

Because up until 1709 VS2017 was not supported for dri ver builds. So I'll amend my comment, if you are using the 1709 WDK then use VS2017, otherwise use VS2015. To amplify what Tim said: I use msbuild and a (power)shell script to run builds. I'm currently using VSCODE to edit source code. We change build tools infrequently, so when a new WDK version comes out that requires a build tools change, we are unlikely to use either the new WDK or the new build tools until there is a compelling reason to do so. Mark Roddy On Sun, Jan 14, 2018 at 11:54 PM, xxxxx@probo.com <xxxxx@lists.osr.com> wrote: > On Jan 14, 2018, at 10:26 AM, xxxxx@x-publisher.com < > xxxxx@lists.osr.com> wrote: > > > Why using VS 2015? > VS2017 is stable and have some great features for developing drivers. > > > Like what? It has been my experience that driver developers rarely want > to be on the bleeding edge of their tools. We want something that's <...excess quoted lines suppressed...> --
  Message 7 of 11  
16 Jan 18 09:32
makrurisan makkeln
xxxxxx@x-publisher.com
Join Date: 12 Jan 2018
Posts To This List: 8
Development Environment to build WDF driver

@Mark You said: >> I use msbuild and a (power)shell script to run builds. I'm currently using VSCODE to edit source code. I use VSCODE too in other project. What do you do with powershell. Do you make remote calls to the system with Get-WmiObject?
  Message 8 of 11  
16 Jan 18 18:08
Mark Roddy
xxxxxx@gmail.com
Join Date: 25 Feb 2000
Posts To This List: 4048
Development Environment to build WDF driver

No I just use a powershell script to run msbuild - set up the environment, provide the correct parameters etc. Mark Roddy On Tue, Jan 16, 2018 at 9:31 AM, xxxxx@x-publisher.com < xxxxx@lists.osr.com> wrote: > @Mark > > You said: > >> I use msbuild and a (power)shell script to run builds. I'm currently > using VSCODE to edit source code. > > I use VSCODE too in other project. > What do you do with powershell. Do you make remote calls to the system > with Get-WmiObject? > <...excess quoted lines suppressed...> --
  Message 9 of 11  
18 Jan 18 15:09
Tim Roberts
xxxxxx@probo.com
Join Date: 28 Jan 2005
Posts To This List: 11741
Development Environment to build WDF driver

xxxxx@gmail.com wrote: > > To amplify what Tim said: I use msbuild and a (power)shell script to > run builds. I'm currently using VSCODE to edit source code. I have to say, your endorsement made me take a look at VSCode.  That's a pretty slick tool.  It might actually coax me away from vim. -- Tim Roberts, xxxxx@probo.com Providenza & Boekelheide, Inc.
  Message 10 of 11  
18 Jan 18 15:20
Mark Roddy
xxxxxx@gmail.com
Join Date: 25 Feb 2000
Posts To This List: 4048
Development Environment to build WDF driver

Full integration is a WIP for me right now. I want full error reporting integration and that is not working for me yet. (Click on the error go to the code.) But it's close. Obviously MSFT would rather you use the bulky VS. Mark Roddy On Thu, Jan 18, 2018 at 3:08 PM, xxxxx@probo.com <xxxxx@lists.osr.com> wrote: > xxxxx@gmail.com wrote: > > > > To amplify what Tim said: I use msbuild and a (power)shell script to > > run builds. I'm currently using VSCODE to edit source code. > > I have to say, your endorsement made me take a look at VSCode. That's a > pretty slick tool. It might actually coax me away from vim. > > -- > Tim Roberts, xxxxx@probo.com <...excess quoted lines suppressed...> --
  Message 11 of 11  
18 Jan 18 16:20
Peter Viscarola (OSR)
xxxxxx@osr.com
Join Date:
Posts To This List: 5960
List Moderator
Development Environment to build WDF driver

ONE (significant, to me) advantage of the 1709 WDK over the earlier (VS2015 compliant) WDK is that SDV is significantly better. It uses a new engine, IIRC. CA finds more errors, as well. VS 2015 was a "work in progress" for a long time. The first release of the re-written compiler. I was happy to put it in my rear view mirror. Peter OSR @OSRDrivers
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 04:25.


Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license