Geek Answers Handbook

.Net: Contemporary Art in Tools and Frames

This is a question for those who work in .Net , and it is curious enough to expand their set of tools, including those outside of Microsoft solutions.

From the Java world, there is a set of tools that I would consider using each new project, for example:

  • Spring for IoC and MVC.
  • JPA / Hibernate for saving and ORM.
  • JUnit / TestNG for unit testing.
  • Maven for building management.
  • Sonar for code quality indicators.
  • CruiseControl / Hudson for continuous integration.
  • Etc.

Question

What will be a similar set of tools for high-quality .Net projects?

My (basic) knowledge tells me that I should look at NHibernate and NUnit. In addition, I can still use CruiseControl for CI if my build procedure and test scripts sound. It makes sense? Any other noteworthy tools? (from MS or from the community)

Some people told me about the latest Microsoft tools for CI (Team System, etc.), but they did not have real experience in their hands. If you have such an experience, you can share it.

+4
source share
5 answers

Just replace ā€œJā€ with ā€œNā€ and you're almost done ...

  • Spring.Net (or Windsor / Castle or LinFu)
  • NHibernate
  • NUnit (or MbUnit, which I prefer, or xUnit.Net)
  • NDepend for code quality metrics
  • CruiseControl.Net (or better: TeamCity)

also definitely useful:

  • NCover for code coverage analysis
  • MS StyleCop / FxCop for text / static code analysis
  • Simian for code detection

NTN
Thomas

+3
source

Our current stack when working is as follows:

  • Windsor Castle for IoC
  • NHibernate to save / ORM
  • NUnit for unit testing (I am also working on adopting a mocking structure like Moq or Rhino.Mocks).
  • MSBuild for assembly
  • TestDriven.NET for unit testing in Visual Studio
  • TeamCity for CI (although in the past we used CruiseControl.NET/NAnt)
+4
source

I would use TeamCity as a continuous integration server - it is easy to use and install and can run NAnt, MSBuid, etc.

If you plan to use NUnit, make sure that you have a way to run your tests from the IDE - eith TestDriven.NET or Resharper / CodeRush.

You can use Spring.NET or StructureMap for IoC (although any other framework will be fine).

+1
source

Surprisingly different, our current stack:

  • StructureMap for IoC
  • We performed our own ORM
  • MbUnit and Moq for unit testing
  • MSBuild for assembly
  • Gallio Icarus / Visual Studio tester to run unit tests
  • TeamCity for CI
  • FxCop / StyleCop for code quality
+1
source

Visual Studio 2010 Ultimate with TFS and TFS Build.

This covers all areas that you list (and much more). If we need more (for example, for IoC), then we will consider other tools (the first one will be for ridicule, in which VS will not directly turn on, and then, probably, Moq (but some time has passed since I used that which is good in this area)).

0
source

More articles:


All Articles