So my blog software was pretty much fleshed out.  I could write posts, have tags, have a calendar of posts, an archive links.  Multiple blogs, mutliple blog writters per blog, File uploads, WYSIWYG text editing.  All in all I was pretty pleased. Now though I was starting to get into personalizing my blog with some controls that only I may care about.  Since I'd like to share this software with others and let them use it I thought it would be better if I made these features

Okay so I had found a way to do MVC plugins, but it didn't work in my environment.  So now what do I do? Well I still wanted to work in the MVC framework somehow.  Maybe not for showing my plugin control, but I did want to somehow handle form submissions cleanly.  Mainly for administering my control (configuring it as neccessary).  So what did I do? Well I went back to the way I've done plugin architectures in the past.  I defined an interface that would get us

So I had my infrastructure in place for allowing plugins on this blog, now I wanted to add some sort of storage mechanism for those controls. My first thought was they could just connect to the database and add tables themselves, but there were a few things I didn't like about that. I wanted the blog site to just grab the plugin and be able to immediately use it.  However that would require allowing the control to add tables to the database.  Which means I'm writing code that uses a c

When I first launched this blog I found I was frequently getting the following error. Object reference not set to an instance of an object. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.Source Error: An unhandled exception was generated