This one is simple to use. The original version can be found at: (Creating a XBox 360 Widget.) I just wanted to update it for my own needs, and so that it would run with current BlogEngine.NET Core. This is what it looks like…

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 a thread from BlogEngine.NET on CodePlex. (Multiple blogs on same installation) I would like to see the current dev plan, if it exists yet. If I knew we/they/you were going to use SqlBlogProvider, and even integrate it into the core, I would like to help. If there was also a way to allow multiple blogs within a single application, that would be great too. Should everyone just create a new branch?

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.