![]() It's discussed in File Security and Access Rights, but not in any useful way. The first parameter, FILE_LIST_DIRECTORY, isn't even mentioned in the CreateFile() documentation. StrDirectory, // pointer to the file nameįILE_LIST_DIRECTORY, // access (read/write) modeįILE_FLAG_BACKUP_SEMANTICS // file attributes Under the documentation for the first parameter, it says “This directory must be opened with the FILE_LIST_DIRECTORY access right.” Later, the Remarks section says, “To obtain a handle to a directory, use the CreateFile function with the FILE_FLAG_BACKUP_SEMANTICS flag.” The actual code looks like this: Did you know that you can get a handle to a directory? There is no OpenDirectory function and the CreateDirectory function doesn't return a handle. When reading the declaration for ReadDirector圜hangesW, you'll notice that the first parameter is to a directory, and it's a HANDLE. Now we'll look at the details of implementing the Balanced solution described in Part 1. Go to the GitHub repo for this article or just download the sample code. Part 1 describes the theory and this part describes the implementation. The longest, most detailed description in the world of how to successfully use ReadDirector圜hangesW. Note that the "Include" command in these rules really means "Exclude" because you checked the box "Files matching this set will be EXCLUDED." Or / Include / Folder name / is / ipch / Files and Foldersįinally, if you use Virtual PC, create a third rule: If you run Visual Studio 2010, also click the plus sign (+) on the right and create a second rule that reads: This will exclude temporary and intermediate files for Visual Studio 2005 through 2010, as well as Virtual PC undo files. ![]() Include / File Type / sdf pch ncb idb tlog sbr res dep obj ilk ipch bsc Next check the box in the top right labeled "Files matching this set will be EXCLUDED." Under the Rules, the first rule should read: In the Backup Set Editor, put a checkmark next to C: so that this rule applies to the entire drive. Create a new backup set and call it something like Excluded Files. To create a rule for Visual Studio, go to the Backup Sets page in the MozyPro configuration. By creating a global rule, the temporary files will be ignored by all other projects. Although MozyPro has a predefined Backup Set named "Visual Studio Projects", I've created other Backup Sets based on projects and customers. I found it best to create a global rule instead of modifying one of the predefined Backup Sets. This article tells how to set up MozyPro so that files with those extensions will not be backed up. bsc, and others, all of which are unnecessary to backup. There are numerous other temporary files, such as. Since Visual Studio automatically rebuilds this file as necessary, it's a waste of time and money to back it up. sdf file) is 70MB to 300MB for each project. In Visual Studio 2010, the IntelliSense data (the. One of my frustrations in earlier versions of MozyPro was figuring out how to exclude Visual Studio temporary files. In short, MozyPro went from something I found acceptable to something that I am quite happy with. Earlier this week I revised my review of Mozy based on version 2.0 of the MozyPro client software.
0 Comments
Leave a Reply. |