I installed WinDDK 7.1.0 in a XP machine and then VS2008.
Now i wanted to launch SDV to check my code but i donot see driver menu in VS2008 window.
Please help on this.
Go ask the guy who wrote winddk, that is not supported config from the msft pov
d
Bent from my phone
From: xxxxx@gmail.commailto:xxxxx
Sent: ?6/?1/?2015 6:42 AM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] Urgent: no driver menu in VS2008
I installed WinDDK 7.1.0 in a XP machine and then VS2008.
Now i wanted to launch SDV to check my code but i donot see driver menu in VS2008 window.
Please help on this.
—
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</mailto:xxxxx></mailto:xxxxx>
xxxxx@gmail.com wrote:
I installed WinDDK 7.1.0 in a XP machine and then VS2008.
Now i wanted to launch SDV to check my code but i donot see driver menu in VS2008 window.
Right. Versions of the WDK prior to Windows 8 do not integrate with
Visual Studio at all. In order to have a driver menu, you have to be
using Visual Studio 2013 and WDK 8.1.
You can launch SDV from a command-line using one of the build
environment set up by the WDK installer.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Thank you Tim…
One more query.
I use XP free build environment setup by WDK installer.
In WDK documentation, I read that before launching SDV scan command i should build the library by using the staticdv /lib command.
When I changed the path to my source code path and run this lib cmd, I received a message as " Build ‘Driver’ …Done
This is not a valid library folder."
I opened VS command prompt, located driver source code path for my project “Driver.vcproj” and tried running cmd “msbuild /t:sdv /p:Inputs=”/check:*" Driver.vcproj /p:Configuration=“Windows 7 Release”/p:Platform=Win32".
Got error as " build failed. MSB 4057, the target sdv does not exist in the project".
ttempted VS command prompt
Thank you Tim…
One more query.
I use XP free build environment setup by WDK installer.
In WDK documentation, I read that before launching SDV scan command i should build the library by using the staticdv /lib command.
When I changed the path to my source code path and run this lib cmd, I received a message as " Build ‘Driver’ …Done
This is not a valid library folder."
I opened VS command prompt, located driver source code path for my project “Driver.vcproj” and tried running cmd “msbuild /t:sdv /p:Inputs=”/check:*" Driver.vcproj /p:Configuration=“Windows 7 Release”/p:Platform=Win32".
Got error as " build failed. MSB 4057, the target sdv does not exist in the project".
There’s your issue, I think.
You don’t build from the VS command prompt. The version of the WDK you’re using doesn’t integrate with OR EVEN USE Visual Studio at all.
You need to build from the “special” command prompt window that sets up the “build environment” for your desired target. THis is launched by the WDK shortcut under Start->Programs->Development Kits->Window WDK->BuildEnvironments->WinXP->Checked (or whatever)
HTH,
Peter
OSR
@OSRDrivers
I tried msbuild command in cmd launched by Start->Programs->Development Kits->Window
WDK->BuildEnvironments->WinXP free cmd.
Error received as “‘msbuild’ is not recognized as an internal or external command,
operable program or batch file.”
Use “build” and not “msbuild”
wrote in message news:xxxxx@ntdev…
>I tried msbuild command in cmd launched by Start->Programs->Development Kits->Window
> WDK->BuildEnvironments->WinXP free cmd.
>
> Error received as “‘msbuild’ is not recognized as an internal or external command,
> operable program or batch file.”
>
xxxxx@gmail.com wrote:
I use XP free build environment setup by WDK installer.
In WDK documentation, I read that before launching SDV scan command i should build the library by using the staticdv /lib command.
When I changed the path to my source code path and run this lib cmd, I received a message as " Build ‘Driver’ …Done
This is not a valid library folder."I opened VS command prompt, located driver source code path for my project “Driver.vcproj” and tried running cmd “msbuild /t:sdv /p:Inputs=”/check:*" Driver.vcproj /p:Configuration=“Windows 7 Release”/p:Platform=Win32".
Got error as " build failed. MSB 4057, the target sdv does not exist in the project".
You’re telling us about half the story here.
If you are using the XP Free build environment, then you are have files
called “sources” and maybe “dirs”, and you build your driver by typing
“build” at the build environment command line. There are no vcproj or
vcxproj files, and no sln files. Visual Studio is not involved in any
way, shape, or form.
So, where did you get “Driver.vcproj”?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Maxim,
As i understand, to build my project, I use “build” in xp free environment command prompt.
For SDV, what is the command to be run in XP free env. cmd?
Tim,
I understood that we are talking about two paths here and i confused a little.
After reading your’s and Peter’s posts, I understood the below things.
-
WinDDK - XP free build enviornment cmd
I can build my project using build -cZ.
I can run build command only. -
VS command prompt
I can get driver.vcproj (file name specific to my driver VS project) only when i compile using VS.
I can run SDV using msbuild in VS command prompt or from driver menu in VS project window if WinDDK installed is integrated with VS.
Here, my problem is WinDDK is not integrated with VS.
Then please suggest how could I run SDV from XP free build env. command to check my driver code?
Staticdv.exe
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Tuesday, June 02, 2015 11:59 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Urgent: no driver menu in VS2008
Maxim,
As i understand, to build my project, I use “build” in xp free environment command prompt.
For SDV, what is the command to be run in XP free env. cmd?
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
> Here, my problem is WinDDK is not integrated with VS.
So, forget .vcproj forever with this WDK version.
Use newer WDK for .vcproj
–
Maxim S. Shatskih
Microsoft MVP on File System And Storage
xxxxx@storagecraft.com
http://www.storagecraft.com
xxxxx@gmail.com wrote:
I understood that we are talking about two paths here and i confused a little.
After reading your’s and Peter’s posts, I understood the below things.
- WinDDK - XP free build enviornment cmd
I can build my project using build -cZ.
I can run build command only.
Correct. For WDKs prior to the Win 8 WDK, this is the standard
operating procedure. Everything is done from the command line.
- VS command prompt
I can get driver.vcproj (file name specific to my driver VS project) only when i compile using VS.
I can run SDV using msbuild in VS command prompt or from driver menu in VS project window if WinDDK installed is integrated with VS.
The Win 8.1 WDK requires Visual Studio 2013, which means you use a
.vcxproj, not a .vcproj. With that WDK, you can run SDK from within the
IDE.
Maxim is right, you need to forget completely about using Visual Studio
2008 for drivers (except as an editor).
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Okay, I hope I can run the project file wiht VS 2013. The *.vcproj file
that I’m using, has been developed 15 yrs back by someone who is not in our
company anymore and he used VS2008 with WinDDK 7.0, Since I took it back to
do some minimal modifications just wanted to maintain the environment same
for time being.
On Wed, Jun 3, 2015 at 10:15 PM, Tim Roberts wrote:
> xxxxx@gmail.com wrote:
> > I understood that we are talking about two paths here and i confused a
> little.
> > After reading your’s and Peter’s posts, I understood the below things.
> >
> > 1. WinDDK - XP free build enviornment cmd
> > I can build my project using build -cZ.
> > I can run build command only.
>
> Correct. For WDKs prior to the Win 8 WDK, this is the standard
> operating procedure. Everything is done from the command line.
>
>
> > 2. VS command prompt
> > I can get driver.vcproj (file name specific to my driver VS project)
> only when i compile using VS.
> > I can run SDV using msbuild in VS command prompt or from driver menu in
> VS project window if WinDDK installed is integrated with VS.
>
> The Win 8.1 WDK requires Visual Studio 2013, which means you use a
> .vcxproj, not a .vcproj. With that WDK, you can run SDK from within the
> IDE.
>
> Maxim is right, you need to forget completely about using Visual Studio
> 2008 for drivers (except as an editor).
>
> –
> 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
>
It won’t port over. the vcproj you have works in one of two ways
-
It is an nmake project that just shells out to the win7 wdk build underneath the hood
-
It is a hand coded vcproj that approximates the win7 wdk build by hard coding a bunch of configuration values
Either way, the 8.1 wdk has no way of understanding either one. You have two choices
- Start from scratch and throw the vcproj away
a. If you still have a sources file, you can use the wdk’s sources conversion tool to create a vcxproj
- Keep the vcproj and continue with vs2008 and never upgrade until you can’t use it anymore
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of dev srini
Sent: Thursday, June 4, 2015 12:01 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Urgent: no driver menu in VS2008
Okay, I hope I can run the project file wiht VS 2013. The *.vcproj file that I’m using, has been developed 15 yrs back by someone who is not in our company anymore and he used VS2008 with WinDDK 7.0, Since I took it back to do some minimal modifications just wanted to maintain the environment same for time being.
On Wed, Jun 3, 2015 at 10:15 PM, Tim Roberts > wrote:
xxxxx@gmail.commailto:xxxxx wrote:
> I understood that we are talking about two paths here and i confused a little.
> After reading your’s and Peter’s posts, I understood the below things.
>
> 1. WinDDK - XP free build enviornment cmd
> I can build my project using build -cZ.
> I can run build command only.
Correct. For WDKs prior to the Win 8 WDK, this is the standard
operating procedure. Everything is done from the command line.
> 2. VS command prompt
> I can get driver.vcproj (file name specific to my driver VS project) only when i compile using VS.
> I can run SDV using msbuild in VS command prompt or from driver menu in VS project window if WinDDK installed is integrated with VS.
The Win 8.1 WDK requires Visual Studio 2013, which means you use a
.vcxproj, not a .vcproj. With that WDK, you can run SDK from within the
IDE.
Maxim is right, you need to forget completely about using Visual Studio
2008 for drivers (except as an editor).
–
Tim Roberts, xxxxx@probo.commailto:xxxxx
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
— 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</mailto:xxxxx></mailto:xxxxx>
That’s not good news… as I think you’ve guessed from this thread, that’s an unsupported configuration (now and when he did it).
Still, drivers typically aren’t that complicated.
WERE you able to build your driver with “build -cZ”? If so, you’re good to go. You have a “SOURCES” file (that’s just “sources”, nothing after the dot) that describes the driver… and you should be able to import that into the current VS with the WDK add-in installed.
Peter
OSR
@OSRDrivers
I can build driver from WinDDK using build -cZ and also in VS, my solution
file could be build. The build commands are using ‘ddkbuild -W7XP checked’
for debug mode and ‘ddkbuild -W7XP free’ for release mode
Sry, WinDDK build version used by the person is 7600.16385.0 and not WinDDK
7.0
On Thu, Jun 4, 2015 at 6:20 PM, wrote:
>
>
> That’s not good news… as I think you’ve guessed from this thread, that’s
> an unsupported configuration (now and when he did it).
>
> Still, drivers typically aren’t that complicated.
>
> WERE you able to build your driver with “build -cZ”? If so, you’re good
> to go. You have a “SOURCES” file (that’s just “sources”, nothing after the
> dot) that describes the driver… and you should be able to import that
> into the current VS with the WDK add-in installed.
>
> Peter
> OSR
> @OSRDrivers
>
>
> —
> 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
>
On 04-Jun-2015 16:29, dev srini wrote:
WinDDK build version used by the person is 7600.16385.0 and not
WinDDK 7.0
These are almost the same version, with minor fixes which maybe do not
affect your project at all.
But you want to use the latest version for Win7 which is known as 7.1.0
https://www.microsoft.com/en-us/download/details.aspx?id=11800
It’s not clear why they decided to change the release numbering scheme
form WDKs from 6xxx … 7xxx to 7.x. May this be our least significant
trouble.
– pa
On Thu, Jun 4, 2015 at 9:29 AM, dev srini wrote:
> I can build driver from WinDDK using build -cZ and also in VS, my solution
> file could be build. The build commands are using ‘ddkbuild -W7XP checked’
> for debug mode and ‘ddkbuild -W7XP free’ for release mode
>
> Sry, WinDDK build version used by the person is 7600.16385.0 and not
> WinDDK 7.0
>
That’s fine. ddkbuild works quite well using VS as a code editor/project
manager, but that is all it does. You can run sdv by modifying the
parameters to ddkbuild.
Mark Roddy