This post originated from an RSS feed registered with .NET Buzz by Scott Watermasysk. Original Post: Microsoft ASP.NET v1.1 Member Management Component Prototype Feed Title: ScottW's ASP.NET WebLog Feed URL: /error.aspx?aspxerrorpath=/blog/rss.aspx Feed Description: ASP.NET and Blogging Latest .NET Buzz Posts Latest .NET Buzz Posts by Scott Watermasysk Latest Posts From ScottW's ASP.NET WebLog

The Community Server membership, roles, and profile system have been built on a version of the Whidbey provider API's. Today,  the ASP.NET team, has announced their release to the public.

The functionality provided by this component is a preliminary version of the Membership, Roles, and Profile functionality coming in ASP.NET 2.0 and will change in the final release of ASP.NET 2.0. This means that any ASP.NET v1.1 applications you develop using this component will need to be updated when you migrate to the final release of ASP.NET 2.0. This is also a non Microsoft supported component.

You can download the component here.

The port covers just about the entire API with one notable difference; there is no support for named providers. What this means is that within a single application, you can not access a  provider other than the first one configured in your web.config.

I think this is a pretty cool way to get people thinking about the new Whidbey providers sooner than later. Once we move towards releasing the CS source, I will try to post some more notes on how we implemented these providers and a couple of changes/goodies we created to make working with them a bit easier (such as support for dynamic application names, an efficeint profile reader, etc)