Vs 2012 & driver build

Correct. We generate the cat as a part of the package project

  1. does "C:\Users\prokash\dp_5_17\DPLEX\win\portfltr\Win8Debug\x64\nveloportfltr.sys exist?
  2. is there a copy of the sys and inf in x64\Win8Debug\Package ?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Friday, June 8, 2012 11:46 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Vs 2012 & driver build

Looks like empty placeholder type cat file is no longer an option???

-pro


NTDEV is sponsored by OSR

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

C41A8F23187161983235A3EF1@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
To: “Windows System Software Devs Interest List”
X-Mailer: Apple Mail (2.1278)
X-Barracuda-Connect: mail201.messagelabs.com[216.82.254.211]
X-Barracuda-Start-Time: 1339182980
X-Barracuda-URL: http://208.13.232.231:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at osr.com
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL00.0 KILL_LEVEL=6.0 testsX-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.99296
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------------------------

Yes, both file exist.

The folder structure is <buildtype><platform>

I’ve not seen any Package folder anywhere. Am I suppose to have such a folder ?

-pro

On Jun 8, 2012, at 11:57 AM, Doron Holan wrote:

> Correct. We generate the cat as a part of the package project
>
> 1) does "C:\Users\prokash\dp_5_17\DPLEX\win\portfltr\Win8Debug\x64\nveloportfltr.sys exist?
> 2) is there a copy of the sys and inf in x64\Win8Debug\Package ?
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
> Sent: Friday, June 8, 2012 11:46 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Vs 2012 & driver build
>
>
>
> Looks like empty placeholder type cat file is no longer an option???
>
> -pro
>
> —
> NTDEV is sponsored by OSR
>
> 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
>
> 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

C41A8F23187161983235A3EF1@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
To: “Windows System Software Devs Interest List”
X-Mailer: Apple Mail (2.1278)
X-Barracuda-Connect: mail28.messagelabs.com[216.82.249.131]
X-Barracuda-Start-Time: 1339183172
X-Barracuda-URL: http://208.13.232.231:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at osr.com
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL00.0 KILL_LEVEL=6.0 testsX-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.99296
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------------------------

Never mind there is a -Package folder. Yes just that two files sitting there…

On Jun 8, 2012, at 11:57 AM, Doron Holan wrote:

> Correct. We generate the cat as a part of the package project
>
> 1) does "C:\Users\prokash\dp_5_17\DPLEX\win\portfltr\Win8Debug\x64\nveloportfltr.sys exist?
> 2) is there a copy of the sys and inf in x64\Win8Debug\Package ?
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
> Sent: Friday, June 8, 2012 11:46 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Vs 2012 & driver build
>
>
>
> Looks like empty placeholder type cat file is no longer an option???
>
> -pro
>
> —
> NTDEV is sponsored by OSR
>
> 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
>
> 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

The creation of a driver package (ie copying the inf and sys file into a dir as well as other collateral files) occurs in a driver package project, not in the driver project itself. Inf2cat should only run in the package projec

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Friday, June 8, 2012 12:16 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Vs 2012 & driver build

C41A8F23187161983235A3EF1@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
To: “Windows System Software Devs Interest List”
X-Mailer: Apple Mail (2.1278)
X-Barracuda-Connect: mail201.messagelabs.com[216.82.254.211]
X-Barracuda-Start-Time: 1339182980
X-Barracuda-URL: http://208.13.232.231:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at osr.com
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL00.0 KILL_LEVEL=6.0 testsX-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.99296
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------------------------

Yes, both file exist.

The folder structure is <buildtype><platform>

I’ve not seen any Package folder anywhere. Am I suppose to have such a folder ?

-pro

On Jun 8, 2012, at 11:57 AM, Doron Holan wrote:

> Correct. We generate the cat as a part of the package project
>
> 1) does "C:\Users\prokash\dp_5_17\DPLEX\win\portfltr\Win8Debug\x64\nveloportfltr.sys exist?
> 2) is there a copy of the sys and inf in x64\Win8Debug\Package ?
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
> Sent: Friday, June 8, 2012 11:46 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Vs 2012 & driver build
>
>
>
> Looks like empty placeholder type cat file is no longer an option???
>
> -pro
>
> —
> NTDEV is sponsored by OSR
>
> 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
>
> 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

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

The listserver might be in alert mode :), seeing some odd behavior.

