Microsoft delivers updated WebMatrix Web-development toolset

Microsoft delivers updated WebMatrix Web-development toolset

Summary: Microsoft has released to the Web the final version of its latest free WebMatrix tool bundle, which includes tighter Windows Azure integration.


On May 1, Microsoft released to the Web the final version of its WebMatrix 3 toolset for creating, publishing and maintaining Web sites.


(It looks like the early April WebMatrix 3 announcement was for a test build, and not the final version, which was hard to tell.)

The third release of this lightweight toolset includes support for Windows Azure Web Sites (the Web-hosting framework codenamed "Antares"); source-control tools for working with Git and TFS and improved remote editing.

WebMatrix 3 also includes support for code completion for PHP, Node.js, ASP.NET, HTML5, CSS3, and jQuery. It supports open-source apps like Wordpress, Drupal, Umbraco, Joomla out of the box, and has built-in database management for SQL Server, SQL CE as well as MySQL. The WebMatrix toolset also can help devs test their Web sites on iPhone, Windows Phone, iPad.

WebMatrix 3 can be downloaded from Microsoft's site for the product.

WebMatrix is a free set of tools for creating, publishing and maintaining Web sites. It enables developers to quickly install and publish open-source applications or built-in templates to create, publish and maintain their Web sites. Included in the bundle are a Web server, database engines, various programming languages and more. It is aimed at developers using ASP.Net, PHP, Node.js and/or HTML5.

Originally launched in 2010, WebMatrix got its start as a collection of a lightweight version of Microsoft’s IIS Web Server, known as IIS Express; an updated version of SQL Server Compact Edition; and a new “view-engine option” for ASP.Net, known as “Razor,” which enabled developers to embed Visual Basic or C# within HTML.

In other Azure-related news of potential interest to developers, Microsoft also released the Windows Azure SDK (software development kit) 2.0 for .Net earlier this week.

Topics: Web development, Cloud, Microsoft, Open Source


Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • Azure team continues widening their lead

    over amazon and google. It's really the only choice now for serious cloud app deployment.
    Johnny Vegas
    • The cloud will never get there, it will go up like a PUFF of smoke

      Think what you won't be long and it will be over before it really gets started......end of story
      Over and Out
  • Microsoft only product.

    Yet another Microsoft only tool. 65% or greater percent of all web servers are Apache. This tool required IIS. Another we will make tools and think no one is using them because of bad design and re-brand and change the interface completely. All the while not realizing that no one uses our tools because they are all tied to IIS. IIS has never and will never be remotely comparable to the stability, reliability, and low resource usage that Apache has always had. If Microsoft would lose the IIS they could gain some ground in web develop until then it is as always a waste of time. Just like Front Page, Blend, etc...
    • Yes, Microsoft makes IIS

      Yes, Apache powers the great majority of *small websites*. However, among Fortune 1000 sites, IIS dominates and has done so for more than a decade.

      IIS and Apache are much the same when it comes to the stability and reliability. The IIS architecture is a little better designed for optimal stability through better separation of the request receiving and-processing. Apache can be clogged by a misbehaved app, IIS cannot.

      IIS has *much* better support for *application* stability by providing integrated health monitoring and automatic recycling. IIS will by default monitor applications for excessive CPU and RAM usage. If an application starts going rogue and allocates excessive amounts of RAM, IIS will gently recycle the app with no admin intervention. All configurable, of course. Apache doesn't do that. If an app goes rogue on Apache - it just keeps on consuming resources.

      By IIS gently recycling the app - that means exactly that. IIS actually spins up a new instance of the app *before* taking the old one down. It will then "drain" the old instance by not dispatching any more requests to it. When all requests has completed it will then terminate the process/thread. Apache doesn't do that.

      IIS smokes Apache when it comes to performance. Really. It serves up static pages much faster and it has an integrated kernel mode cache which works for output caching even for dynamic pages.
      • Apache "small business"?

        Apache powers 58% of fortune 500 company. Sorry Apache beat IIS hands down all day long on performance. IIS has to managed and monitored, Apache doesn't it just runs. It doesn't do apps as well because your web service shouldn't be running apps you web server should or script on your web server if you can't make the client handle it. IIS work well in a Microsoft only world, but with the global world the web now exist in, it is now not a Microsoft world.
    • Why it requires IIS?...

      Well it's pretty simple. Why on earth do you think this full blown product is FREE? For selling back the server products. Developing PHP on IIS engine will imply you will deploy it on IIS (and therefore on Windows Server).
      That being said, I agree with . There are much more things happening in the enterprise world that we see by evidence. What counts finally is the global ROI. If after all investments and developments the company has a better ROI, it does give a damn whether is uses open source or a "closed" product based solution. And it is really the case with all enterprise product suite from MSFT.