Running DotNetNuke on MySQL

There was a recent post by a member asking why we have a Firebird  provider project and not a MySQL provider project.

The Core DOES want a MySQL provider and I have been tasked with helping bring that about.

I haven't "put the word out" yet because I was waiting for the Firebird provider to be finished because I was hoping we could borrow code from it. You see the "big issue" with creating a provider is handling the membership provider. The current DotNetNuke membership provider is Microsoft's membership provider and it works with SQL server. Sanjay Mehrotra created code to make it work with Oracle and he is using the same code for the Firebird project.

Sanjay's code is the key that got the Firebird provider off the ground.

However, there are changes coming with DNN 4.1/3.1 to the membership provider. We are "un-coupling" DotNetNuke from the Microsoft membership provider and making a layer that sits above it that should make creating a alternate membership provider easier. That may mean that there wont be much code to borrow so we should just move ahead.

So my current plan is to wait for DNN 4.1/3.1 and then "put the word out" that we are looking to form a MySQL team.