• After Upgrade I can't login - This is generally caused because you performed an upgrade and forgot to copy over the MACHINEKEY settings. Hopefully you backed up your web site before you upgraded so that you can get the proper machinekey settings from the old web.config file. If you used the UPGRADE package you likely will never come across this problem.
• After Upgrading I get Compiler Errors - This is likely caused by a failure of the system to upgrade your web.config to .Net 3.5. The easiest way to test this is to look at the <system.codedom /><compilers /> section of web.config and compare it to the examples below.
  

<system.codedom> 

  <compilers> 

    <compiler language="vb" type="Microsoft.VisualBasic.VBCodeProvider, System,

     Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" extension=".VB" /> 

  </compilers> 

</system.codedom>

<system.codedom> 

  <compilers> 

    <compiler language="vb;vbs;visualbasic;vbscript" type="Microsoft.VisualBasic.VBCodeProvider,

     System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

     extension=".vb" warningLevel="4"> 

      <providerOption name="CompilerVersion" value="v3.5" /> 

      <providerOption name="OptionInfer" value="true" /> 

      <providerOption name="WarnAsError" value="false" /> 

    </compiler> 

    <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider,

     System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" 

     warningLevel="4"> 

      <providerOption name="CompilerVersion" value="v3.5" /> 

      <providerOption name="WarnAsError" value="false" /> 

    </compiler> 

  </compilers> 

</system.codedom>

• More coming soon!