New Project Setup
I’ve been creating some new projects and it occurs to me that it’s remarkably time-consuming to set up a modern development environment for anything but the simplest of projects.
For me, we’re usually talking C#. Let’s look at the steps…
- Create a new project in Visual Studio.
- Sign it with my strong-named key.
- Manually fix the path to the key in the project file (Visual Studio wants to copy it rather than let you use a relative path).
- Create the companion unit test project.
- Enable code analysis and fix the warnings (seriously — a fresh project doesn’t comply with FxCop rules!).
- Enable XML documentation creation.
- Manually add a step to the build file to create HTML documentation.
- Fill out all the assembly metadata (company, copyright, etc.).
- Add the whole thing to source control.
- If part of a larger solution, I may now have to add it to my automated build process and tell CruiseControl to keep an eye on the source.
Whew! You’d think a programmer would automate some of this stuff.
Comments
Comment from Steve
Date: January 18, 2007, 12:20 am
I think you’re doing a good job at this blogging thing, certainly a better job than me. I tend to find something blog-worthy, think to myself, “Hrm…I should blog about this…”, and then promptly forget the whole experience and end up not writing anything.
Comment from Nessie
Date: January 18, 2007, 3:44 pm
But Steve you did just blog something about a beanbag chair, didn’t you? That is right up there with creating a new project in C#.
Comment from Steve
Date: January 18, 2007, 9:22 pm
You are hi-larious. There, I just blogged about something relevant.
Write a comment