I am starting to learn such programming (driver programming) since a while.
I used to traditional _ & gt; I mean that I used to use WDK for bulid and compiled driver and was working properly with the simple method of projects, but when I wanted to expand my program or develop a bit, There were small problems. So, I started using VS2.2010 in Windows 7, I really had a lot of problems because I do not have a background, I can use it as well. Finally, I arrive at a good point, saying this thing (if you want to start with driver programming in VS-2010, 1- you should install WDK2 - 2 -VS2010 Installing 3- VSD 2010 Directors have to keep the path of WWDK headquarters decryts together. The Makefile Project Finally, I'm not really sure, this is the right way Or not, I just started But I liked it and I got a good result And I found: My question is this: Is this the correct way? How can I know that this program is working properly? Should I do something else to get my program to work correctly in kernel mode? Never create a driver in Visual Studio! The only way to create a driver is to: Open WDK build environment command prompt, type the CD in the driver's project directory, and "build". You can use Visual Studio as the only source code editor, but do not create a driver with it! There are several ways to do this, which are published in various programming sites, but professional driver developers have advised to use only the WDK build for this. To open the WDK build environment, click on the main Windows menu - Program - Windows Driver Kit - WDK - Build Environment - Choose Target OS - Choose the built environment according to the target computer processor type. Check Build Building means debug, release of free build environment means.
#include "wdm.h" NTSTATUS driver directory (IN PDRIVER_OBJECT theDriverObject, INPUNICODE_STRINGRegistryPath) {DbgPrint ("Hello World!"); Return STATUS_SU ccess;}
1> ------ Build Started: Project: 1, Configuration: Win32 ----- - 1> C: \ Program Files \ MSBuild \ Microsoft.Cpp \ v4.0 \ Microsoft.MakeFile.Targets (37,5): Warning MSB8005 : Property 'NMakeBuildCommandLine' does not exist ... ========== Build: 1 succeeded, 0 failed, 0 upt -Date, 0 skipped ==========
Comments
Post a Comment