diff options
Diffstat (limited to 'filesys/fastfat/README.md')
| -rw-r--r-- | filesys/fastfat/README.md | 40 |
1 files changed, 15 insertions, 25 deletions
diff --git a/filesys/fastfat/README.md b/filesys/fastfat/README.md index 00460089..1c409ac7 100644 --- a/filesys/fastfat/README.md +++ b/filesys/fastfat/README.md @@ -8,16 +8,6 @@ products: - windows-wdk --- - -<!--- - name: fastfat File System Driver - platform: WDM - language: cpp - category: FileSystem - description: A file system driver based on the Windows inbox FastFAT file system used as a model for new file systems. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=620305 ----> - # fastfat File System Driver The *fastfat* sample is file system driver that you can use as a model to write new file systems. @@ -28,8 +18,7 @@ The *fastfat* sample is file system driver that you can use as a model to write This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. -Build the sample ----------------- +## Build the sample You can build the sample in two ways: using Microsoft Visual Studio or the command line (*MSBuild*). @@ -39,27 +28,28 @@ You build a driver the same way you build any project or solution in Visual Stud The default Solution build configuration is **Debug** and **Win32**. -**To select a configuration and build a driver** +#### To select a configuration and build a driver + +1. Open the driver project or solution in Visual Studio (find fastfat.sln or fastfat.vcxproj). -1. Open the driver project or solution in Visual Studio (find fastfat.sln or fastfat.vcxproj). -2. Right-click the solution in the **Solutions Explorer** and select **Configuration Manager**. -3. From the **Configuration Manager**, select the **Active Solution Configuration** (for example, Debug or Release) and the **Active Solution Platform** (for example, Win32) that correspond to the type of build you are interested in. -4. From the Build menu, click **Build Solution** (Ctrl+Shift+B). +1. Right-click the solution in the **Solutions Explorer** and select **Configuration Manager**. + +1. From the **Configuration Manager**, select the **Active Solution Configuration** (for example, Debug or Release) and the **Active Solution Platform** (for example, Win32) that correspond to the type of build you are interested in. + +1. From the Build menu, click **Build Solution** (Ctrl+Shift+B). ### Building a Driver Using the Command Line (MSBuild) You can build a driver from the command line using the Visual Studio Command Prompt window and the Microsoft Build Engine (MSBuild.exe) Previous versions of the WDK used the Windows Build utility (Build.exe) and provided separate build environment windows for each of the supported build configurations. You can now use the Visual Studio Command Prompt window for all build configurations. -**To select a configuration and build a driver or an application** +#### To select a configuration and build a driver or an application + +1. Open a Visual Studio Command Prompt window at the **Start** screen. From this window you can use MsBuild.exe to build any Visual Studio project by specifying the project (.VcxProj) or solutions (.Sln) file. -1. Open a Visual Studio Command Prompt window at the **Start** screen. From this window you can use MsBuild.exe to build any Visual Studio project by specifying the project (.VcxProj) or solutions (.Sln) file. -2. Navigate to the project directory and enter the **MSbuild** command for your target. For example, to perform a clean build of a Visual Studio driver project called *filtername*.vcxproj, navigate to the project directory and enter the following MSBuild command: +1. Navigate to the project directory and enter the **MSbuild** command for your target. For example, to perform a clean build of a Visual Studio driver project called *filtername*.vcxproj, navigate to the project directory and enter the following MSBuild command: -```bash -msbuild /t:clean /t:build .\\fastfat.vcxproj -``` +`msbuild /t:clean /t:build .\\fastfat.vcxproj` -Installation ------------- +## Installation No INF file is provided with this sample because the *fastfat* file system driver (fastfat.sys) is already part of the Windows operating system. You can build a private version of this file system and use it as a replacement for the native driver. |