After my last post on sitemaps, I received an email from Scott saying I should check out http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/ASPNETProvMod_Prt3.asp and saw Microsoft has a sitemap provider for SQL!  Great, why don’t they ship this kind of stuff?  But what about the other databases?  Wouldn’t it be cool to have one that works with almost all databases?  Shouldn’t they follow their own best practices on ADO.Net usage? 

I guess I am sensitive because I have been working with Oracle a lot.  Funny how many customers want .Net and have Oracle.  I then used the Enterprise Library 2.0 and abstracted the code from the MSDN example to work with almost any database!  I think this is a much more preferment and configurable way to do a SiteMapProvider.

I went to Scott’s site and downloaded the Macro to create the sitemap and added it to my other Visual Studio .Net 2005 Macros.  Then I created a simple site.  I ran the Macro and translated that to a SQL table.  Using the NCS Library for .Net 2.0 I then created a Database Sitemap.  Then I downloaded the ASP.Net handler to create a Google Sitemap and it worked flawlessly.