Download
How to Install? – How to Upgrade?

Release news

7. December 2007 Team BlogEngine.NET 1.2 9 comments

We’re had a change of plans and have decided to hold off a few weeks on the next release of BlogEngine.NET.  While we initially wanted to make more of a patch release, we’ve kept adding more and more into it.  The new features need time for perfecting and really more than anything, we want another solid release.

However, since we are taking extra time and packing it full of features, we’re going to make the next release 1.3.  Here is a sampling of what to look forward to in BlogEngine.NET 1.3:

  • Full mono support (right out of the box)
  • Updated Metaweblog API including support for creating/editing pages in WLW.
  • Improved Blog importer/exporter, including support for easily switching between XML and SQL backends
  • New extension manager to managing extensions and their settings.
  • New events for extension writers
  • Support for mobile devices
  • New themes

Version 1.3 will be released before Christmas 2007.  As soon as we feel it is ready, we'll release it for the world.  In the meantime, if you can't possibly wait another day, you're welcome to try the latest build from CodePlex and let us know if you experience any issues.  The more testing we have, the better the release will be.


Tags : ,

Comments (9) -

  • Troy Goode

    12/8/2007 5:32:10 AM |

    Thanks for the update Mads. With this and the MVC Framework delay, today is a bit of a dissapointment .Net developers. It sounds like it is for the best though, and I am looking forward to all the new features you are baking into 1.3.

  • Mohamed Tanna

    12/8/2007 8:12:27 PM |

    what about slug ?

  • James Skemp

    12/10/2007 4:19:44 AM |

    As someone who's built themes in the past (and wishes he had time to build some more), any chance we can expect a 'template' theme we can use to build new, or modify existing, themes?

    Ideally, it would contain every possible element, with no CSS applied (the CSS file itself would contain all of the classes and ids, with no styles).

    Right now I'm grabbing the default theme and doing a compare from version to version (care of WinMerge). It works, but it seems that there should be a better way, especially since it doesn't contain all of the elements (and I have to do compares on some of the other themes to see what other elements there are, and what was changed).

    Of course, this wouldn't make the theme real usable outside of theme creation, but I definitely think it would be a great help. I've been tempted to work on this project myself, but it seems as though this should really come from the official BE team.

  • guest

    12/10/2007 4:48:15 PM |

    Great news

  • Tamilar

    12/11/2007 1:53:10 PM |

    Looking forward for the 'Christmas' present... Smile

  • Robert Bullock

    12/12/2007 1:50:53 AM |

    Thanks again for this awesome app! Also, I pledge to get involved with this project in the New Year after I leave my full-time gig... I really think this is one of the best asp.net open source projects out there, right up there with Subsonic. I'd love to be a part of it, but time isn't there right now.

  • Milad

    12/13/2007 11:46:51 AM |

    Hi!
    Would u plz add some documentation about safe-upgrading from earlier versions?!

  • breakstring

    12/17/2007 6:06:56 PM |

    In release 1.2, the user A can update/delete the post of user B. I think it's realy not good for a multi author blog.
    Is there any changes in 1.3?

  • Mads Kristensen

    12/17/2007 6:18:02 PM |

    Yes there is. An Administrator can delete anything, but editors can only modify and delete their own posts.

Comments are closed