- Yes. Support for W2K has been removed from later WDKs. Full regression
testing with later WDKs requires too much time to take such a risk. - Yes. Same sources as I find very few occasions where a change is
required. - We use our own build batch files that invoke the appropriate setenv.
“Don Burn” wrote in message news:xxxxx@ntdev…
> 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?
> 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?
> 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?
>
> –
> Don Burn (MVP, Windows DDK)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4148 (20090611)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>