I bloged about not being able to use the Profile feature of ASP.NET 2.0 in the new Web Application Project (which is now released in case you haven't noticed). Scott shows a workaround in his tutorial for migrating Web Sites to the new Web Application Project. It's a ok workaround and I guess it would be really easy to make it even a little bit more consistent with the Web Site model by creating a base class for your pages with a property that exposes the class. Creating your own base class for your pages works much smoother in ASP.NET 2.0 than it did in 1.1. I can also see times when Scotts workaround is the only correct way to expose the Profile information instead of defining it in a very editable config-file.

Johan was nice enough to send me a link to this post which links to an add-in for creating a strongly typed version of the Profile feature.