New OSR List for VS2013 Driver Development?

NTDEV
21

On 12/17/2013 4:41 PM, John Matsumoto wrote:

Not to sound like a dinosaur, but I’m still using command lines to build
both my drivers and to sign them. I’m now moving onto VS2013 as my build
environment. Would there perhaps be a webinar or YouTube on the start to
finish of building a device driver with VS2013 (build -> debug -> Verisign
-> test/QA -> WHQL)? Just the build to release process done entirely with
VS2013. I know parts of VS2013 process but would like to know how to do it
from start to finish.

Do you *want* to do it all within Visual Studio though? What we do is
make it simple for developers to build the driver in VS for
development/debugging, but all the staging/signing/packaging is done via
MSBuild scripts outside the IDE, building the C/C++/WiX/etc. code via
the ‘MSBuild’ task which doesn’t need to run devenv.

–
Bruce

22

I don’t know how much has been changed from VS2012 to VS2013. But you can
still use batch script or some other script to execute and build your
components. Almost 2 years ago, I had to port a bunch of batch scripts to
build user and drivers components using new msbuild.

I had to take lot of helps from Doron, and other internal build people to
get it thru. At that time, VS2012 just got released.

May be searching the archive might give some pointers…

-pro

On Tue, Dec 17, 2013 at 5:41 PM, John Matsumoto wrote:

> Not to sound like a dinosaur, but I’m still using command lines to build
> both my drivers and to sign them. I’m now moving onto VS2013 as my build
> environment. Would there perhaps be a webinar or YouTube on the start to
> finish of building a device driver with VS2013 (build -> debug -> Verisign
> -> test/QA -> WHQL)? Just the build to release process done entirely with
> VS2013. I know parts of VS2013 process but would like to know how to do it
> from start to finish.
>
> Thanks,
> Motz
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Pavel A.
> Sent: Tuesday, December 17, 2013 2:06 PM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] New OSR List for VS2013 Driver Development?
>
> On 16-Dec-2013 08:47, the wrote:
> > Can anyone explain how to write makefiles (GNU make) and compile
> > drivers?
>
> For Linux - gladly. For Windows… you see, this is exactly what
> “unsupported” means: one can ask for help with an unsupported thing, but
> won’t necessarily get help.
> --pa
>
>
>
> —
> 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
>
>
> —
> 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
>

23

Prokash Sinha wrote:

I don’t know how much has been changed from VS2012 to VS2013. But you
can still use batch script or some other script to execute and build
your components. Almost 2 years ago, I had to port a bunch of batch
scripts to build user and drivers components using new msbuild.

I had to take lot of helps from Doron, and other internal build people
to get it thru. At that time, VS2012 just got released.

There’s not that much magic required. msbuild /p:Configuration=“Win7
Debug”,Platform=x64 replaces the “build” and “sign” steps. The rest is
pretty much unchanged.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

24

I truly wish it were that easy :slight_smile: From directory structures to lot of other problem, going thru the project files etc. Well lot of it also depends on how good were those scripts ( like macro definitions, so slight changes can make them dance to developers tune).

I don’t have those email trails, any more… So …

-pro

Date: Tue, 17 Dec 2013 16:22:13 -0800
From: xxxxx@probo.com
To: xxxxx@lists.osr.com
Subject: Re: [ntdev] New OSR List for VS2013 Driver Development?

Prokash Sinha wrote:
> I don’t know how much has been changed from VS2012 to VS2013. But you
> can still use batch script or some other script to execute and build
> your components. Almost 2 years ago, I had to port a bunch of batch
> scripts to build user and drivers components using new msbuild.
>
> I had to take lot of helps from Doron, and other internal build people
> to get it thru. At that time, VS2012 just got released.

There’s not that much magic required. msbuild /p:Configuration=“Win7
Debug”,Platform=x64 replaces the “build” and “sign” steps. The rest is
pretty much unchanged.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

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

25

Thanks to everyone for your helpful advice. No, we’re not required to do
everything through VS2013. But not knowing exactly what VS2013 can do for us
(actually, I’ve only just loaded VS2013 and haven’t even used it yet) and IF
Microsoft has gone through the effort to have a methodology to take a driver
from start to finish with VS2013, I thought it would be prudent to learn it.

