This is a follow-up on my previous post.

I wanted to see how the 3 browsers I use the most rank regarding their current support for web standards. I ran the popular Acid3 test on the latest versions available for download of Chrome, Firefox and IE. 

These are the results I got.....

I want to start by saying that I’m not Google fan boy and the only Google product I use apart from Chrome is, of course, Google search (I also tried to give Bing a change but couldn’t use it for more than one hour, I guess I’ll have to try again).

Two days ago I tried to deploy to a production environment a WCF service and got the following error:
 
System.ServiceModel.EndpointNotFoundException
There was no channel actively listening at 'http://somehostnameIdidntrecognize.local/services/myservice.svc'. This is often caused by an incorrect address URI. Ensure that the address to which the message is sent matches an address on which a service is listening.

I've noticed that some voices in the .Net community are jumping into the NoSQL wagon and trying to get as much people aboard as possible. I see posts regarding NoSQL getting more and more frequent; see here and here for example.

I have the following confession to make:

I stumbled upon this excellent article written by Scott Haselman: Creating an OData API for StackOverflow including XML and JSON in 30 minutes.

I, like many developers, spend so much time "handcrafting" my solutions that reading about how easy is to create an OData service using the new versions of .NET and Visual Studio was really refreshing and pleasantly surprising.

For the last two weeks I've had the opportunity to work on a project which uses Entity Framework (EF) ver. 1.0. For more than a year I've been reading complains, reviews and comparisons regarding EF but finally after using it I have my own opinion:

• It's not a mature solution.
• Definitely falls short when compared to other products in the same category, like NHibernate for example.
• It's not as bad as some people want to make it appear.
• Can help some teams deliver small projects on time, especially if the developers have no experience on the use of O/R mapping tools or if like in the project I was working on, most of the business logic was implemented on the database side.

There are plenty of good Dependency Injection Container implementations out there. The selection of an IoC container is not only defined by the developer's preference, which can swing the vote big time since most developers swear by their favorite container, but also of other factors like standards in the organization, the usage of another product which already supports, or favors, a given IoC implementation, etc.

The usage of an IoC container should always be abstracted, making the process of switching between implementations fairly simple, or at least, the refactoring needed to accomplish this task will be minimal compared to the one needed if you were using references to a specific container all over your codebase.

I'm not a fan of meta posting but this information was so valuable to me that I wanted to keep track of it on my blog just in case something happens to the original article.

If you are one of the unlucky few (I would like to think there are no many of us) still using Visual Source Safe in 2010, then I bet that you've needed to get a version of your project at a given point in time. It happened to me today again and instead of setting with the "Sorry, SS doesn't support that" I set up to find a solution.

I found an old post by Brennan Stehling with the exact instructions to get a point in time snapshot using Visual Source Safe or using Brennan words: Get by date.

This post from Uncle Bob generated lots of talking on the developer community regarding Inversion of Control (IoC) and Dependency Injection (DI), which is always good for the sake of  learning and general awarness. Almost every developer with a blog posted about their take on this subject. Two people which I respect a great deal and suscribe to their blogs also posted their reactions, please read Ayende and Davy's blogs for a better understanding of their positions.

What I get from all this, in short, is that Uncle Bob accepts the advantages of using dependency injection but prefers to encapsulate the access to the IoC container on factories. Davy seems to accept this approach on another post...

Today, when writing a function that opens an image, adds a simple text on the top corner and streams the resulting image to the client I noticed that the original image used as template couldn't be renamed or deleted after the code ran for the first time and for as long as the web application remained running. Restarting the web application makes the problem to go away until of course the offending code runs again.