The very most frustrating thing about using Microsoft developer tools
Is when I want to do something and the tools' programmers refuse to let me do it.
- Created a directory under source control. Must be the first step, because a fellow developer went slap-happy with the directory tree and adding a new directory became delicate and fraught with peril.
- Using Visual Studio 2003 Enterprise Developer Edition Super-Extra-Heavy With Moisturizer, created a C# web project.
- Cannot create the C# web project, because the new project dialog forces me to choose a virtual directory on the local web server, instead of a file location.
Listen up, Microsoft numbnuts - I know where I want to put the files. I am capable of hooking this fancy-pants new web project up to the web server myself. Let me freakin' do it!
- Create the web project anyway.
- Go searching for it, since I know it saved the file somewhere but damned if I can find them easily.
- Create an empty solution.
- Create an empty project.
- Repeat the previous 2 steps until I finally get the new project to sit nicely alongside the new solution, instead of in a subdirectory.
- Copy the web project's code files into the new project which is in the new directory which is where the new solution file is.
- Look at the clock.
- Regret that this process took hours.