Wednesday, January 20, 2010

Visual Studio 2010 and .NET Framework 4.0 Launch Date Postponed

In a very small announcement by Developer Division’s Marketing and Communications Manager Rob Caron, Visual Studio 2010 and .NET Framework 4.0 is set to be officially launched April 12, 2010 and not March 22 as previously announced. However, the date for release to manufacturing (RTM) still remains unknown.

Historically, RTM for Visual Studio has been months ahead of the official launch. Visual Studio 2008 as an example was RTM November 19 2007, but officially launched February 27 2008, 3 months later.

Scott Guthrie reported late last year that Visual Studio 2010 is postponed because of performance issues found in Beta 2 and revealed plans for an intermediate release in February:

…we plan to make a Release Candidate build available in February that everyone will be able to download and test. It will be a public build and include a broad “go live” license that supports production deployment.

Taking into account that the official release date is now April 12 and the RC is in February, the date difference between the official release and the RTM is probably much closer than for previous releases of Visual Studio.

jQuery 1.4 released

Great news for jQuery lovers, jQuery 1.4 is released on 14-Jan-2010 and it has got amazing new features. Please click here to see 15 new features of jQuery you must know.

What’s New in jQuery 1.4?

jQuery is probably the most popular JavaScript framework on the web. Many developers insert the script by habit (yes, I’m referring to you!), so the jQuery team needs to be extremely cautious when creating new releases.

The code base has been heavily restructured to reduce complexity and increase performance. There are some impressive bar charts on which highlight how good the optimizations are.

207 bugs have been fixed and the framework now passes 100% of all tests in IE6, IE7, IE8, Firefox 2, Firefox 3, Firefox 3.5, Safari 3.2, Safari 4, Opera 10.10, and Chrome.

There is a substantial number of new methods and two new events: focusin and focusout. These are equivalent to focus and blur, but they implement an event bubbling-like technique (focus and blur do not normally bubble)

What Will Break If You Upgrade?

The jQuery team has provided a list of the most likely problems. I suspect the following issues will cause the most confusion:

1. jQuery() returns an empty set
In previous versions of the library, running jQuery() (no arguments) returned jQuery(document). It now returns an empty set, although the jQuery().ready() event will still fire as expected.

2. Ajax requests must use valid JSON
If you’re passing JSON data in Ajax calls, you must ensure it’s not malformed.jQuery now use the browser’s native JSON.parser in preference to eval when possible.

3. jQuery.browser returns the engine version
If you’re sniffing for browsers, jQuery.browser now returns the rendering engine version rather than a specific browser type, e.g. “webkit” rather than “chrome”.

I mentioned how difficult user agent parsing had become in a previous post. The jQuery developers have reduced complexity and increased speed by simplifying the returned information.

Although jQuery still supports browser-like detection, I strongly recommend you avoid it and use feature/object detection instead.