As I wander further into the landscape of Test-Driven Development and ASP.NET MVC, I find myself being pounded by tools. The Dependency Injection frameworks like StructureMap, Unity, NInject, Castle Windsor, Pico.NET and Spring.NET. It's also damn near impossible to do TDD without hitting a mocking framework like RhinoMocks, Moq, TypeMoq and NMock. Then, if you're serious about your enterprise-level development, you begin looking at code analysis and documentation generation frameworks. flame11

Now maybe I have been living in the unorganized underverse of development, but none of the small companies I have worked for has had the time and budget to do ALL of this  stuff,  and of course ALL of it is not necessary for every project, but I wanted to get a community opinion.

What tools do YOU use? Now, I know this has sparked enormous flame wars in the past, but that's not my intent. We are all grownups, and most of us are accomplished developers and architects. I think we all realize the there is no RIGHT way; only the best way we know how for the current circumstances. I just want to get a feel for what people are using and why. I'd like it if the comments stuck to compliments about your particular tools and NO DEGRADING OTHERS' TOOLS.

In the next few months, I am going to try to put together a comprehensive, non-biased comparison of the frameworks (at least for DI and Object Mocking). This may make me a target, but I have to make a desicion as to what is best for me, and I have NO preconceived ideas about these frameworks.

So cast your vote for your faves and I'll try to compare them and get some kind of matrices out so that people can use them as a good starting point for deciding which frameworks best fit them and their environment.

Happy commenting!

~L

posted on Sunday, April 20, 2008 10:32 PM |
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Comments

Gravatar
# re: Tools for .NET development
Posted by Lee Brandt
on 4/21/2008 7:37 PM
OK. I've been using RhinoMocks, StructureMap and MSTest for unit testing.
Anyone?
Bueller?
Gravatar
# re: Tools for .NET development
Posted by Cyril Gupta
on 4/22/2008 10:44 AM
Right now I am NOT using ANY tools. I guess I have one of the small companies you were talking about that don't have the time for ALL this. But I am seriously contemplating moving to TDD in forseeable future.
Gravatar
# re: Tools for .NET development
Posted by Sendhil
on 4/23/2008 12:02 AM
I right now use Spring.NET & Rhino Mocks. I am also interested in moving to Windsor because I dont like Spring.NET. I also would like to evaluate Moq unless Ayende comes up fast with Rhino Mocks 3.5 Edition real quick http://www.ayende.com/Blog/archive/2008/02/18/Planning-Rhino-Mock-3.5--The-Lambda-Edition.aspx

Regards,
Gravatar
# re: Tools for .NET development
Posted by Lee Brandt
on 4/23/2008 12:20 AM
@sendhil: I've been using Rhino with .NET 3.5 using lambdas for my expectations. (e.g. Expect.Call(() => repository.Save(obj));) Is that what you're waiting for? or is there more? Admitedly, I am VERY new to mocking so...

~L
Gravatar
# re: Tools for .NET development
Posted by Kevin Berridge
on 6/10/2008 11:56 AM
Late to the party but...
I work at one of those small companies. I use nmock, nunit but we're switching to MSTest, and TFS Build. I don't use a DI framework.
Gravatar
# re: Tools for .NET development
Posted by Robz
on 7/21/2008 9:01 PM
VS AddIns - R# (required) and TDD.NET (also pretty much required)

SCM - TFS, SVN (other engagements), TortoiseSVN
Testing - MbUnit, Rhino.Mocks
Automated Builds - MSBuild, Nant, CC.Net
Other tools - Windsor, NHibernate

Evaluating - NDepend
Post Comment
Title *
Name *
Email
Url
Comment *