One thing which is overlooked is that the license for MVC, unlike ASP.NET, states that you can't run the code on Linux machine. So if you want to use Mono you have a problem with MVC.

NUnit isn't bad but MbUnit does support a few things better. There is even an old CodeProject article about an early version of MbUnit which explains the differences. Regarding the VS 2008 - firstly you have to use the team version and secondly I have heard only bad things about it. No one working with it seems to like it.

I've forgot that possibility. Can one combine this approach with manual testing?

When is using Debug.Assert() recommended? I do check my parameters but I throw exceptions here. Do methods using the conditional attribute survive the compilation even if the symbol isn't supplied there? If not it seems that one has to provide for libraries two versions.

I've been wondering which framework is the best to use on a green-field project. I know NUnit and MbUnit and noticed that MbUnit is better than NUnit, but I don't have any experience with xUnit.net. I have seen the controversial xUnit.net has caused with its introduction but so far I haven't found a review how it does really compare to the mature competition. It seems that only people with negative opinions about the xUnit.net design blogged about it without actually using xUnit.net. So does xUnit.net fall short from its promises? Are the perceived flaws it supposedly fixes real? Is there another framework I should look into before I'll stay with MbUnit?

Will do so. Thanks for the clarification!

I have to convert some Java code to C# and I've stumbled over the Error class. I have been told already that the use of Error instead of Exception allows to bypass catch-clauses for all Exceptions. Now C# doesn't have a direct equivalent to Error, AFAIK. Also at the place of the Error the internal state of the program is corrupted, so abortion makes sense. Am I supposed to use the Exception or even InvalidOperationException then?

Fernando A. Gomez F. wrote:

I... couldn't say. I'm still stucked with C# 2.0, and haven't had the chance to look to C# 3.

Anonymous functions have been introduced in C# 2.0, as well generics and partial types. Looks to me that you aren't quite uptodate with the evolution of C# as you thought originally.

Fernando A. Gomez F. wrote:

Christian Graus wrote: The C# team says they are aiming to make the language as easy as possible, which is the exact opposite of the goal of the C++ team ( make it as powerful as it can be ). That's why I don't like C#. IMO they are creating a monster with the language. As an example, do the yeild return thing adds power? No. But it makes it easy. It reminds me of all this keywords they added to VB6 (not comparing both languages though). They are just making it fancier, instead of giving power to the programmer.

What about anonymous functions and LINQ? Those do give more power, don't they?

Then you haven't used Foxit to copy text from PDFs to other applications. The text in the Ecma 334 PDF must be sorted into the correct order and PDFs from Pragmatic Programmers lose all the spaces between the words. Or the bookmarks don't show chapter numbers. These are the little things for which Adobe had years to perfect. The only hope is that Foxit works on those problems or being only faster won't help them in the long run.