New Post: 4.2 Beta 2 available

I've just upgraded to 4.2 beta3 and C1 continues to be rock-solid. However, the issues above have not yet been addressed. Should I log these into the Codeplex Issue tracker?

During the upgrade from beta2 to beta3, I got a lot of orange log messages along the lines of "File C:\Users#####\www-composite\Composite\skins\system\shadows.css does not exist, cannot be deleted". Are these cause for concern?

I also had a red log item reported during the upgrade:

System.IO.FileLoadException: Could not load file or assembly 'System.Web.WebPages, Version=3.0.0.0, Culture=neutral, PublicKeyToken=##############' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)File name: 'System.Web.WebPages, Version=3.0.0.0, Culture=neutral, PublicKeyToken=##############'

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

System.Exception: Failed to load assebmly 'System.Web.Helpers, Version=3.0.0.0, Culture=neutral, PublicKeyToken=##############'

Is that anything to worry about, or can I safely ignore?