“Walter Oney” wrote in message news:xxxxx@ntdev…
>
> That’s not actually what he’s recommending. As best I can tell,
> DriverStudio uses the DDK compiler and linker. I know I do, and I do all
>
Sorry, the problem is SRCTODSP (or whatever it is)… This encourages people
to build in VS, and NOT use the correct compiler. This is not a good idea.
>
> Many developers, including me, have a strong preference for using an IDE
> with all of its ancillary tools.
>
No worries! Just do so such that you’re using the correct compiler and
linker. AND the correct build settings.
>
> I would estimate that we’re currently
> partway through a transition period that will see all of using some
> flavor of Visual Studio, and perhaps some C++ class library, for driver
> development a few years down the road.
>
Wow! You must have some special powers…
As to “all of us using… some C++ class library for driver development”,
this will be true only if the “all of us” doesn’t include yours truly.
> It’s a bit painful for the
> pioneers, but we’re coping.
>
“Pioneers?” Engineers at OSR have been doing this for more than 5 years.
Nobody I know who uses Visual Studio (OK, it’s only 3 people, but STILL)
finds it even remotely “painful”. Just use an external build procedure, and
RUN BUILD from within VS. It’s easy. It’s painless. You get all the
benefit, and you build drivers correctly.
The only “cost” is having to keep your “sources” file in sync with your
project. Given that this entails nothing more than adding or changing a
single line, I think most devs could handle it.
Peter
OSR