Unit Testing ASP.NET? ASP.NET unit testing has never been this easy.
Typemock is launching a new product for ASP.NET developers – the ASP.NET Bundle - and for the launch will be giving out FREE licenses to bloggers and their readers.
The ASP.NET Bundle is the ultimate ASP.NET unit testing solution, and offers both Typemock Isolator, a unit test tool and Ivonna, the Isolator add-on for ASP.NET unit testing, for a bargain price.
In my previous blog about domain objects and contracts for those, I have described the situation where the team was thinking in a different way than myself, and what we tried. I have never blogged back about the fact that the team got convinced that this is not a good practice, and long time ago we stopped doing that. Today I spotted a blog post from James Gregory where he names it properly “an anti-pattern”. That’s what it is. End of the story.
Seeing is believing. I was looking for a Hudson plugins that would allow me to present any TODOs left in the code. And as usual, found it (love that!). Static Code Analysis Plugins are useful when you need that type of information. In particular, I am talking about Task Scanner Plugin. The snapshot will tell everything.
I had an old post, back in July 2008, where I had a few comments on Data Driven vs. Domain Driven applications. It will be almost a year soon since that post, and I have definitely learned a lot since then. One thing I learned for sure, is to pick your the battles. You cannot fight a developer who knows data driven applications since day one and nothing else, that domain driven applications are not necessarily more ‘efficient’, but more maintainable, allow better link between domain concept and software, allow change, pass the reality tests when change in business is coming. It’s the same as trying to convince someone who spent 2/3 of his career without testing and sees no value in it, suddenly to start TDD or even ‘worse’, BDD. Why to bother? I know my stuff well, don’t I? Look, XX years in the industry are not wasted. No, they are invested with a little ROI. But these are religious wars. Useless. Therefore I am off the topic, and just learning, exploring, and implementing things I see the right way at the given moment. Once you concentrate on doing that rather than chasing ghosts to convince, you realize what is right and what is wrong, without a need in side-kicks.
Anyone who’s doing TDD is familiar with the CategoryAttribute coming with the most of frameworks. Today (I am surprised it took us so long!) we got read of
I have a deep respect to people writing books. Not only it’s a commitment, but a hard work that may not be appreciated, despite all the efforts invested into creation of a such. Saying that, some books are just not as good as the hype around them. Unfortunately, I found “xUnit Test Patterns” by Gerard Meszaros not very pleasant for reading…
Do not misunderstand me - the book has a lot of knowledge and practical experience behind it. I am absolutely sure that the author knows very well what he wrote about. The problem I found with the book was the way it laid out and presented. And in particular:
This post is political.
I am just glad that along with Israel, Canada and US did not take part in this pre-arranged “show”. Boy oh boy, an international conference masqueraded with good intentions, and leading to the same old thing - hatred for Jews and state of Israel. Now ask the question yourself: do you trust UN and everything you hear? Cause I wouldn’t.
Some countries representatives have left in order to boycott the speech, and this is where I am not sure if that was in solidarity to what was done to Israel, or because they felt attacked. Either way, I hope they will open their eyes, and stop participating ahead.
I was exposed to Domain-Driven Design not that much time ago. Prior to that, I was struggling with the object-relational impedance mismatch while developing objects based applications. First attempt to get relational database close to the applications I was writing was an uneducated experiment to “wrap” the data into objects. The reason I think of this now as “uneducated” decision, is because I knew nothing about proper object relational mappers, neither had sufficient knowledge about patterns such as Identity, Unit of Work, Repository, etc.
FluentNHibernate is an amazingly nice DSL to use for quick NHibernate mapping implementation. Today I had to refactor some of the code we did at work, in order to persist a state of an object. The original code was implemented using State pattern, which allows simple division of responsibility and easy decision making at each given step. I have decided to create a simple example of State pattern persisted with FluentNHibernate in order to demonstrate how powerful it is and what kind of freedom it can give to developers.
I have started to read a new book about OODB. The reason I decided to get the book and go through it is because I am SICK of the traditional RDBMS and the way it forces us to go through loops and hoops to create domain driven applications.
The very first question to popup - what’s the practicality? Don’t know, but I know the truth is out there. And it doesn’t have a shape of conventional databases.
