summaryrefslogtreecommitdiff
path: root/filesys/miniFilter/cdo/ReadMe.md
diff options
context:
space:
mode:
Diffstat (limited to 'filesys/miniFilter/cdo/ReadMe.md')
-rw-r--r--filesys/miniFilter/cdo/ReadMe.md16
1 files changed, 16 insertions, 0 deletions
diff --git a/filesys/miniFilter/cdo/ReadMe.md b/filesys/miniFilter/cdo/ReadMe.md
new file mode 100644
index 00000000..750de7b7
--- /dev/null
+++ b/filesys/miniFilter/cdo/ReadMe.md
@@ -0,0 +1,16 @@
+CDO File System Minifilter Driver
+=================================
+
+The CDO minifilter sample is an example if you intend to use a control device object (CDO) with your minifilters.
+
+Although the filter manager infrastructure provides a message interface for communication between applications and minifilters, you might need explicit CDOs while the minifilters interface with legacy software. This sample shows how to create and use a CDO with minifilters.
+
+## Universal Compliant
+This sample builds a Windows Universal driver. It uses only APIs and DDIs that are included in Windows Core.
+
+Design and Operation
+--------------------
+
+When the CDO minifilter is deployed, it creates a CDO object named "FileSystem\\Filters\\CdoSample" in the Microsoft Windows object namespace and enables applications to open it and perform certain operations on it.
+
+For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide.