-{wiki: Introduction}
+{section: Introduction}
-Assuming you have read-up on how to create a new Condor Daemon ({wiki: CreatingNewDaemons Creating a new daemon}-a somewhat dated, but useful reference for a budding Daemon Core user) or you have a really cool new tool in mind, then the following will help you add a new Project to Condor's Visual Studio Solution file.
+Assuming you have read-up on how to create a new Condor Daemon ({wiki: CreatingNewDaemons Creating a new daemon} -- a somewhat dated, but useful reference for a daemon developer) or you have a really cool new tool in mind (even a boring one will do too), then the following will help you add a new Project to Condor's Visual Studio Solution file.
+
+For those not versed in the Microsoft development lexicon, a *Project* as one would expect is a structure that defines a new executable, dynamic link library, etc. anything that Visual Studio can build. As *Solution* is simply a collection of *Projects* that enforces pre-defined inter-project dependencies, like a *Makefile*. All Project files are represented in XML, so they can easily be created and modified by anyone with sufficient XML know how. Solution files, on the other hand, are still a proprietary -- although text, but not very human consumable (it's just lists of GUIDs) -- so it is best to leave Visual Studio's capable hands to make any of you desired changes. This, unfortunately, means that a Windows developer may still always be involved in the introduction of a new Project.
+
+{section: Project Types}
