2 Introduction Why Everett? Numerous bug fixes Mobile project types “in the box”
3 Installation Side-by-side V1.0 and V1.1 of the framework install side- by-side.
4 Side-by-Side Abandon hope all ye who enter here. Microsoft will release new versions of the framework. New versions “should” be compatible. Microsoft will break compatibility for: Bug fixes Security fixes Multiple versions of the framework can be installed simultaneously (Side-by-side)
5 Side-by-Side Your application will run on the framework it was compiled against (in most cases)
8 Side-by-Side Application Behavior V1.1 Application V1.0 Framework Application fails unless specifically configured to run on V1.0
9 Side-by-Side Application Behavior V1.0 Application Application tries to run unless specifically configured to fail. V1.1 Framework
10 Side-by-Side Components V1.1 Application Components have no life of their own. They run in whatever context the app runs in. V1.1 Framework V1.0 Component
11 Side-by-Side Components V1.0 Application This could be bad. What if the component uses/depends on something in V1.1? V1.0 Framework V1.1 Component
12 Side-by-Side ASP.NET V1.0 and V1.1 web sites can run on the same machine. After you install V1.1, the default web site is upgraded to V1.1. Any site that inherits the default web site (which, by default, includes all your V1.0 ASP.NET sites) are upgraded Any new sites you create (even with VS 2002) will be V1.1 sites. You can manually configure the framework of a site with: aspnet_regiis –s w3svc/1/root/MySite
13 Side-by-Side Demo Configuring Target Runtime ASP.NET Side-by-Side
14 Security Enhancements ASP.NET Security Enhancements Protection against cross-site scripting attacks built-in. Ability to sandbox ASP.NET Web sites. No-touch deployment Windows forms apps deployed through the Internet run with some basic permissions.
15 Everett Summary Security enhancements Bug fixes Not a “Major” new release, but no reason to stay on V1.0 either.