How to change your BlogEngine.NET backend

paths Many moons ago, I asked for some testers for my BlogEngine.NET Provider Migration tool and I’m finally getting back to everyone with a tool you can use to move your BlogEngine data from one backend to another.  If you’ve been using XML and wish you could start using VistaDB, SQLite, SQL Server, or even MySQL, this is your chance.  If you started with a database and wanted to get back to XML, this tool should be able to help you too.  Lastly, if you are a database such as SQL Server and wanted to go the simplicity of SQLite, this process can likely help you as well.

The process is simple.  You configure the new provider you’d like to use.  The tool will copy most of your blog data from your current provider to another provider you select.  Once it is finished, you change your default provider in your web.config.  The process will leave your current data in place after it makes the copy so you will still have it in case something isn’t right.

You might have noticed I wrote “most of your blog data” above.  This is because the tool only transfers your blog posts, pages, settings, and ping services.  Widget data, extension data, and user data is not dealt with.  If you are transferring your membership and roles at the same time, you’ll need to set up your users and passwords again.

Full details on my Provider Migration Instructions and Tool page.  Good luck switching over.

Link: BlogEngine.NET Provider Migration Instructions and Tool

Comments

12/9/2008 3:47:50 PM #

Janko

And I was wondering what should I do to migrate to SQL Server when I change my hosting Smile Thanks!

Janko Serbia |

12/14/2008 7:07:29 AM #

mr.boss

hey man you site is cool  , i learn many things here .

mr.boss Spain |

12/16/2008 8:45:15 AM #

Talal

Worked perfectly
Thanks allot man, I really want to move to sql long time ago.

Talal Saudi Arabia |

12/17/2008 11:40:47 PM #

Joshu Folkerts

nice work on the site.

Joshu Folkerts United States |

1/5/2009 11:38:11 AM #

kelsey

Hey Al,

first off, thanks for your contributions to the .NET and blogengine worlds. I really appreciate you sharing your knowledge.

I have done the XML to VistaDB (Express) migration path. Everything went beautifully until I went live with it. I should have tried this in a test directory on my web hosting provider's server, but alas I didn't. The problem I get is

Could not load file or assembly 'VistaDB.NET20, Version=3.3.1.54, Culture=neutral, PublicKeyToken=dfc935afe2125461' or one of its dependencies. The module was expected to contain an assembly manifest.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'VistaDB.NET20, Version=3.3.1.54, Culture=neutral, PublicKeyToken=dfc935afe2125461' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



My configs and DLLs on the dev machine and the prod machine are exactly the same. Do I have to register the VistaDB dll in the GAC or something?

Any help would be appreciated.

Thanks.

kelsey United States |

1/5/2009 12:28:52 PM #

kelsey

re: my prior post. I should add that I am running blogengine version 1.4.5.0.

Thanks again.

-k

kelsey United States |

Comments are closed
Recent Comments