DISQUS

Thanks, missed that. I have posted to the dev list, so we'll see.

Thanks, I wish I have seen it before.
It is almost the same solution I am providing, but without the support for IEnumerable/IList/ICollection dependencies.
There is still a question why it is not in Castle itself.

Jeff, I am sorry for having bashed MbUnit, but for me this post was about common deficiencies, and MbUnit was only an example, since I use it every day.

Andrey, have you tried [assembly: InternalsVisibleTo(RhinoMocks.StrongName)]?

Thank you, Jeff. I know that I could have asked you directly instead of blogging it, but I wanted to stress the importance of solving these things by default.

As for Gallio, I'll enjoy working with it when it's out, but it is not here yet. So, since I wanted to extend a stable version, I haven't looked deep into Gallio.

Thanks, it solves the problem at hand.

Thanks! Could you please give me your email?
Mine is ashmind+blog(at)gmail.com.

Thanks for your interest.

I've just put it on the Google Code
http://code.google.com/p/ashmind-web-ui/
and I've fixed the AlternatingItemTemplate.

You can download and try the latest version.

Yes, I have seen a post on a similar problem with LINQ.
Type inference has its limits.

Yes, of course.

I completely agree with you on user tests.
But what I was writing this time was closer to JS unit tests — something like "changing the selected value in a combo box should change some property of a global object on the page".

Basically I wanted to fix fragility of my javascript and didn't want to do it with more javascript. Even if WatiN would have to call up the browser for each test fixture.

I have read some sources myself, and you are correct. HTML does not want to think of itself as XHTML unless served as application/xhtml. And HTML does not want unknown tags.

But, formally, if I set doctype to xhtml, I feel my right to push in any tags if they have correct (xmlns declared) namespaces. And browsers behave as if I am right.

The only problem with this is that IE requires xmlns on html tag, and that means that my content can not be embedded without an iframe (which is not a solution). I am still figuring out the solution for this problem.

I understood that point, but did you have any problems viewing my blog? The highlighting in the previous post was done by a bunch of random XML tags styled with CSS.

All three browsers that I have at home (IE7, Firefox and Opera 9.20) handle them just fine.