It’s been a while since I last worked on Windows driver. I’m tryring to build a WDM driver using VS2015
I’ve this in ‘sources’
NTTARGETFILE0 = $(OBJ_PATH)$(O)\my.bmf
I’ve a corresponding mof file.
rc file has this
myDataWMI MOFDATA my.bmf
How these are done in VS2015?
Thanks,
Hakim
One way: create a new WDM project in VS2015 using their “wizard”. Then
throw out all the wizard generated source files (and inf etc.) and replace
with yours.
Another way: take one of the WDK github projects that are wdm and use the
vcxproj from that for your driver, again replacing the original sources
with your own.
Once you get the hang of it, look at the msbuild xml in the vcxproj files.
You can readily replicate this stuff for your own projects without wizards.
Mark Roddy
On Fri, Jul 28, 2017 at 1:22 PM, xxxxx@yahoo.ca
wrote:
> It’s been a while since I last worked on Windows driver. I’m tryring to
> build a WDM driver using VS2015
>
> I’ve this in ‘sources’
>
> NTTARGETFILE0 = $(OBJ_PATH)$(O)\my.bmf
>
> I’ve a corresponding mof file.
>
> rc file has this
>
> myDataWMI MOFDATA my.bmf
>
> How these are done in VS2015?
>
> Thanks,
> Hakim
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></http:>
Another way: use vs2013 to convert sources file via the menu.
Then open the output project with 2015 which should trigger the one way
upgrade tool
On Jul 29, 2017 2:25 AM, “Mark Roddy ” <
xxxxx@lists.osr.com> wrote:
> One way: create a new WDM project in VS2015 using their “wizard”. Then
> throw out all the wizard generated source files (and inf etc.) and replace
> with yours.
>
> Another way: take one of the WDK github projects that are wdm and use the
> vcxproj from that for your driver, again replacing the original sources
> with your own.
>
> Once you get the hang of it, look at the msbuild xml in the vcxproj files.
> You can readily replicate this stuff for your own projects without wizards.
>
> Mark Roddy
>
> On Fri, Jul 28, 2017 at 1:22 PM, xxxxx@yahoo.ca
> wrote:
>
>> It’s been a while since I last worked on Windows driver. I’m tryring to
>> build a WDM driver using VS2015
>>
>> I’ve this in ‘sources’
>>
>> NTTARGETFILE0 = $(OBJ_PATH)$(O)\my.bmf
>>
>> I’ve a corresponding mof file.
>>
>> rc file has this
>>
>> myDataWMI MOFDATA my.bmf
>>
>> How these are done in VS2015?
>>
>> Thanks,
>> Hakim
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> Visit the list online at: http:>> lists.cfm?list=ntdev>
>>
>> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>> software drivers!
>> Details at http:
>>
>> 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 online at: MONTHLY seminars
> on crash dump analysis, WDF, Windows internals and software drivers!
> Details at To unsubscribe, visit the List Server section of OSR Online at</http:></http:>
===> Another way: use vs2013 to convert sources file via the menu.
Yes that will do the trick… i think its the best way .
./nT
I did not find a menu in VS2013 ultimate to convert ‘sources’, probably missing converting tools.
I solved the issue by adding ‘sources’ and mof file to ‘Source Files’
Thanks.
I think that is really the wrong way to go and it is not supported going
forward. The utility does not exist in 2015. The output from the utility is
not the same as what the “wizard” from 2015 generates, and that will
present problems. Use the wizard or clone an existing project and learn you
some msbuild xml until you are comfortable enough to write your own vcxproj
file for a driver.
Mark Roddy
On Sat, Jul 29, 2017 at 4:41 PM, xxxxx@gmail.com
wrote:
> ===> Another way: use vs2013 to convert sources file via the menu.
>
> Yes that will do the trick… i think its the best way .
>
> ./nT
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></http:>
>I solved the issue by adding ‘sources’ and mof file to ‘Source Files’
MOF files belong to the ‘Driver Files’ filter like INF files. You can then right-click on the file and click ‘Properties’ to set MOFCOMP options for th