Thanks again,
Motz

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bruce Cran
Sent: Tuesday, December 17, 2013 4:09 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] New OSR List for VS2013 Driver Development?

On 12/17/2013 4:41 PM, John Matsumoto wrote:

Not to sound like a dinosaur, but I’m still using command lines to
build both my drivers and to sign them. I’m now moving onto VS2013 as
my build environment. Would there perhaps be a webinar or YouTube on
the start to finish of building a device driver with VS2013 (build ->
debug -> Verisign
-> test/QA -> WHQL)? Just the build to release process done entirely
-> with
VS2013. I know parts of VS2013 process but would like to know how to
do it from start to finish.

Do you *want* to do it all within Visual Studio though? What we do is make
it simple for developers to build the driver in VS for
development/debugging, but all the staging/signing/packaging is done via
MSBuild scripts outside the IDE, building the C/C++/WiX/etc. code via the
‘MSBuild’ task which doesn’t need to run devenv.

–
Bruce

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

26

You can get to the point of building, packaging and real signing a driver for production (I assume provisioning and loading a machine under test is not germain here). After that, be it self signed or WHQL, there is no automated process for that in the wdk

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of John Matsumoto
Sent: Tuesday, December 17, 2013 4:54 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] New OSR List for VS2013 Driver Development?

Thanks to everyone for your helpful advice. No, we’re not required to do everything through VS2013. But not knowing exactly what VS2013 can do for us (actually, I’ve only just loaded VS2013 and haven’t even used it yet) and IF Microsoft has gone through the effort to have a methodology to take a driver from start to finish with VS2013, I thought it would be prudent to learn it.

Thanks again,
Motz

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bruce Cran
Sent: Tuesday, December 17, 2013 4:09 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] New OSR List for VS2013 Driver Development?

On 12/17/2013 4:41 PM, John Matsumoto wrote:

Not to sound like a dinosaur, but I’m still using command lines to
build both my drivers and to sign them. I’m now moving onto VS2013 as
my build environment. Would there perhaps be a webinar or YouTube on
the start to finish of building a device driver with VS2013 (build ->
debug -> Verisign
-> test/QA -> WHQL)? Just the build to release process done entirely
-> with
VS2013. I know parts of VS2013 process but would like to know how to
do it from start to finish.

Do you *want* to do it all within Visual Studio though? What we do is make it simple for developers to build the driver in VS for development/debugging, but all the staging/signing/packaging is done via MSBuild scripts outside the IDE, building the C/C++/WiX/etc. code via the ‘MSBuild’ task which doesn’t need to run devenv.

–
Bruce

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

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

27

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/18/13 02:05, Pavel A. wrote:

On 16-Dec-2013 08:47, the wrote:
> Can anyone explain how to write makefiles (GNU make) and compile
> drivers?

For Linux - gladly. For Windows… you see, this is exactly what
“unsupported” means: one can ask for help with an unsupported thing, but
won’t necessarily get help.
–pa
So obtaining binaries with the help of a certain compiler is
unsupported. Got it!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSsTfSAAoJEK64IL1uI2ha/7AH/iICukiC54aii7bHbWBVvV4v
zYG+eXL69RFyK6QAylporOAjntdwj5ffYBRIqMP7D8I4XePd2sCSxD+mhKhPSRmd
zCxDOXkf/oxWqvp2NL/jDNL5FxSzItU3afiKEUFZ/bCzdh5EowVNQR+HhTAv7jRc
mdvbYN75gwNBKPkTiDBfsw7XIc2q8GoXZ+j3DpkjI2uq1rax11EQghSKjVxupDDl
emWnthteSYmJMCjlYH2hrM5elY+4J80VGLXv2emFGtV3GwVV2cqBpDY0yoAFJJXG
/u04TZHo20YKV7IL5DpDK1MP1QuF9hotiLVrqPlDcpk+rTc2iiFhoWN6wT13esI=
=XtWE
-----END PGP SIGNATURE-----

28

> Not to sound like a dinosaur, but I’m still using command lines to build

both my drivers and to sign them.

So am I, and these command lines are then executed a a part of major build process governed by CMake.

There are some VSxxx projects, but they are also built the same way - by running command line of Visual Studio from CMake.

–
Maxim S. Shatskih
Microsoft MVP on File System And Storage
xxxxx@storagecraft.com
http://www.storagecraft.com