Thanks, I will keep committing all changes at the same time. Might make less changes between each commit to reduce the information that should be included in the log. I have not been committing changes regularly as I am the only developer. Cages

Option 3. Use a logging framework such as log4net where somebody else has taken care of the development and testing of this for you. I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be Forgive your enemies - it messes with their heads My blog | My articles | MoXAML PowerToys | Onyx

I use references and set their property to "copy local" or something like that. You can reference other projects so the dll is rebuilt and imported automatically to your build directory. For asp.net, I guess you could use the strategy of having an "assemblies" directory and set their build action to "copy to output directory", and "copy if newer". If that is not available in asp.net, you could use a post build script to copy the files from assemblies to bin. And if all else fails, I think it's possible to declare that directory as a dll search path or something in the config, but that's less than ideal because it breaks the "standard" directory structure of an asp.net site...