Well, you can kind of see why we’ve been quiet around here…


 

If you’re watching what’s going on at //BUILD (and why wouldn’t you be?), you may have seen that UMDF now supports hardware access (via ports and registers) and interrupt handling!  If you haven’t seen it, you can go read more here.

And the other big one.  Something I’ve been begging to get done for years and believe me in all my years at Microsoft it’s been one of, if not the most, commonly requested thing I’ve heard at all the WinHECs, Developer Conferences, Trade Association meetings, etc from you guys. – Visual Studio integration of the WDK.  Even down to templates for UMDF and KMDF drivers!  You know what that means, native Intellisense (not that we haven’t figured out how to do that already), but more importantly, the one thing I couldn’t give you (partly because I couldn’t get the plug in to work across all VS editions) integrated WDK build support. 😀

There are still a couple of other very cool things in the UMDF / KMDF space we’ll get to start talking about pretty soon, and for sure I’ll start digging more in to these two as we move closer to the Windows 8 / WDF 1.11 release timeline.

So the blog will be spooling back up with some fun posts in the coming months.

Let me know if you have any questions or comments!

 

-p

Comments (3)

  1. Actually there have been a ton of the senior developers who said please don't go to VS! says:

    Actually, most of the professional driver developers were saying don't do this, and if you are going to support Visual Studio make sure one can revert to BUILD.  VS has terrible configuration management for projects and I have ironically spent a lot of consulting time converting firms from VS to BUILD for all development since they find that quality soars when the get out of Visual Studio.

    The current VS integration of the WDK is a disaster since it neither supports XP driver development, or moving out of VS and back to a BUILD environment.  Most clients I have require XP, so basically Microsoft is saying do a ton of parallel maintenance to use the latest tools.  I suspect most of my clients will say ignore Windows 8 and it tools since we can't afford the cost of maintaining the parallel environments.  This is a great way to reduce the quality of WIndows drivers.

  2. pat.man says:

    I totally understand the parallel environment situation, maybe we can do something to figure out a solution there.

    While there's never been a fully "supported" VS Integration of the WDK, there have always been a number of work arounds to get some of the cool features of VS working – such as my Intellisense work and the various tools out there that have allowed people access build environment from within the IDE.

    I know there people who focus solely on driver development that have never really had a need for VS integration.  But this was really a big ask for those who did both application and driver developement for their companies – end to end package owners – and those who were starting to write drivers.  And especially those wanting to use the frameworks.

    I actually have always used Visual Studio since I started working at MSFT.  I used to use gvim / vi way back when, but moved over when I started here – being good company boy and all.  That's how I figured out how to do the Intellisense, declaration / definition / parameter highlighting for driver projects.  But like a lot of people externally, I always kept my build environment via CMD line.  I'm also only one of two people on my team who still uses KD.exe for debugging as well.  I still refuse to give up some of my old habits. 🙂

    I personally have not played with VS11 yet (I know, as such a heavy VS user you'd think I'd be all over it by now g).  I've got a couple of my own plug-ins for VS10 that I haven't fixed to work with VS11 yet.  But in looking at the Visual Studio project templates that have been provided for the UMDF and KMDF side, it should be a big stepping stone to get people who are aready to migrate over to the frameworks up and running easier.

  3. Kristopher Micinski says:

    Glad to hear that this came to fruition, it was a fun project to work on last summer :-).