Don Burn wrote:
Recently in a discussion with the WDK team, the problem of working in
multiple versions of the WDK was brought up. Microsoft does not see this
problem internally since it uses the latest WDK for almost everything. So
I would like to ask a simple survey to folks on NTDEV:1… In normal work do you have more than one version of the WDK in use?
If so why?
Yes, I currently have 6 versions installed, both at work and at home.
* 2600 (XP)
* 3790 (Server 2003)
* 3790.1830 (Server 2003 SP1)
* 6000 (Vista)
* 6001.18002 (Vista SP1)
* 7100 (Win 7 RC1)
I do builds using each of the last three (occasionally). The first
three are just for reference.
Like Don, I have clients with regulatory concerns who release drivers
only after lengthy validation. If one of them encounters a problem in a
driver built with the 6000 WDK, I need to deliver a fix based on the
6000 WDK. Switching to a new WDK means revalidating.
I also keep the old one around for reference, and for answering
questions on mailing lists and newsgroups. Also, the good samples
sometimes come and go. The best and most complete BDA sample driver
(the Europa sample) exists in exactly one of those DDKs – 3790.1830.
2… When the WDK beta comes out, do you try it with current projects? If
so do you try to use the same copy of the sources for both, or clone one
specifically for the beta?
I generally try the beta with my current projects. I keep the same copy
of the sources for both. My clients have not yet insisted on being
completely Prefast-clean, so Don’s specific issue has not arisen for me.
3… Have you encountered problems with using more than one WDK? Would you
like to have a way to conditionalize the build files or the driver source
for differing WDK versions?
Although I understand Don’s issue, and think a solution would be
appropriate, this has not been an issue for me. The only time this has
been an issue for me was with the original KMDF release, before it was
integrated in the WDK. KMDF required changes to the sources file that
were not appropriate after it was integrated into the WDK.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.