But why is it now different from BlogEngine.NET 1.5.1.46?

I downloaded it yesterday and Diffed to find out what I need to change to keep up…and it was the “version number.”

So, I guess keeping up with several code changes over the past few months and making sure my version of the Multi-blog capable SqlBlogProvider was in tune paid off, only to realize I’m still one of the very few to implement such a “clean” version of multiblog BlogEngine.NET.  I’ve been working on an Entity Framework provider since this could replace or certainly enhance the capabilities of BlogEngine, but it may really be just another stepping stone to work out a new architecture to support BlogEngine Like capabilities for .NET 4.0 and IIS 7 using MVC, Entity Framework and perhaps WCF for integration and remote administration capabilities.

At least I’m learning a lot about Open Source capabilities and limitations. Does anyone want to legitimately tackle a Next Gen BlogEngine with me?  Of course, I would not want to steal the branding created here unless there is a parallel effort to create a distinctly separate single Blog, Multi-user system such as BlogEngine.NET and a more scalable, database centric, multi-blog, real-time administration console application.

Design first, Agile methodology, Eat-your-own-dog-food approach with lots of prototyping.

Or I could just use BeerHouse or DotNetNuke, I guess.  Need to go get some additional experience.

See Y’all l8r,

Dave (BizTron)

BlogEngine.NET Core Version 1.5.1.31 is running on this server as of this Post.

ref: (Waiting for a Minor Release of BlogEngine.NET with MultiBlog)

 

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 three 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:

• Get the latest BlogEngine.NET code and use it as a baseline. (1.5.1.31)
• Get the latest SqlBlogProvider code and ditto. (27978)
• Make sure to upgrade Everything to .NET 3.5
• Modify the SQL Database Schema to include Blog and Host tables, and BlogDataStoreSettings
• and add BlogId columns where necessary.
• Recreate the DBML for the new schema.
• remove references to multiblog="true" because they don’t matter anymore.
• Simplify and verify.

OK, done!!!  Now what?

I have a set of Blogs running an older version of everything and now I have a new schema.  Also, I have new capabilities and only a SQL script to modify or add new blogs.  It is simple but always required modifications before running.

• Windows Form, new simple DBML for required tables…because the Provider model is too complex,
• and Done.

Oh, and I needed a migration tool and some more fun with Linq to SQL, so I created a one-off migration tool with a useless UI that couple be done from a command line, but I thought I might need more.

And, it’s running now!!!

BlogEngine.NET code is now at version 1.5.1.39 (change set 31351)

Now I have to isolate changes, bug fixes, enhancements I want and implement…but this is the exact scenario I want to avoid.

• Do I create a Branch that uses most of BlogEngine.NET?
• Should I start over?

I think the best option is to start a new core based on current or future technology and leave behind what can be upgraded.  Linq, Entity Framework, WCF, Silverlight 4, .NET 4.0 can be used much more.  MVC can become a solid base for the UI, maybe. This is not a hard nut to crack, and get’s easier with time and new technology.  The hardest part about using BlogEngine.NET today is that it takes longer to fix than to build again from scratch.

It’s time for a new architecture.  I’m glad I didn’t create one myself a few years ago when BlogEngine.NET was introduced, but I will be happy when I can safely deploy a new version based on those principles.

Please support my technical-development community support initiative and send checks for any amount to help offset the cost of my next “ergonomic” workstation. You KNOW I’ll support the community MUCH better with this in my office. :)

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.  1.5.1.22 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

More...

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.More...

For anyone who recently noticed issues with Twitter on several fronts, you’ll want to read this.  I’m not sure if it’s made the rounds on TV news yet but it answered some questions and caused some concern.  It’s always blissful until someone slams the door in your face, or cut’s you off on the road, flips you off, etc.  No idea why this would happen, but it did.  Now we all need to BOTH find ways of keeping these things from happening, within reason, and to prosecute and slam the door on those idiots who do this for fun, revenge, or terrorism.

App developers stung by Twitter's DOS woes

I received this message from Andrew Badera:

LinkedIn

MESSAGES

Andrew Badera wrote:

Though I think Computerworld took a slightly more negative spin to my input than my email really conveyed (in) toto, this is a decent look at the Twitter DDoS situation from the perspective of Twitter app developers like myself.

App developers stung by Twitter's DOS woes

Computerworld | August 07, 2009 | 06:04 PM PDT

Developers who built applications for Twitter and generate money from them have been hard-hit by the micro-blogging service's many hours of downtime in the past day, as hackers pummel Twitter with an ongoing denial-of-service attack