Microsoft WebMatrix is intended to serve the website creation, customisation and publication needs of designers and amateurs, and not as a substitute for Visual Studio or other professional development tools. As a professional developer, I can see why it might appeal to its target audience, but I can't stand to use it myself for more than 15 minutes at a time.
Rick Grehan's preview of WebMatrix in November covered most of the product features well, so I won't repeat his descriptions and analysis. Since then, a few features and gallery items have been added, which I'll discuss as I go along. I've included a handful of screen images at the end of the article.
Rick picked on the weakness of the editor and the lack of a debugger, and until I worked with the product myself, I didn't understand how kind he was in the way he phrased his objections. After spending time with WebMatrix, I know otherwise.
|Webmatrix Start Page|
When I first saw the WebMatrix demo, I was very impressed with the smooth way it calculated dependencies and constructed the application stack, database, interpreters and connectors, needed to run a public domain web application on Windows. It looked like the Windows answer to the auto-installer packages you get for free on hosted Linux websites.
When I tried it myself, I was bitterly disappointed. Sure, the dependencies were calculated, and the primary package came down quickly. However, the download stalled, and I was never able to do a successful installation from the Gallery, even after multiple tries on multiple days.
I had better luck with the templates, but there are only a few of them, and they don't do much. The Bakery demo does show off Razor markup, but frankly I'm not impressed. Yes, Razor requires less markup and simpler code than ASP, PHP or ASP.Net, but those technologies make a much clearer distinction between server code and client markup than Razor when you are looking at the source of a page.
The new SEO scanner can look at any site, not just your own and point out where the rules in its database have been broken and how to fix the problem. Many of the checks are useful, but mostly at a low level, such as "The page contains broken hyperlinks." Other checks seem to be misguided, based on my own experience doing search optimisation. For example, search engines tend to give higher scores to pages with organic body content and no keyword metadata, but the SEO scanner expects to see keyword metadata.
|Import Sites from Web Gallery easily|
The SQL Server Compact Edition database has SQL semantics but is entirely file-based. That makes it perfect for low-overhead development scenarios. WebMatrix's ability to upsize from this to scalable SQL databases makes it fit into the typical web development lifecycle. Of course, the free open source SQLite3 has many of the same characteristics, but Microsoft has always had a streak of NIH syndrome.
The product also includes an editor for the database. It isn't much, but it does the job for the schema, data and indexes, and it keeps the novice from having to learn SQL Server Management Studio or phpMyAdmin.
- Lightweight desktop SQL database
- Website deployment that synchronises databases and files
- Simplified Razor syntax and single page model for server-side code
- A small assortment of helpers to add common functionality easily
- SEO site scanner and checker
- Web application stack constructor depends on download servers being available
- Oversimplified site editor, but easy link to Visual Studio
- SEO checker not particularly useful