Here's a project to test anyone's sanity. At my company, my team maintains an ASP.net web-site project that makes heavy use of the Profile object on several pages. Maintainability of the site is at issue since we can't use web.config transformations to separate our test settings from our production settings, and I'd like to use transformations to help implement better practices in general.
One major roadblock to this is the use of the Profile object on most pages, since web application projects do not generate the ProfileCommon class. I've come up with a solution to access profile information, but I question its maintainability - I've modified the pages to inherit from a base class that has a member that implements my 'Profile' object. This makes the Profile object accessible where it is needed, but I'm wondering if there is a better way to go about this. Any thoughts?