I just saw there is that driver-Packages folder, and as per your path, yes only the two files exist there. On the studio I saw it creates two projects, I think the *.sln file contain both projects, so when I invoke the msbuild, the final stage is to package!!

Yes, both file exist.

The folder structure is <buildtype><platform>
>
> I’ve not seen any Package folder anywhere. Am I suppose to have such a folder ?
>
> -pro
>
> On Jun 8, 2012, at 11:57 AM, Doron Holan wrote:
>
>> Correct. We generate the cat as a part of the package project
>>
>> 1) does "C:\Users\prokash\dp_5_17\DPLEX\win\portfltr\Win8Debug\x64\nveloportfltr.sys exist?
>> 2) is there a copy of the sys and inf in x64\Win8Debug\Package ?
>>
>>
>>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
>> Sent: Friday, June 8, 2012 11:46 AM
>> To: Windows System Software Devs Interest List
>> Subject: Re: [ntdev] Vs 2012 & driver build
>>
>>
>>
>> Looks like empty placeholder type cat file is no longer an option???
>>
>> -pro
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> 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
>>
>> 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
>
> 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
>
> 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

We built the driver package project infrastructure to create one package per architecture vs mult architectures in the same package. This is the guidance we now give on MSDN in general for driver packages. Multiple architectures in the package is quite difficult to get right and highly problematic. In that light, the following in your INF is probably the source of confusion

[SourceDisksNames.x86]

1 = %diskid1%,\i386

The package project must be looking for the sys file in .\i386 sub folder of where the inf file resides. inf2cat thinks sys file is located in x64\Win8Debug\Package\i386 folder instead of x64\Win8Debug\Package because of that entry.

So, I think you have two choices

  1. Refactor the INF into arch specific packages

Or

  1. You can attempt to create per architecture copy file directives that override the default copy behavior the package project has. You can do this by right clicking on the driver package project in the UI, select Properties, then Configuration Properties | Driver Install | Package Files and then fill out the table. You want to be careful of the configuration that you do this for. For instance, to do this for all x86 targets (ie vista through win8), select “All Configruations” in the Configuration dropdown at the top of the property dialog and then choose Win32 for the Platform

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Friday, June 8, 2012 12:29 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Vs 2012 & driver build

The listserver might be in alert mode :), seeing some odd behavior.

I just saw there is that driver-Packages folder, and as per your path, yes only the two files exist there. On the studio I saw it creates two projects, I think the *.sln file contain both projects, so when I invoke the msbuild, the final stage is to package!!

Yes, both file exist.

The folder structure is <buildtype><platform>

I’ve not seen any Package folder anywhere. Am I suppose to have such a folder ?

-pro

On Jun 8, 2012, at 11:57 AM, Doron Holan wrote:

Correct. We generate the cat as a part of the package project

1) does "C:\Users\prokash\dp_5_17\DPLEX\win\portfltr\Win8Debug\x64\nveloportfltr.sys exist?
2) is there a copy of the sys and inf in x64\Win8Debug\Package ?

-----Original Message-----
From: xxxxx@lists.osr.commailto:xxxxx [mailto:xxxxx@lists.osr.com]mailto: On Behalf Of Prokash Sinha
Sent: Friday, June 8, 2012 11:46 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Vs 2012 & driver build

Looks like empty placeholder type cat file is no longer an option???

-pro


NTDEV is sponsored by OSR

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

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

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

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

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</mailto:></mailto:xxxxx>

I would try the option 2 first to see if I get it right. Having arch specific packages could stay as 2nd option, since it would be good to have one package per driver ( unless I feel bit more comfortable about packages ).

Thanks, this helps - really.

-pro

On Jun 8, 2012, at 12:49 PM, Doron Holan wrote:

We built the driver package project infrastructure to create one package per architecture vs mult architectures in the same package. This is the guidance we now give on MSDN in general for driver packages. Multiple architectures in the package is quite difficult to get right and highly problematic. In that light, the following in your INF is probably the source of confusion

[SourceDisksNames.x86]
1 = %diskid1%,\i386

The package project must be looking for the sys file in .\i386 sub folder of where the inf file resides. inf2cat thinks sys file is located in x64\Win8Debug\Package\i386 folder instead of x64\Win8Debug\Package because of that entry.

