Friday, November 12, 2004 - Posts
I've heard a lot about MockObjects and I just came across this article dealing with the topic. Unfortunately I still dont understand what the heck they are and how to use them.
The sample given in the article doesnt make any sense to me since there is no explanation of what the author actually wanted to test and what he would have done in the absence of mock objects.
It also appears that some other readers of the article couldnt even get the code to compile, so I'm not alone in this.
Can anyone point out some really good links to understand this concept?.
Hoping for some good pointers.
Well, it was supposed to be out on Nov 1st but there must have been some last minute hurdles. It would be good to have some news. I read the article from Nina with the details of DNN 3.0 and it appears that its really going to rock. So I'm waiting eagerly.
Update: Looks like today is a day of posting and immediately updating. I found another post dealing with the DNN delay which linked to this post by Shaun Walker. The post also explains a great deal about the new features expected in the release. Its looking better and better.
I'm sure we can all wait for the product to be released. Its better to get our hands on a stable one with rich features than a buggy one because some people demanded it.
Actually that was the same comment (ie) that its better to wait for a big stable release, that someone in Microsoft raised about the Yukon delay, but the Longhorn excuses about the chop of WinFS from the client OS in 2006 is exactly the opposite (some rubbish about clients demanding ease of deployment and new OS features and all that). Looks like the departments inside MS cant agree on a common approach to these issues. Never mind.
Is it only me or are other bloggers here on DotNetJunkies facing feedback with advertisements for casinos and little blue pills? Its getting very annoying. Thankfully the emailing feature here which informs us about posts works fine, else I would find the site rife with spam.
Is there no end to this menace? Should we look at implementing feedback control posts watching for iillegal words or is that feature already available or, still, would it make it difficult for genuine feedback?
Update: No sooner had I posted this than I found Scott Hanselmann's post dealing with a dasbBlog solution to help rid blogs of spam. Dont know if .Text has this included, but it would be a worthwhile addition to the code base.
Update-2 : Now I've also found something from Stefano Demiliani on the subject. Good to see that some momentum is building around possible solutions to this menace.