What OSS software should I use for enterprise software?

Question

Summary: OSS Technologies that fit with MS C#, Dot Net, and VS enterprise development.

I am not trying to be subjective. I need a finite list of MS C# specific enterprise practices with matching OSS software titles that work with MS MVC (outlined below). From there I can review and setup a "hobbie kit" installer for my dev team. I want to consider refined and proven OSS software titles, and how they are a good match with C# and Dot Net, along with a list of TLAs we should consider.

• Environment: MS Windows and MS Visual Studio Professional. JetBrains ReSharper too?
• Project type: MVC
• ORM: NHibernate (EF infant? Linq to SQL is no ORM, but is easy to use and stable. iBattis, Subsonic?)
• Testing: NUnit and Moq (Standard installer for the templates?) Rhino Mocks?
• Ajax: jQuery (MS Ajax 4?)
• Subversion: TortoiseSVN
• Client side data validators? xVal validation?
• Code generation? very shaky on this. Does this relate to client side templates (jTemplates)?
• Data: Lazy List (iterator pattern?) How best to bind data using MVC, JSON, and jQuery?
• Missing anything? What replacements are there for the various server side controls we lose in MVC? FlexiGrid for GridView?

I have always stuck with MS apps, but many OSS projects designed around java fit well with non-java based development. Mono has really opened up the use of Dot Net on *nix, so this question is really relevant.

JohnnyCoder website, Phil Haack's blog, Elijah Manor's video, and Stephen Walter's videos are just a few extremely helpful sources.

Thanks for the links and the feedback. Sorry for any redundancy, but I have not seen this collection together as a whole yet. Feel free to leave links from other questions. It would be helpful to link "premade" installers for these things, like the "standard installer" for NUnit and Moq linked above. For that matter, I think one of the MS juggernauts should take this material and make a screencast video of it (Stephen Walter probably already did this. :-)

Thank you so much.

Answer 1

We are using the following tools and libraries in our large enterprise software product:

• Visual Studio
• Team System
• WCF
• MSTest
• NHibernate
• RhinoMocks
• log4net

And a few others you're probably not interested in. I think it is a very good choice, but the following products are also valuable alternatives:

• Subversion and Tortoise instead of Team System
• NUnit or MbUnit instead of MSTest
• Moq instead of RhinoMocks

One advantage of any OSS product is that you can use it without asking your boss for money. So you can try them and you don't have to prove that it is worth the money. With the given OSS alternatives (Subversion, NUnit, MbUnit), I don't see any disadvantages using them.

Edit: Forgot to mention Spring.Net for IoC, which is also important in a large software product.