So, I think you have two choices

  1. Refactor the INF into arch specific packages
    Or
  2. You can attempt to create per architecture copy file directives that override the default copy behavior the package project has. You can do this by right clicking on the driver package project in the UI, select Properties, then Configuration Properties | Driver Install | Package Files and then fill out the table. You want to be careful of the configuration that you do this for. For instance, to do this for all x86 targets (ie vista through win8), select ?All Configruations? in the Configuration dropdown at the top of the property dialog and then choose Win32 for the Platform
    d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Friday, June 8, 2012 12:29 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Vs 2012 & driver build

The listserver might be in alert mode :), seeing some odd behavior.

I just saw there is that driver-Packages folder, and as per your path, yes only the two files exist there. On the studio I saw it creates two projects, I think the *.sln file contain both projects, so when I invoke the msbuild, the final stage is to package!!

Yes, both file exist.

The folder structure is <buildtype><platform>
>
> I’ve not seen any Package folder anywhere. Am I suppose to have such a folder ?
>
> -pro
>
> On Jun 8, 2012, at 11:57 AM, Doron Holan wrote:
>
>
> Correct. We generate the cat as a part of the package project
>
> 1) does "C:\Users\prokash\dp_5_17\DPLEX\win\portfltr\Win8Debug\x64\nveloportfltr.sys exist?
> 2) is there a copy of the sys and inf in x64\Win8Debug\Package ?
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
> Sent: Friday, June 8, 2012 11:46 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Vs 2012 & driver build
>
>
>
> Looks like empty placeholder type cat file is no longer an option???
>
> -pro
>
> —
> NTDEV is sponsored by OSR
>
> 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 athttp://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> NTDEV is sponsored by OSR
>
> 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 athttp://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> 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 athttp://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> NTDEV is sponsored by OSR
>
> 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 athttp://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> 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
>
> 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

I’ve finally got one build (Win8Debug) on x64 done, including the cat file processing/signing done. But I could not find ( from searching the cloud ) a way to build all the types ( for example:: Release | Debug ) as well as Win7 | Win8.

I’m missing an obvious thing… Currently for each component ( drivers, services, apps, libs ) we have batch files that used to build ( using wdk build enviornments) and package them up for installation. So the thing I’m looking for is to issue “msbuild ” to build.

The batch file would be invoked for each component, so if it is , then it should build All the OS specific build as well as architecture specific ( this one I’m building only for x64 now ).

From the batch file I use something like this “msbuild <component.sln> /p:Platform=x64” without quote.

It only builds the Win8Debug. I see the .sln file has all the variations I’m looking for, also the vcxproj file has those. Build does not have error, so there is not abrupt stops.

RK: The idea is to build using the same set of batch files (1) from wdk env. (2) new win8 msbuild env. Bunch of ( actually lot of ) test firing would start, and comparing would be easier to stave off “Oh this one used to work, now it does not, and vice versa…”

-pro

On Jun 8, 2012, at 1:13 PM, Prokash Sinha wrote:

> I would try the option 2 first to see if I get it right. Having arch specific packages could stay as 2nd option, since it would be good to have one package per driver ( unless I feel bit more comfortable about packages ).
>
> Thanks, this helps - really.
>
> -pro
>
> On Jun 8, 2012, at 12:49 PM, Doron Holan wrote:
>
>> We built the driver package project infrastructure to create one package per architecture vs mult architectures in the same package. This is the guidance we now give on MSDN in general for driver packages. Multiple architectures in the package is quite difficult to get right and highly problematic. In that light, the following in your INF is probably the source of confusion
>>
>> [SourceDisksNames.x86]
>> 1 = %diskid1%,\i386
>>
>> The package project must be looking for the sys file in .\i386 sub folder of where the inf file resides. inf2cat thinks sys file is located in x64\Win8Debug\Package\i386 folder instead of x64\Win8Debug\Package because of that entry.
>>
>> So, I think you have two choices
>> 1) Refactor the INF into arch specific packages
>> Or
>> 2) You can attempt to create per architecture copy file directives that override the default copy behavior the package project has. You can do this by right clicking on the driver package project in the UI, select Properties, then Configuration Properties | Driver Install | Package Files and then fill out the table. You want to be careful of the configuration that you do this for. For instance, to do this for all x86 targets (ie vista through win8), select ?All Configruations? in the Configuration dropdown at the top of the property dialog and then choose Win32 for the Platform
>> d
>></component.sln>