Expression Web

Expression Web
Name	Expression Web
Developer	Microsoft
Released	2006
Latest release version	4.0
Latest release date	2010
Operating system	Microsoft Windows
Genre	HTML editor, web design
License	Proprietary, later free

Expression Web Expression Web is a discontinued HTML editor and web design tool originally developed by Microsoft. It targeted professional designers and developers working with HTML5, CSS3, JavaScript, XHTML, and ASP.NET technologies. The application sat alongside other Microsoft products such as Visual Studio and Microsoft Office in Microsoft's portfolio of developer and authoring tools.

Overview

Expression Web provided a visual design surface and code editor intended for creating websites compatible with standards championed by organizations like the World Wide Web Consortium, WHATWG, and the Internet Engineering Task Force. It integrated features familiar to users of tools such as Adobe Dreamweaver, Notepad++, and Sublime Text while aligning with Microsoft's server platforms including Internet Information Services and frameworks like .NET Framework and ASP.NET MVC. The product aimed to bridge the workflows of front-end developers who referenced resources from Mozilla Foundation implementations, WebKit-based browsers, and Google Chrome.

History and Development

Development traces to Microsoft's broader multimedia and web initiatives alongside products such as Microsoft Expression Studio, Microsoft FrontPage, and Microsoft Visual Studio Express. Announced during the era of competing web editors including Adobe Creative Suite and Macromedia Dreamweaver successors, the software evolved amid standards debates involving the W3C HTML5 Working Group and the emergence of HTML5 as a formal specification. Microsoft positioned the product during the reign of executives associated with Bill Gates and Steve Ballmer, and it was influenced by internal engineering groups that had earlier worked on Internet Explorer. Community feedback from groups linked to Stack Overflow and GitHub users shaped subsequent releases. In response to shifts toward open-source patterns exemplified by Mozilla Firefox and corporate moves by Google LLC, Microsoft eventually reclassified the product's licensing and support.

Features and Functionality

The application combined a WYSIWYG editor, a split view for code and design, and integrated debugging tied to Internet Explorer engines. It included code intelligence akin to features promoted in Visual Studio Code and earlier in Microsoft Visual Studio. Designers used tools comparable to those in Adobe Photoshop for asset preparation and in Adobe Illustrator for vector elements, while developers leveraged support for scripting models popularized by projects from jQuery Foundation and Dojo Toolkit. Server-side editing workflows referenced ecosystems surrounding PHP, Perl, and Ruby on Rails although first-party integration emphasized ASP.NET pages and Active Server Pages. Collaboration with source control systems reflected interoperability with Team Foundation Server and third-party systems such as Subversion and Git.

File and Standards Support

File format handling covered standards like HTML4, XHTML 1.0, CSS2, CSS3, and later HTML5 features. The product aimed to interoperate with validation guidance produced by the World Wide Web Consortium and interoperability tests performed by the Web Hypertext Application Technology Working Group. It read and authored files commonly used in web stacks such as XML, SVG, JSON, and server-side templates used by ASP.NET Razor. Support for multimedia referenced codecs and containers standardized by organizations like the Moving Picture Experts Group insofar as browsers supported them. Compatibility considerations included rendering engines such as Trident and standards adopted by Blink-based browsers.

Extensibility and Integration

Extensibility was enabled through add-ins and configuration options comparable to ecosystems around Eclipse and JetBrains. Integration points targeted development lifecycles that included continuous integration systems such as Jenkins and version control systems like Microsoft Team Foundation Server and GitHub. It could be extended by developers familiar with APIs influenced by COM and scripting interfaces similar to those used by Windows PowerShell. Interop scenarios touched on content management systems like WordPress, Drupal, and Joomla! when developers prepared themes and templates for those platforms.

Reception and Criticism

Reception varied across reviews in magazines and blogs alongside commentary from communities on platforms such as Stack Overflow and Reddit. Supporters compared its visual editing and standards focus favorably to Adobe Dreamweaver and legacy tools like Microsoft FrontPage, while critics highlighted limitations when juxtaposed with rapidly evolving open-source editors such as Atom and Visual Studio Code. Analysts commented on Microsoft's strategic adjustments following moves by competitors including Google and Apple to push their own tooling and rendering engines. Reviewers referenced interoperability challenges tied to browser diversity involving Internet Explorer, Mozilla Firefox, and Safari.

Versions and Lifecycle

Major iterations culminated in a final branded release contemporaneous with releases from Microsoft Office and updates to Microsoft Visual Studio. The lifecycle paralleled transitions in Microsoft's business strategy, including shifts that led to open-sourcing initiatives exemplified by .NET Foundation and community engagements around GitHub. Support timelines intersected with product decisions announced during events and corporate communications from groups associated with Microsoft Corporation leadership. After formal support ended, the application remained in archives and influenced the design of subsequent Microsoft offerings and community tools.

Category:Microsoft software