Feb 21, 2011 13:07 GMT  ·  By

Developers leveraging the first version of WebMatrix that have come across glitches, need to head over to the Microsoft Web Platform site and access the latest release made available. Microsoft shipped version 1 of WebMatrix in the first half of January 2011, and it appears that some issues survived past the RTW (release to web) milestone.

This is why the company published an update to WebMatrix last week, aiming to resolve some of the problems reported by devs since the RTW went live.

A member of the Microsoft Web Platform team provided a list of fixes, highlighting some of the glitches that the Redmond company has already dealt with.

The WebMatrix Refresh is live since last week, and is considered to be nothing more than a minor update.

“We did this to fix some of the top customer issues that have been reported since we launched in January,” the Microsoft Web Platform team representative added.

Here is a list of fixes that were implemented in the WebMatrix Refresh which is now availale:

“•Customer report: Ctrl+C/X/V breaks once international characters are entered when using the United States-International keyboard layout with WebMatrix

•Exception error when template installer link is broken

•Web Deploy hard-coded fallback MySqlDump.exe path will make MySQL app operations fail by default when WebPI starts using new version of MySQL

•Web Deploy requiring MySQL installed locally when installing application for use with remote MySQL server

•Bin deployment of SQL CE binaries broken in WebMatrix because Web Deploy copies only .dlls and additional .manifest file is required

•Add "spotlight=true" to Find Web Hosting URL

•Broken xml file for spanish resource file of template

•IIS Express doesn't run when My Documents is on a root drive

•For non-local documents, introduce a new environment variable that WebMatrix sets and IISExpress reads to determine if it needs to start polling

•Redirection.config fallback path is incorrect

•Add a regkey to switch default opening of PHP files in UTF-8 vs. local code page.”