<p>If you create an ASP.NET web file project you have direct access to the Profile information in the web.config file. If you convert that to a Web App and have been using ProfileCommon etc. then you have to jump through a whole bunch of hoops to get your web app to work.</p>

<p>Why wasn't the Profile provider built into the ASP.NET web app projects like it was with the web file projects?</p>

[{'answer_id': 12606, 'author': 'Jon Galloway', 'author_id': 5, 'author_profile': 'https://Stackoverflow.com/users/5', 'pm_score': 3, 'selected': True, 'text': '<p>The profile provider uses the ASP.NET Build Provider system, which doesn\'t work with Web Application Projects.</p>\n\n<blockquote>\n  <p>Adding a customized BuildProvider\n  class to the Web.config file works in\n  an ASP.NET Web site but does not work\n  in an ASP.NET Web application project.\n  In a Web application project, the code\n  that is generated by the BuildProvider\n  class cannot be included in the\n  application.</p>\n</blockquote>\n\n<p>source: <a href="http://msdn.microsoft.com/en-us/library/system.web.compilation.buildprovider.aspx" rel="nofollow noreferrer">MSDN Build Provider documentation</a></p>\n'}, {'answer_id': 633311, 'author': 'nandos', 'author_id': 3440, 'author_profile': 'https://Stackoverflow.com/users/3440', 'pm_score': 2, 'selected': False, 'text': '<p>Actually, Microsoft does have a solution for this known issue.\nIt\'s the "Web Profiler Builder". I used it for my Web App and it works great.\n<a href="http://code.msdn.microsoft.com/WebProfileBuilder/Release/ProjectReleases.aspx?ReleaseId=980" rel="nofollow noreferrer">http://code.msdn.microsoft.com/WebProfileBuilder/Release/ProjectReleases.aspx?ReleaseId=980</a></p>\n'}]
['https://Stackoverflow.com/questions/12603', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/1463/']