ASP.NET 2.0 Provider Toolkit


The ASP.NET 2.0 Provider Toolkit went live on MSDN today. It contains the source code for the Access database providers (which were cut from B2 and will not be in the final RTM product either, we are pushing SQL Express as the new defaults).  Coming in mid-month will be the detailed Provider Toolkit whitepaper (probably around August 15th, it is like 75 pages in Word!!) that explains how developers and architects can customize and extend the provider model of ASP.NET 2.0 for any enterprise environment. This is great news as it enables developers to see sample code of the providers and gives them insight into how we built our internals.  You can download it here: http://msdn.microsoft.com/asp.net/provider.


In Phase 2, we plan to extend the Provider Toolkit to include source code from the default SQl Server and Windows AD/AZMAN providers that will ship as part of ASP.NET 2.0.


Our key goal here is to make it incredibly easy for you all to build your own custom providers to that the rich ASP.NET 2.0 services can work in your environment.


Probably a bit early for feedback, but I’ll post again once the whitepaper is up, just wanted to bring your attention to this new landing page which will have lots of great info (there are already a few whitepapers up there).


 


Comments (20)

  1. Yohan says:

    I really wish someone would publish an article on creating our own provider based solution. Not creating an alternate provider for the Membership feature in ASP.net 2.0, but creating our own section we can plug into the web.config that allows custom providers to be added, etc…

    Fredrik Normen has a great project which does just this, but I think a step-by-step would be best.

  2. The ASP.NET 2.0 Provider Toolkit is available for download on the MSDN-site.

    The provider model is…

  3. Erik Wynne Stepp says:

    Yohan, follow the link above to the MSDN page to download the ASP.NET 2.0 Provider Toolkit.

    On that same page there is a link to an article by Rob Howard explaining how to build a provider-based solution on ASP.NET 1.1.

    While he’s targeting those who’d like to take advantage of this pattern before ASP.NET 2.0 is release, many of the same concepts would apply to implementing your own on top of ASP.NET 2.0.

    Here’s the direct link to his article:

    http://msdn.microsoft.com/asp.net/beta2/providers/default.aspx?pull=/library/en-us/dnaspnet/html/asp04212004.asp

  4. PeteL's Blog says:

    If you’ve read Brian’s blog, you’ve probably already heard that we released the ASP.NET 2.0 Provider…

  5. I know I should do all of this link-dumping on my del.icio.us but somehow it seems easier to store it…

  6. Would it be possible for you to provide something other than a C# Express package? Either that, or could you include the community package modules in the professional version of VS.NET? I’d like to use this provider, but I don’t need to install C# Express.

  7. bgold says:

    Michael — The VSI package requires the C# functionality in one way or another — VWD won’t work with it, but C# Express, VS Std, VS Pro, and VSTS will… therefore if you have any version of the full visual studio, you can easily install this VSI and work with the sample access provider.

    Does that answer your question?

  8. B says:

    Hello,

    I’m trying to connect to an MSAccess database usign ASP.NET 2.0 and I found your article and the provider on the MSDN site, but coudl somebody explain me how I can install this provider ?

    I noticed that you need C# and that you need to compile it with, but I don’t have any expertise with Visual Studio C#.

    Can some help me how I can install the provider?

    This woudl be very helpfull, because I’m already looking for this answer a few weeks.

    Thank you all.

  9. Jeff Lynch says:

    Any word on the "mid-August" whitepaper and SQL Provider source code? It’s already mid September!

  10. bgold says:

    Hey Jeff — sorry about the delay, we had to ‘slip’ this a bit because we decided shipping VS2005 and .NET F/X 2.0 was more important 🙂 But, funny you ask cuz I got the final final draft today — just need to have a product team review then get it onto MSDN — so it is coming. Ping me directly and I’m happy to send you the draft. bgold at ms dot com

  11. I really wish that an MS Access provider was still included as a built in option for ASP.NET 2.0.  For small shops using an SQL database is so much more complicated.  Updates are more difficult and it requires the production server to have an SQL engine installed – something that hosters are reluctant to do because of all the targeted attacks.

    Requiring SQL server really limits markets for small web projects.

  12. bgold says:

    Ken — I hear your feedback, but access doesn’t really scale and we have many affordable SQL solutions with hosters.  Also, SQL Server Express is a free database options that works for most small/medium workloads.  

    If Access is still what you need, we have it avaialble for download and it can be easily compiled and swapped into a project — we just felt that it was best to take Access out as a default option but we didn’t want to not enable this scenario for folks like you that want it.

    Hope this helps clarify.

    -Brian

  13. Brian posted about this a little earlier today, but in case you missed it I'd recommend checking