No problems, implementing was pretty straightforward.
We wanted to write the provider in a separate assembly but a few entity classes were internal, also we needed all entities to be marked Serializable. Instead we forked and added our provider directly to the blogengine.core assembly.
a short blog entry about the provider including some links to the fork.
Not sure about what happens next... Here are some alternative paths:
- Nothing. The fork lives on independently.
- We create a pull request and our provider ships with the blogengine core assembly.
- We maintain the provider in a separate project and create a pull request with necessary changes to the core.
The second alternative would be awesome and I could commit to maintaining the provider. I feel it's up to us to show what kind of value our provider creates before you guys can commit to the extra maintenance involved.
So I think the third alternative is the best choice, at least for now. What do you think?