I based my implementation on SqlBlogProvider, but since it was out of synch with BlogEngine.NET I had a dilemma. My biggest complaint about BlogEngine.NET if I had any at all was the fact that sometimes changes come at a snails pace. This is not to say that you can't find a new build there every other day, but that the major enhancements I want don't always take, or in the case of MultiBlogs, the most popular enhancement to date, is completely ignored. Once Jacob Proffitt created a solution, I figured it would be rolled into BlogEngine.NET. OK, so I was Way off on this one. So here's a strategy: ...

Pipedream: Multiple Blogs I’m not sure if anyone else has noticed but the NUMBER ONE requested feature of BlogEngine.NET (That’s #1 by a landslide) is to support Multiple Blogs per installation. I have been struggling with this concept and while searching for and designing a workaround using BlogEngine.NET and the Provider model using SQL Server only, I came across SqlBlogProvider that also uses Linq to SQL. This model supports Multiple Blogs in a single SQL Server Database in a single Application folder. It now also supports multiple hosts or domains per blog if required. So the only dilemma I’m struggling with today is where to go from here...

This is what you see when attempting to rate a new post. Click on a Star to rate the post. Notice the infinitesimally small rating that is generally added when creating a first post. This may be something I did myself while trying to “fix” the Add a new Blog script.

When developing multi-tiered applications, it's not uncommon that to encounter code and architectural "noise" where a developer is forced to shift languages between the business logic layer and the data layer. The preference of many developers is the use of tools (typically Object Relational Mapping solutions) to abstract the database-specific aspects of the data layer into objects usable by the upper layers by object-oriented programming languages.