Context Menu Extension in ATL

Context Menu Shell Extension DLL using written in ATL with the following requirements: 1) Must designate the GUID in the C++ application. I have seen the code for that in examples, but I don’t know how it is done. 2) Must be able to handle both files and folder paths. It will be registered to: a. HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers b. HKEY_CLASSES_ROOT\Folder\shellex\ContextMenuHandlers 3) I have an example and a wizard from CodeProject.com. One example is a wizard created for Visual Studio 6 (you must develop this in that environment unless you can make Visual Studio 2003 work). I request you use the example or wizard provided to be a base for this project. From what I can see, you will not need to write much code to extend the functionality for my purposes. Please give a very good reason if you don’t want to use those examples. 4) I believe the paths of files and folder are accessible from an array of strings already from what I can read of the C++ (I know a tiny bit of C++, but I’m mainly a VB6 coder) in the examples. You may need to add some code to the function to make sure it gets all selected file system objects (files and folders). 5) You will be adding one menu item. That is handled by the examples and is very simple. 6) When the item is clicked by a user, the DLL will do the following: a. Using the Window Environment variables, find the TEMP directory for that current user. Then you will create a text file for writing, deleting it if I already exist. Then you will write to the file, line by line, the paths of each file system object currently selected by the user in Window Explorer. Not hard from my perspective. You will then cleanly close the file and create a process and running another exe. b. I have already written that app and I am currently working on the installer for this project. Those are mine and hope to keep it that way. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Windows XP/2000 a must Windows Me,9x OSes a big plus