Jack @ ASP.NET

Industry standards and innovation took center stage at MIX10, as Microsoft Corp. made a series of announcements that underscore the company’s commitment to interoperability and performance on the Web. Dean Hachamovitch, general manager of Internet Explorer at Microsoft, unveiled the Internet Explorer 9 Platform Preview including expanded support for HTML5, hardware-accelerated graphics and text, and a new JavaScript engine. Together these allow developers to use the same markup and deliver graphically and functionally rich Web applications that take advantage of modern PC hardware through a modern operating system.

Microsoft also announced that it will contribute to the development of new features and enhancements in the jQuery JavaScript Library and shared the release of new software development kits (SDKs) for the Open Data Protocol (OData) that make it easier for developers to access data from the cloud to create more compelling cross-platform Web applications.

As part of Microsoft’s broad engagement with open source communities, Corporate Vice President Scott Guthrie today announced that Microsoft is investing resources to contribute to the development of the jQuery JavaScript Library to help improve the development process of standards-based Web applications. Microsoft will also work to provide better interoperability between ASP.NET and the jQuery JavaScript Library by enhancing ASP.NET so .NET developers can better incorporate jQuery capabilities. In addition, Microsoft will actively promote and distribute versions of the jQuery JavaScript Library by packaging it with popular products such as Microsoft Visual Studio 2010 and ASP.NET MVC 2. As a first step, Microsoft will contribute a templating engine to the jQuery JavaScript Library Team to simplify Web applications.

Sometimes, we have to convert an Enum back to its original Xml value, after google the solution, I fond it is not hard to implement, and share it here

Method

public static string ConvertToString(Enum e)
{
// Get the Type of the enum
Type t = e.GetType();

// Get the FieldInfo for the member field with the enums name
FieldInfo info = t.GetField(e.ToString("G"));
// Check to see if the XmlEnumAttribute is defined on this field
if (!info.IsDefined(typeof(XmlEnumAttribute), false))
{
// If no XmlEnumAttribute then return the string version of the enum.
return e.ToString("G");
}
else
{
// Get the XmlEnumAttribute
object[] o = info.GetCustomAttributes(typeof(XmlEnumAttribute), false);
XmlEnumAttribute att = (XmlEnumAttribute)o[0];
return att.Name;
}
}


A demo of how to use this method

static void Main()
{
// Get the XmlEnumAttribute
Console.WriteLine(ConvertToString(TestEnumClass.Three));

public enum TestEnumClass
{
One = 1,
Two = 2,
[System.Xml.Serialization.XmlEnum("The Third one")]
Three = 3,
}


FastCGI extension has a set of configuration settings that controls the behavior of FastCGI processes associated with the FastCGI process pool. This section lists all the settings supported by FastCGI and their format:

* ExePath – The physical path to the process executable to use in the pool
* Arguments – Arguments to pass to each process in the pool at start time. This setting is optional.
* EnvironmentVars – Environment variables that are set for the process executable associated with this pool.
Some more improvement including:
# Monitor changes to a file. The module can be configured to listen for file change notifications on a specific file and when that file changes, the module will recycle FastCGI processes for the process pool. This feature can be used to recycle PHP processes when changes to php.ini file occur. To enable this feature use the monitorChangesTo setting in the configuration element.
# Real-time tuning of MaxInstances setting. This MaxInstances setting dictates the maximum number of FastCGI processes which can be launched for each application pool. Set it to 0 to let FastCGI module automatically adjust the number of instances up or down based on the system load and number of requests waiting in the queue.
# STDERR stream handling. There are several options of how the module can handle text sent by FastCGI application on STDERR. The module can send the error data as a failure response to the HTTP client or it can ignore the error and send whatever was received on STDOUT as a response with 200 status code. This behavior is controlled by the stderrMode setting.
# Sending a termination signal to FastCGI processes. The module can be configured to send a termination signal to FastCGI process before terminating it. This enables FastCGI processes to do a clean shutdown before getting killed. The signalBeforeTerminateSeconds setting can be used to specify how long the module will wait before it forcefully shuts down the FastCGI process that does not respond to the termination signal. This feature is disabled by default.
# _FCGI_X_PIPE_ environment variable. This variable is set by FastCGI module and it contains the name of the named pipe that is used for communication between the module and FastCGI process.
# Relaxed enforcement of response headers syntax. The FastCGI module now has less strict enforcements for the correctness of the response headers.
# Using UTF-8 encoding for server variable values. By default FastCGI uses ASCII encoding when setting server variables. If a FastCGI application requires UTF-8 encoded values for certain server variables, the module can be configured to use UTF-8 only for required server variables.

A hotfix is now available for issues most commonly described as "Controls are not being recognized in the code-behind" and "Editing existing .aspx regenerates .aspx.designer.(cs), but most of the controls are now missing”.

This hotfix can be downloaded from: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=27117

The update addresses the following Connect bugs:

    * Cannot embed standard asp.net controls in Ajax Control Toolkit TabContainer
    * Controls in CreateUserWizard WizardStep not visible as before
    * issue with auto-generated Designer files not addding components
    * Code Generation in 2010 RC doesn’t work the same as 2008 for ASP.NET Application
    * Editing existing .aspx regenerates designer.cs (good) but most of the controls are now missing (bad)
    * ASP.NET designer fails to auto-generate fields
    * Bug in generating the designer.cs file in VS2010 (Converting VS2008 project to VS2010)

Visual Studio 2010 is set to be released in April.  Microsoft has made significant investments to improve the “Testing”, “Architecture”, and “Developer” tools within Visual Studio to make it an even more powerful productivity solution.

VS 2010 Webinar Session Overviews:

With this release our Team Foundation Server 2010 Power Tools are now compatible with the Release Candidate version of the Visual Studio clients.

Changes from Beta2

· Fixes to customer reported bugs

· Team Members is now enabled

· Extended rules for the RC Best Practice Analyzer

The following are the Power Tools supported in this release.

• Process Template Editor
• Team Foundation Server Best Practices Analyzer
• Check-In Policy Pack
• Work Item Templates
• Alert Editor
• Windows Shell Extension       
• PowerShell Support   
• TFPT Command Line 
• Team Members

For detailed information, please go to http://7e4f200f.linkbucks.com