I’ve bit the bullet and plunged into converting a moderate number of apps
and drivers from a WDK7 build system to (unfortunately) a combined WDK7 and
VS2013 build environment. I’d rather it was just VS2013 but MSFT keeps
dropping support for platforms so that isn’t an option.
Along the way I read (skimmed) the msbuild trickery book and plunged
straight into that book’s suggested model of common imports and skeletal
vcxproj files. All very nice from a sccs/build engineering perspective as I
have all of the standard settings we need in a small collection of
controlled files. The nightmare of configuration skew in large VS solutions
seems manageable.
Having walked down that path, with more or less ok results (although some
msbuild mysteries remain) I stumbled across the msft VS recommendations,
which basically say “don’t do that, use property sheets and the gui”. So
now I’m worried that if I continue on this path I will end up in some
nightmare with, for example VS2014, (and will the next release drop Win7?)
where they’ve changed everything and I have to start over again.
So what (if anything) are other people doing?
The other puzzle is “legacy mode driver model”. So one starts with an empty
wdm project model, but then I don’t need an inf but I do need a signed exe,
so I don’t quite understand how to do that. Anyone else been there?
Mark Roddy
A package project will build a signed sys.
On Dec 16, 2013 12:01 PM, “Mark Roddy” wrote:
> I’ve bit the bullet and plunged into converting a moderate number of apps
> and drivers from a WDK7 build system to (unfortunately) a combined WDK7 and
> VS2013 build environment. I’d rather it was just VS2013 but MSFT keeps
> dropping support for platforms so that isn’t an option.
>
> Along the way I read (skimmed) the msbuild trickery book and plunged
> straight into that book’s suggested model of common imports and skeletal
> vcxproj files. All very nice from a sccs/build engineering perspective as I
> have all of the standard settings we need in a small collection of
> controlled files. The nightmare of configuration skew in large VS solutions
> seems manageable.
>
> Having walked down that path, with more or less ok results (although some
> msbuild mysteries remain) I stumbled across the msft VS recommendations,
> which basically say “don’t do that, use property sheets and the gui”. So
> now I’m worried that if I continue on this path I will end up in some
> nightmare with, for example VS2014, (and will the next release drop Win7?)
> where they’ve changed everything and I have to start over again.
>
> So what (if anything) are other people doing?
>
> The other puzzle is “legacy mode driver model”. So one starts with an
> empty wdm project model, but then I don’t need an inf but I do need a
> signed exe, so I don’t quite understand how to do that. Anyone else been
> there?
>
> Mark Roddy
> — NTDEV is sponsored by OSR Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!! See
> http://www.osr.com/careers For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer