If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post and use all the features of the Chess2U forums. To start viewing messages, select the forum that you want to visit from the selection below.

Feature 2 - When a shadow cache assembly that is turned into a symbolic link to the same file is validated, the size of the assembly is not checked. Therefore, ASP.NET uses Optimization for Shared Web Hosting.

Feature 3 - New syntax lets you define a TextBox control that is HTML5 compatible. For example, the following code defines a TextBox control that is HTML5 compatible: <asp:TextBox runat="server" type="some-HTML5-type" />

Feature 4 - A new switch is added for the Visual Basic compiler that allows for server control output of HTML5-friendly elements. For example: <asp:TextBox runat="server" type="some-HTML5-type" />

In earlier versions of the .NET Framework, all Visual Basic applications automatically had a runtime dependency added. The dependency was with the Visual Basic Runtime library file, Microsoft.VisualBasic.dll. With this update, a command-line option can be set to remove this dependency. Some functionality of the Visual Basic Runtime is embedded in the application, and other functionality is no longer available with the switch set.

Feature 5 - Changes to the support portable libraries. These changes include API updates and binder modifications. This update enables the CLR to bind successfully to portable libraries so that a single DLL can run on the .NET Framework 4, on Silverlight, on Xbox, or on the Windows Phone. This update adds public Silverlight APIs to the .NET Framework 4 in the same location. The API signatures will remain consistent across the platform. All modifications are 100 percent compatible and will not break any existing code.

Feature 6 - The update extends the support of the portability files to compile Silverlight 5 XAML files.”