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?

If we don't know the future plans, dates, implementation, etc., we're stuck deciding whether to wait or risk going forward with an alternative branch and missing out.  Communication would be good.  I may be missing something.  I've stated recently that I spend more time modifying current BE.NET code than I ever do Blogging and I have over a dozen blogs. is currently stable, from my perspective with SqlBlogProvider supporting all of those blogs on a single folder, with a single SQL database and schema.  The only (minor) issue is still creating multiple Web Applications and pointing them to the same folder.  I can live with that on an 8-way server with 2 GB of RAM.

It’s related to Multiple blogs in one BlogEngine.NET instance and BlogEngine.Net for SQL Server

The concern here is complex, balancing need, want and political correctness.  But it doesn’t need to be this way.  I’m more afraid of pissing-off the folks who have put so much into this project than I am of whether or not I can build a system from scratch so I don’t want to say what I’m thinking.  Hey, if I had the time, or could work with “you folks” I’d want to contribute towards a cleaner architecture, test methods (not that I’m the expert in that), and MVC version, even contribute the Oracle portion of data model and db provider.  But overall, I’d like to see a plan.  I’m most concerned about waiting for people who are deciding on things without customers’ input, frankly because we aren’t customers.  Nobody’s paying for this.  So, you get what you pay for, right?!?!  Not quite.  There’s an incredible value in this product, and for the developer in us, there’s even room for learning by fixing, altering and improving.

The point is, I feel useless in the process and could contribute substantially to the process.  I’d hate to say BlogEngine.NET needs “new” blood, because I think it just needs more time, as in planning and development effort.

If anyone is interested in contributing to this effort, but has been shut out, let me know if you want to go down the branch path together.  I’m not against trying something and dropping it in the future for the right reasons or sticking with it if it adds even incremental value, or for that matter, starting from a completely different approach.

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.



These are the symptoms I could find so far, but I cannot isolate the DateTime property that is causing the Exception.

Line number (approximate:)


SqlTypeException without enough detail for me to locate the offending data point.  What am I missing?


For more information on this Project:  I will update this post when a resolution is found.

Update (10/17/2009)

BlogEngine.NET appears to be closer than ever to a Multi-Blog implementation thanks to work done by Jacob Proffitt found here: Multi-blog Obsession.  The SQLBlogProvider allows multiple blogs to be supported by a single SQL Server database.  Imaging the maintenance and resource requirements, compared with “n” blogs and “n” databases, or “n” folders with “n-times-x” xml files for all those posts.  Currently, this provides for a single folder and any number of application instances, all pointing at the same folder.  There may be a few potential answers to this, but only if someone deems it a problem.  I’m now running about 12 (BlogEngine.NET) blogs in a single location with a single database using the SQLBlogProvider.  A few details were worked out to bring this solution up to the 1.5.x version of BlogEngine.NET.  While looking at this, I’ve learned a lot about some new features and found some useful and straightforward applications of Linq to SQL.

Future support

If the BlogEngine.NET team comes to roll this solution to the Multi-blog “request” into the core solution, it may need a few tweaks.  I’m not sure which ones may or may not be important to everyone but I’ll try to innumerate the issues I see here:

  • “ONLY” SQL Server support due to Linq to SQL dependency
    • I don’t see this as a problem since I wanted this solution myself, however Linq to Entity or other patterns could certainly be employed for other frameworks or architectures.
  • Multiple blogs require multiple IIS Applications
    • This may be due to BlogEngine.NET core dependencies so it may not be reasonably addressed in the near future.  This one item would make sense to “Fix” for me because it would make an already easily maintained multi-blog approach an order of magnitude easier still.
  • System Resources still grow due to the way BlogEngine.NET loads blog data into lists for performance reasons
    • Again this is a core BlogEngine.NET issue for multi-blogging.  Not necessarily an urgent matter, but a sizeable problem for many blogs running in a limited environment.  Throttling could become necessary.
  • Each host site depends on host header or specific domain name to define a unique blog
    • There may be a some simple answer to this so I’ll try to provide any findings when I’m done testing some of my theories.
  • No UI for adding or “maintaining” each new blog
    • Not a difficult problem to solve.
  • Extensions, including Widgets, are not yet configured per blog.
    • This only matters for configuration of Extensions that are blog specific.  There should be a default setting for every Extension, but also a means for specifying, at least, blog specific settings for certain blogs.
    • Widget Zone should also be configured and styled per blog.  I would like to have Text Widgets displaying things like Author information that does not conflict with other blogs.
  • Several bugs still exist and should be tracked down and corrected.
    • Again, not difficult.  Something that will require time and testing.

I’m extremely happy with the results to date but I still consider this a Beta test of the latest BlogEngine.NET source merged with the latest SQLBlogProvider source, plus some merge code of my own.  I’m running on a 1and1 VPS solution so everyone can give it a try.