Welcome to the companion Web site for Microsoft Expression Web for Windows VQS. The book gives you a jump start on using this new Web creation tool. Gone are all the crufty code hijinks of FrontPage, Microsoft's previous Web tool. Unlike its predecessor, Expression Web complies with all current Web standards. It also includes some of the handiest CSS tools available. You'll find example files from each chapter below.
FrontPage migration issues
Back in 2006 when Microsoft released Expression Web, I'd said in my book that folks looking to migrate from FrontPage should check Microsoft's site for more info. If at microsoft.com, as I suggested, you enter the terms "FrontPage migration" you won't see anything particularly useful.
But using Google, I found the document to answer your questions: written by Microsoft. Oy, what does that tell you about Microsoft's internal search engine?
Anyway, what you want to download is a 51-page white paper that's chock full of useful info.
If you used FrontPage to build your site, take comfort from this: Expression Web can open FrontPage sites without a hiccup. But because FrontPage uses so many nonstandard tools and bots, there are some migration issues, mainly bots and extensions. You don't have to rebuild the pages that use them.
Here's the white paper's key bit of info:
"FrontPage Server Extensions (FPSE) will continue to work as long as the site remains on a server with FPSEs. In addition, almost all of the components can be edited in Expression Web by double-clicking the component in Design view.
Even though Expression Web supports your pre-existing Web components, you might want to consider moving away from FrontPage Web components for several reasons. First, they produce invalid code; second, your ability to customize Web components is severely limited; third, FrontPage Server Extensions have a limited life span; and fourth, you can’t add new components using Expression Web. This section explains how to edit FrontPage Web components you may have in your site and also provides resources and suggestions to get functionality similar to that provided by unsupported FrontPage Web components.
BTW, Microsoft has a $99 upgrade package from FrontPage to Expression Web available as a download. Despite the migration heartaches, the best strategy remains upgrading.
Using the example files
The examples listed below are ready to download, chapter by chapter to match the book. Each chapter is compressed as a .zip archive: once you download a file just double-click to expand.
I'm still tidying up the files and uploading them chapter by chapter until I finish the job. That way, early-bird readers can get started without having to wait for all the chapters. .
Except for the first few chapters, which are pretty simple, each chapter folder contains example files of what the page looks like before you start working on it and what it should look like after you're done. The file names make it pretty obvious (usually something like examplefileBEFORE.htm and examplefileAFTER.htm). Whenever images are required in building the page, you'll find a separate images folder within the chapter folder.
Example Files to Download (compressed as zip files)
Chapter 1—None since overview chapter
Chapter 2—Creating Sites
Chapter 3—Working with Pages
Chapter 4—Working with Text
Chapter 5—Working with Images
Chapter 6—Creating Links
Chapter 7—Creating Style Sheets
with CSS
Chapter 8—Creating Layouts with CSS
Chapter 9—Adding Interactive
Behaviors
Chapter 10—Adding Tables
Chapter 11—Adding Forms
Chapter 12—None since it's about
publishing your files.