Access vs. SQL Express providers in ASP.NET v2

I noticed that the Access providers for Membership and such won't be there, or am I reading that they just won't be the default providers?

It doesn't actually matter to me, but I'm trying to get my book finished and I'd like to at least take a reasonable stab at getting it right. Sure, I've got disclaimers here and there about what was for real in beta 1, but I'd like to get that up to beta 2. Now I see what authors mean about the pains writing for a product that isn't final yet.

I noticed in Shanku's blog that they want to substitute the Access providers with SQL Express. I have to admit I haven't even installed that product yet. You can move a database as a file? Anyone see a good article on that?

2 Comments

  • I can forward your details to the publisher, if you like.



    It's not a huge issue if it changes, because what I wrote had more to do with creating your own providers than using the default Access provider. I'm still really surprised by this because having the framework just mystically generate and Access file sure was a nice feature for small sites.



    Not sure about a release date for the book. I assume sometime in 2Q05, but the thing I'm learning about publishing is that it's a very fluid process.

  • The Access provider will be removed from the product. They removed it because the Jet database engine is not suitable for a server environment, and they need to point folks at more robust technologies like MSDE, and Sql Server Express 2005.



    Microsoft will post the Access providers and their code on the www.asp.net at some point during the Whidbey ship cycle. This means the Access providers will be available out-of-band from the framework, and that once we release the code they will not be officially supported by the framework.

Comments have been disabled for this content.