Developer Blog Banter #1: What is your preferred technology stack

Here is the first edition of the Developer Blog Banter. The DBB is a regular article where passionate developers in the community blog on a common topic.
More details and a list of all editions of the DBB is available on the main page

This weeks topic is was inspired by a recent blog post by Paul Stovell.
When starting a new software project, what is your default choices for your technology stack. What common libraries and toolkits do you find yourself reusing again and again.
You can answer the question either from the perspective of “your perfect personal project”, or what your standard choice is for what your day job requires.

Some suggestions to help you get started

  • What UI technologies are you using, web? ASP.Net vanilla, ASP.Net MVC, WPF, Silverlight, Ruby, etc.
  • What would you use to persist / retrieve data. nHibernate, Entity Framework, perhaps you’re using MongoDB as your store.
  • What testing tools / frameworks do you use.
  • Are there any other supporting frameworks you would use in your stack, like Log4Net.

If you need some inspiration or ideas on how to format your response, look at the current list of participants.


  1. David Burela What does your current tech stack look like
  2. Paul Stovell The ultimate Lib folder
  3. Liam McLennan My technology stack
  4. Duncan Bayne What is your preferred technology stack?
  5. Michael Minutillo My (magic unicorns) technology stack
  6. Simone Chiaretta My ASP.NET MVC stack and why I chose it
  7. Damian Maclennan What’s your current stack?
  8. Eric Ridgeway My technology stack
  9. Ko Chang What is your preferred technology stack
  10. Paul Batum My technology stack
  11. Composite code My software stack

By David Burela

What does your current technology stack look like?

In response to the first Developer Blog Banter

Most of my projects look like this

Technology stack


  • Silverlight 4
  • Ninject (IoC)
  • Prism (on occasion)
  • RIA services
  • Entity framework
  • Sql server 2008 R2
  • nSubstitute (for mocking. Made in Australia!)
  • MSTest

Looking at feedback Paul received, I think that I will need to look into using nBuilder soon to create test data for my unit tests. I am using MSTest, because I like how it is easy for developers to just have VS2010 (+apis) installed and run the tests immediately.

Source control

For projects on client sites, I am using TFS 2010 setup with continuous integration.

At home, I don’t have a source control solution. I just zip up the source code folder at intervals and name it ProjectName YYMMDDHHmmSS e.g. DavidProject

I know that the way I do source control isn’t optimal. So after talking to Paul Stovell and Miguel Madero at Code Camp South Australia last weekend, I have decided that I am going to start using Mercurial to help me to check in locally.

So how about you? What are your standard tools right now for new projects?

By David Burela