A couple of weeks ago I blogged about the new ‘Provider Design Pattern‘ being introduced in ASP.NET “Whidbey”. In summary, the provider design pattern allows for a pluggable data abstraction layer / business logic layer which allows for built in functionality of ASP.NET to be easily replaced.
We plan on shipping several providers with ASP.NET “Whidbey” supporting SQL Server, Authorization Manager, and several others. However, we also want to build source-code samples for other systems. Specifically: Oracle, DB2, LDAP, and MySQL.
Today I sat down to start working on an Oracle Membership provider and realized: a.) I have not used Oracle in about 6 years, b.) there are lot’s of people that would likely be interested in helping – and who probably know Oracle better than me!
I’ve created a new workspaces project on GotDotNet called ‘ASP.NET “Whidbey“ Providers‘. It’s private for now, but within the coming weeks we’ll open it up for membership (I’m going to see if I can get some filtered design specs. to help the creative process).
It would be great to start working on some providers for ASP.NET “Whidbey“, the only caveat being that there will be some changes between the current Alpha and the upcoming Beta – specifically that we’re moving to abstract base classes vs. interfaces (which we require now).
To begin with it would be great to start on Oracle providers for the current alpha. If you are interested – and already have a copy of “Whidbey“ and know Oracle, please:
1. Join the workspace
2. Send me an email with the username you joined the workspaces as and I’ll add you.
