To fix ProfileCommon in Web Applicaiton Project, put Global.asax.cs codebehind into Global.asax script tags.

This is interesting (at least, if you are website developer). In .NET 3.5, if you take the Global.asax.cs codebehind and put it into the Global.asax inside of <script runat="Server"> tags, and then, if you change all the "usings" from the Global.asax.cs into "<%@Import" tags in the Global.asax, and then if you fix a few access issues (removing "protected" from Application_Start, Application_Error and the like), low and behind, the ProfileCommon will autogenerate even in a web application project (perhaps not the whole WAP, but at least it shows up in Profile_OnMigrateAnonymous).