The Importance of a Consistent Development Environment

29 Sep

I am again traveling this week, in Toronto speaking at Tech Days Canada 2009, and as luck would have it I needed to complete some work on a few custom DotNetNuke modules for clients on a "Urgent" basis.  So this afternoon I darted off to the speaker room to get an internet connection, just recently I re-formatted my laptop to move to Windows 7, one of the main reasons that I needed to re-format the system was to create an environment that matched my primary development machine, today was the first true test of this new configuration.  Thankfully everything worked as expected and all issues were resolved.  In this blog post, I'll explain a bit as to why it is important when working on multiple environments to have consistent system configurations.

What Must Match?

The first question that is most likely going through your mind at the moment is: what items must be "consistent'?  Well my personal recommendation is as much as possible.  For example the Visual Studio Version, DNN installation location, Module working paths, DNN Versions, and other related folders that might be necessary.

In the case of my modules, each has a build file that creates an installation folder for me, since I have yet to move to MSBuild the paths are hard coded, referencing my folder structure on my primary machine.  Builds on that machine all go to my D: drive and on my laptop prior to the re-install I didn't have a D: drive at all.

So Why Do You Care?

The key point of this exercise is why do I care?  Well this is very simple, if all of the above items match from one system to another, it is possible to simply open your source control system, do a "get latest version" and you can instantly change files and only worry about checking in changes.  If you have environment differences, say for referenced DLL's, or build paths, it might be possible to need to modify files that normally wouldn't be changed, then if you check those in, you wind up breaking your existing development environment.

This is an important thing when working on projects with one developer and multiple machines, as well as when working with multiple developers on the same project.  Establishing a consistent development configuration will help you avoid hassles and problems that can arise from different file paths and references.


tags: .NET 1.1, .NET 2.0, General Tech, .NET 3.5, DNN Development
comments powered by Disqus

Content provided in this blog is provided "AS-IS" and the information should be used at your own discretion.  The thoughts and opinions expressed are the personal thoughts of Mitchel Sellers and do not reflect the opinions of his employer.

Connect with Mitchel

I hope the information here has been helpful. To stay connected you can also subscribe to blog updates via email, contact Mitchel about consulting services, or reach out for assistance via CodeMendor

Content Copyright

Content in this blog is copyright protected.  Re-publishing on other websites is allowed as long as proper credit and backlink to the article is provided.  Any other re-publishing or distribution of this content is prohibited without written permission from Mitchel Sellers.