Creating a Silverlight 4 Development Machine
Now that a Silverlight 4 beta is available, it’s time for me to create a new VM where I can develop Silverlight 4 applications. This development machine will be based on Windows 7 and include:
- Visual Studio 2010 Beta 2
- .NET Framework 4 Beta 2
- Silverlight 4 Beta
- Expression Blend for .NET 4 Preview
As of January, 2010, this represents the most complete development environment possible for Silverlight 4 applications.
Operating System
I’ll be installing into a virtual machine environment, using VMware Workstation 6.5.1, running on top of Windows 7 (the host operating system). The guest operating system, where I’ll be installing the development tools, will be Windows 7 Ultimate.
Both my host and guest machines are 32-bit (x86).
Here’s our “clean slate”–a fresh install of Windows 7 Ultimate with nothing else yet installed:
It’s a beautiful sight.
Overview
Here’s a complete list of what I’ll be installing in the Windows 7 virtual machine:
- Visual Studio 2010 Ultimate Beta 2 (x86) (19 Oct 2009)
- Silverlight 4 Beta Tools for Visual Studio 2010 (2 Dec 2009)
- Microsoft for Expression Blend for .NET 4 Preview (16 Nov 2009)
- Silverlight Toolkit (18 Nov 2009)
- WCF RIA Services for Visual Studio 2010 Beta 2 (3 Dec 2009)
I’ll include a link to the location of each tool in the sections below.
Install Visual Studio 2010
I got my copy of Visual Studio 2010 through my MSDN subscription, but you can get a free copy (“Go Live” license) here:
Download Visual Studio 2010 Beta 2
I haven’t tried downloading Visual Studio 2010 from this location, so I’m not sure what edition you get. But even if it’s one of the Express editions, it ought to be fine for developing Silverlight 4 applications.
We start by launching the VS 2010 installation.
The installation begins.
We agree to the license, after carefully reading it.
Next, we choose either a Full or Custom installation. I always go with Custom, so that I can turn off stuff that I don’t want. Notice that the default installation takes up 6.4 GB.
The next screen lets me select individual components to install. It looks like everything is selected by default.
Here are my preferred choices. I have no interest in VB, VC++ or F#. For now, I’ll just stick with C#. I do include the Office Development tools, but don’t need the Dotfuscator feature or SharePoint development tools. I also uncheck SQL Server 2008 Express, since I’ll later install a full version of SQL Server 2008 when I need it. This brings the install footprint down to 3.6 GB.
The installation process now starts. It will take a while, since we have a lot of different components to install.
A reboot is required after installation of the .NET Framework.
By the way, it’s interesting to note that version 4 of the .NET Framework actually updates the core components of the .NET Framework. This was not true of version 3.0 or 3.5, which were both just releases that added to existing functionality. So 4.0 represents the first time that core libraries have been updated since the 2.0 release in Nov, 2005–just over four years ago.
Nearly done now..
And the installation is now complete.
Install Silverlight 4 Beta Tools for Visual Studio 2010
Visual Studio 2010 includes support for Silverlight 3, rather than Silverlight 4. Because Visual Studio 2010 ships a bit earlier than Silverlight 4 (Visual Studio 2010 shipping in March, 2010 and Silverlight 4 shipping sometime in the first half of 2010), Visual Studio 2010 will support Silverlight 3 rather than Silverlight 4.
You can download the Silverlight 4 Tools for Visual Studio from the link below. Note that this version of the Silverlight 4 tools works only with Beta 2–not Beta 1.
Download Silverlight 4 Beta Tools for Visual Studio 2010 Beta 2
The install starts:
There’s another license agreement to read and accept.
The install begins.
And we’re done..
Install Expression Blend Preview for .NET 4
There is a free preview download of Expression Blend that supports targeting both Silverlight 4 Beta and .NET 4 Beta 2. It is listed as being compatible with Visual Studio 2010 Beta 2 and can be found at:
Download Expression Blend Preview for .NET 4
This is version 3.1.11111.0 of Expression Blend. It supports creation of both Silverlight 4 Beta and .NET 4 Beta 2 content, but does not support creation of Silverlight 3 or .NET 3.5 content. It also does not include SketchFlow.
Note: If you are installing the tools to a virtual machine running in VMware Workstation, you may need to make a change in your display settings for the virtual machine before launching the Expression Blend install. If the 3D graphics setting is enabled for the VM, the Blend install program may not display properly. Under VMware Workstation 6.5.1, I’ve seen this problem consistently. The fix is to disabled the 3D graphics setting for the VM.
One you disable 3D graphics, the first dialog in the install program will display properly.
The Blend install dialogs are certainly beautiful.
The installation starts:
And the installation finishes quite politely.
Install Silverlight Toolkit
Next, we install the Silverlight Toolkit, which includes a number of additional Silverlight Controls. You can find the toolkit on CodePlex.
The install says that this is the toolkit for Silverlight 3, but the Nov, 2009 release has been updated to include support for Silverlight 4.
Yet another license agreement.
You next get a chance to decide which components of the toolkit to install.
Ready to start the install now.
The Silverlight Toolkit install in action:
And we’re done.
Install WCF RIA Services
Next, we install the WCF RIA services, which is a framework that allows writing n-tier ASP.NET/Silverlight applications.
You can find the WCF RIA Services install at:
Install WCF RIA Services for Visual Studio 2010 Beta 2
The link above allows you to download and install the WCF RIA Services. However, I noticed that when I got to this point, it was already installed. As it turns out, the install for the Silverlight 4 Beta also installed the WCF RIA Services preview.
Documentation
We’ve now downloaded everything that we need for creating Silverlight 4 applications. One remaining piece of information that will be helpful is that the Silverlight 4 documentation can be found online at:
Wrapping Up
There we go. I now have a clean virtual machine that has everything on it that is needed for creating Silverlight 4 applications. My one last remaining task is to go and save a snapshot of the VM, so that I preserve the “clean” Silverlight 4 development environment.
Silverlight Gets Full-Fledged Designer Support in Visual Studio 2010
Trying to wrap my head around the current situation with Silverlight 2 and 3 support in Visual Studio 2008 and 2010, I’m confused enough that I feel like shouting out a line from my daughter’s favorite Dr. Suess book, Fox in Socks: “Now wait a minute, Mr. Socks Fox”!!
It is a little confusing. But I think I now understand who supports what and I’ll take a stab at jotting it down, for future reference.
Visual Studio 2008 SP1
- Supports either Silverlight 2 or Silverlight 3, but not both on the same development machine
- Silverlight 2 — install using the Silverlight Tools for Visual Studio 2008 SP1
- Silverlight 3 — install using the Silverlight 3 Tools Beta for Visual Studio 2008 SP1
Visual Studio 2010
- Supports both Silverlight 2 and Silverlight 3
- Can install both on the same development machine
- Each Silverlight project targets one of the two Silverlight versions
- Silverlight 2 — need to install the Silverlight 2 SDK manually
- Silverlight 3 — install manually
Ok, as far as I can tell, that’s the current situation.
This basically boils down to two questions:
- Do I want to develop in Silverlight 2 or Silverlight 3?
- Silverlight 2 is more stable and is officially released
- Silverlight 3 (beta) — new controls, navigation framework, out-of-browser support
- Which version of Visual Studio do I want to use?
- VS 2008 — easier install experience, stable/released
- VS 2010 — improved tooling for Silverlight & WPF
The last point is what I want to talk about. Notice that improved tooling for Silverlight is a feature of Visual Studio, not of Silverlight itself. Visual Studio 2010 finally gives us full design-time drag-and-drop support for Silverlight.
Let’s see what this looks like. But first, let’s go back and take a look at the Silverlight design-time experience in Visual Studio 2008. (I’m using Silverlight 3 here).
The Bad Old Days – Visual Studio 2008 SP1
Until now, Silverlight developers haven’t had the most basic tooling enjoyed by even the lowliest VB6 developers. Namely — the ability to drag and drop controls onto a design surface and set their properties right in the designer.
Specifically, here’s what you couldn’t do. If you look at the split window for Silverlight controls in the designer, you’ll notice that the upper pane is labeled “Preview”.
This was a “Preview” pane because all it could do was to render your XAML on the screen as a preview of how it would eventually look in your Silverlight application. You couldn’t drag controls onto this surface. You also couldn’t select any controls in order to reposition them or to set their properties.
In Visual Studio 2008, if you try dragging Silverlight controls onto this Preview window, you just get a big fat “don’t do this” icon. Even sadder, you can’t select any controls. If you look at the properties window in Visual Studio, you just see the following sad message:
Thankfully, you could at least drag and drop controls down into your XAML. This would at least insert the proper XAML tags for the control that you’d selected. But you just got an empty tag. (In the picture below, I’ve just dragged a Button into my XAML).
And, although we weren’t able to set property values in the property editor, there was some consolation in that Intellisense worked in the XAML code.
So the Silverlight development environment was workable, but not ideal. Also, you could always author/edit your UIs in Expression Blend. But then there was a big learning curve to tackle.
Enter Visual Studio 2010
In Visual Studio 2010, we finally have full designer support for Silverlight applications. In the picture below, I’ve just dragged a Button from the toolbox onto the design surface.
It makes me want to weep. (Who would have thought that a developer would be so happy with being able to drag a button onto a form)?
Not only did the designer let me drag the button onto a design surface, but now it actually gives me a little more than an empty/default Button tag in my XAML. I actually get a sensibly configured button object, with a reasonable size and a preset label. Also notice that the upper pane is now labeled “Design”, rather than “Preview”.
But don’t weep yet. It gets better. You can actually left-click to select the button in the designer. When you do this, you’ll see that you can now actually set properties for the button in the property window.
Now you may weep or cheer, depending on your particular emotional reaction.
You’ll also notice that you can now click on the little event icon and then double-click to generate event handlers in your code-behind. (As opposed to using Intellisense in the XAML to discover relevant events).
This is great, although I still don’t understand why there is no dropdown in the properties window to select the individual controls. Is there a good reason why neither WPF or Silverlight applications allow selecting individual controls from the property window?
Also note that all of the above is possible in both Silverlight 2 and Silverlight 3.
Where Are We?
So clearly, Silverlight is now a full-fledged citizen in Visual Studio, with full tooling. This may not seem like much, but for anyone who works with Silverlight a lot, it will make a huge difference. Not to mention a much shallower learning curve for developers coming up to speed with Silverlight.
Mr. Socks Fox wasn’t spouting blibber blubber after all.
Installing Silverlight 3 with Visual Studio 2010 – Step by Step
A beta version of Silverlight 3 was released at MIX09 in March. Since a beta version of Visual Studio 2010 was also just released–in May–it makes sense to set up a Silverlight 3 and Visual Studio 2010 development environment. My last post included screenshots of the installation process for Visual Studio 2010. This post will cover installing the remaining bits needed for a Silverlight 3 development environment.
Note: Also take a look at the official Getting Started page for Silverlight 3.
This post will describe installing Silverlight 3 bits on top of a clean Windows 7 / Visual Studio 2010 environment. I won’t install the Silverlight 2 components, so the resulting environment will be targeted exclusively at Silverlight 3.
At the moment, the Silverlight 3 beta is targeted at Visual Studio 2008 SP1, rather than Visual Studio 2010. (See Tim Heuer’s blog post explaining this). What this means is that we can’t just run the Silverlight 3 Tools installer. If you try, you’ll get the following error.
Installing the Silverlight 3 Beta SDK
Instead, you’ll need to just install the Silverlight 3 Beta SDK manually. Once you download the SDK installer and launch it, you’ll get the following screen:
Then you get a license dialog. Note the comment about this beta license expiring 30 days after the commercial release of Silverlight 3, but no later than 30 Sep, 2009. Does this imply that we’ll see a final release of Silverlight 3 by 30 Aug, 2009?
If you do a custom install, you’ll see the following features and components listed:
Here’s a quick summary of what is being installed:
- Silverlight Tools – Components needed for building Silverlight applications
- The core Silverlight DLLs, e.g. agcore.dll, coreclr.dll, et al
- Build Components – Components used to build Silverlight projects
- Microsoft.Silverlight.Build.Tasks.dll, et al
- Client Libraries – Silverlight Client Libraries and Controls
- System.Xml.Serialization.dll, System.Xml.Linq.dll, System.Windows.Controls.Navigation, et al
- Server Libraries – Silverlight Server Libraries and Controls
- System.Web.Silverlight.dll, et al
Now we’re ready to install:
Install continues:
The install completes, and a dialog reminds us that the actual Silverlight 3 Beta runtime is not yet present. (Actually, there is an error in this dialog — it’s reminding us that the Silverlight 2 runtime is not present).
Installing the Silverlight 3 Developer Runtime
Now we need to install the actual Silverlight 3 runtime, which you can download from here.
We start with the familiar Silverlight install splash screen (now branded as Silverlight 3 for Developers).
Off we go..
The runtime install completes quickly.
Pretty simple. You now have all of the important stuff that you need for developing Silverlight 3 applications with Visual Studio.
Building a Silverlight Application with Visual Studio 2010
When you bring up the New Project wizard in Visual Studio, you’ll see two types of Silverlight projects listed:
- Silverlight Application
- Silverlight Class Library
If you create a new Silverlight Application, you’ll see the Add Silverlight Application dialog. But notice that there is now a dropdown labeled Silverlight Version. This defaults to Silverlight 2.0, but you can select Silverlight v3.0 to create a Silverlight 3 application.
You’ll see a similar dialog if you try to create a Silverlight Class Library.
The Silverlight Navigation Application
But notice that there is one Visual Studio template that shows up if you install Silverlight 3 Beta in Visual Studio 2008 SP1 that does not show up in Visual Studio 2010 — the Silverlight Navigation Application. This is installed as part of the Silverlight 3 Tools installer, which we were unable to run.
We need to pull this particular template from Visual Studio 2008 SP1 into Visual Studio 2010. To do this, install the Silverlight 3 Tools installer on a machine that is running Visual Studio 2008 SP1. Then fire up Visual Studio 2008, create a Silverlight Navigation Application project, and select Export Template from the File menu.
You’ll see a dialog asking you to select the project to export a template for. We’ll select the main navigation application.
You can also give the new template a description and select an icon.
When you’re done, a new Windows Explorer window will pop up, containing a .zip file for your new template. Now copy this .zip file to the following directory on your Visual Studio 2010 machine:
C:\Users\myname\Documents\Visual Studio 10\Templates\ProjectTemplates\Visual C#
Now when you bring up the New Project wizard in Visual Studio 2010, you’ll see a new template that you can use to create a Silverlight Navigation Application.
Wrapping Up
That should do it — you now have a fully functional Silverlight 3 / Visual Studio 2010 environment.
Technorati tags: Silverlight, Silverlight 3, Visual Studio 2010
Visual Studio 2010 Install Screenshots
Beta 1 of Visual Studio is now available on MSDN. (If you have the appropriate MSDN subscription). Here is a complete set of screenshots, outlining the installation experience.
Note: I installed VS 2010 Beta 1 on a clean virtual machine running Windows 7 Build 7100 (RC).
We start with the familiar install startup menu:
Then we get a banner page, as things start up.
Next, we get a license page, as well as an overview of what is going to be installed. The key components are:
- VC 9.0 and 10.0 runtime libraries
- .NET Framework 4 Beta 1 (more info)
- Help 3.0 Beta 1 (more info)
- Visual Studio Macro Tools
- Visual Studio 2010 Professional Beta 1 (more info)
Next up is an options page:
Now the actual installation begins and we can see a more complete list of all the components that will be installed. For completeness, here’s the full list:
- VC 9.0 Runtime
- VC 10.0 Runtime
- Microsoft .NET Framework 4 Beta 1
- Microsoft Help 3.0 Beta 1
- Microsoft Visual Studio Macro Tools
- Microsoft Visual Studio 2010 Professional Beta 1
- Microsoft Web Deployment Tool
- Visual Studio Tools for the Office System 4.0 Runtime
- Microsoft Office Development Tools for Visual Studio 2010
- Dotfuscator Software Services – Community Edition
- Microsoft SQL Server Compact 3.5 SP1
- SQL Server Compact Tools for Visual Studio 2010 Beta 1
- Microsoft Sync Framework Runtime v1.0
- Microsoft Sync Services for ADO.NET v2.0
- Microsoft Sync Framework Services v1.0
- Microsoft Sync Framework SDK v1.0
- Microsoft SQL Publishing Wizard 1.4
- SQL Server System CLR Types
- Shared Management Objects
- Microsoft SQL Server 2008 Express Edition
Wow. This is going to take a while.
You’ll have to reboot after the .NET Framework 4 installation.
Go get a cup of coffee while the remaining components install..
You’ll get a warning dialog, indicating that SQL Server 2008 has compatibility issues on Windows 7 and suggesting that you install SP1.
I just clicked the Run Program button and proceeded with the install. A little bit later, I got a second compatibility warning dialog, also mentioning SQL Server 2008. An external DOS window was also spawned, running a setup.exe command.
Finally, everything finishes up and we’re done!
After the install completes, we get the main autorun window again and the link for checking for service releases is now active.
If you click the Check for Service Releases link, you’ll be redirected to an update web page, which in turn allows firing up the Windows Update applet. When I tried this (29 Jun 2009), no updates were found.
Finally, we bring up Visual Studio 2010 for the first time.
As with earlier versions, when you start Visual Studio for the first time, you’re asked to choose a language, which dictates how the environment is set up. I’m a C# guy.
When things finally start up, we see the new Start Page for the first time.
The New Project dialog also gets a fresh look.
Finally, we create an empty WPF Application.
Keynote #2 – Ozzie, Sinofsky, Guthrie, Treadwell
PDC 2008, Day #2, Keynote #2, 2 hrs
Ray Ozzie, Steven Sinofsky, Scott Guthrie, David Treadwell
Wow. In contrast to yesterday’s keynote, where Windows Azure was launched, today’s keynote was the kind of edge-of-your-seat collection of product announcements that explain why people shell out $1,000+ to come to PDC. The keynote was a 2-hr extravaganza of non-stop announcements and demos.
In short, we got a good dose of Windows 7, as well as new tools in .NET 3.5 SP1, Visual Studio 2008 SP1 and the future release of Visual Studio 2010. Oh yeah—and an intro to Office 14, with online web-based versions of all of your favorite Office apps.
Not to mention a new Paint applet with a ribbon interface. Really.
Ray Ozzie Opening
The keynote started once again today with Ray Ozzie, reminding us of what was announced yesterday—the Azure Services Platform.
Ray pointed out that while yesterday focused on the back-end, today’s keynote would focus on the front-end: new features and technologies from a user’s perspective.
He pointed out that the desktop-based PC and the internet are still two completely separate world. The PC is where we sit when running high-performance close-to-the-metal applications. And the web is how we access the rest of the world, finding and accessing other people and information.
Ray also talked about the phone being the third main device where people spend their time. It’s always with us, so can respond to our spontaneous need for information.
The goal for Microsoft, of course, is that applications try to span all three of these devices—the desktop PC, the web, and the phone. The apps that can do this, says Ozzie, will deliver the greatest value.
It’s no surprise either that Ray mentioned Microsoft development tools as providing the best platform for developing these apps that will span the desktop/web/phone silos.
Finally, Ray positioned Windows 7 as being the best platform for users, since we straddle these three worlds.
Steven Sinofsky
Next up was Steven Sinofsky,Senior VP for Windows and Windows Live Engineering Group at Microsoft. Steven’s part of the keynote was to introduce Windows 7. Here are a couple of tidbits:
- Windows 7 now in pre-beta
- Today’s pre-beta represents “M3”—a feature-complete milestone on the way to Beta and eventual RTM. (The progression is M1/M2/M3/M4/Beta)
- The beta will come out early in 2009
- Release still targeted at 3-yrs after the RTM of Vista, putting it at November of 2009
- Server 2008 R2 is also in pre-beta, sharing its kernel with Windows 7
Steven mentioned three warm-fuzzies that Windows 7 would focus on:
- Focus on the personal experience
- Focus on connecting devices
- Focus on bringing functionality to developers
Julie Larson-Green — Windows 7 Demo
Next up was Julie Larson-Green, Corporate VP, Windows Experience. She took a spin through Windows 7 and showed off a number of the new features and capabilities.
New taskbar
- Combines Alt-Tab for task switching, current taskbar, and current quick launch
- Taskbar includes icons for running apps, as well as non-running (icons to launch apps)
- Can even switch between IE tabs from the taskbar, or close tabs
- Can close apps directly from the taskbar
- Can access app’s MRU lists from the taskbar (recent files)
- Can drag/dock windows on desktop, so that they quickly take exactly half available real estate
Windows Explorer
- New Libraries section
- A library is a virtual folder, providing access to one or more physical folders
- Improved search within a library, i.e. across a subset of folders
Home networking
- Automatic networking configuration when you plug a machine in, connecting to new “Homegroup”
- Automatic configuration of shared resources, like printers
- Can search across entire Homegroup (don’t need to know what machine a file lives on)
Media
- New lightweight media player
- Media center libraries now shared & integrated with Windows Explorer
- Right-click on media and select device to play on, e.g. home stereo
Devices
- New Device Stage window, summarizing all the operations you can perform with a connected device (e.g. mobile device)
- Configure the mobile device directly from this view
Gadgets
- Can now exist on your desktop even without the sidebar being present
Miscellaneous
- Can share desktop themes with other users
- User has full control of what icons appear in system tray
- New Action Center view is central place for reporting on PC’s performance and health characteristics
Multi-touch capabilities
- Even apps that are not touch-aware can leverage basic gestures (e.g. scrolling/zooming). Standard mouse behaviors are automatically mapped to equivalent gestures
- Internet Explorer has been made touch-aware, for additional functionality:
- On-screen keyboard
- Navigate to hyperlink by touching it
- Back/Forward with flick gesture
Applet updates
- Wordpad gets Ribbon UI
- MS Paint gets Ribbon UI
- New calculator applet with separate Scientific / Programmer / Statistics modes
Sinofsky Redux
Sinofsky returned to touch on a few more points for Windows 7:
- Connecting to Live Services
- Vista “lessons learned”
- How developers will view Windows 7
Steve talked briefly about how Windows 7 will more seamlessly allow users to connect to “Live Essentials”, extending their desktop experience to the cloud. It’s not completely clear what this means. He mentioned the user choosing their own non-Microsoft services to connect to. I’m guessing that this is about some of the Windows 7 UI bits being extensible and able to incorporate data from Microsoft Live services. Third party services could presumably also provide content to Windows 7, assuming that they implemented whatever APIs are required.
The next segment was a fun one—Vista “lessons learned”. Steve made a funny reference to all of the feedback that Microsoft has gotten on Vista, including a particular TV commercial. It was meant as a clever joke, but Steve didn’t get that many laughs—likely because it was just too painfully true.
Here are the main lessons learned with Vista. (I’ve changed the verb tense slightly, so that we can read this as more of a confession).
- The ecosystem wasn’t ready for us.
- Ecosystem required lots of work to get to the point where Vista would run on everything
- 95% of all PCs running today are indeed able to run Vista
- Windows 7 is based on the same kernel, so we won’t run into this problem again
- We didn’t adhere to standards
- He’s talking about IE7 here
- IE8 addresses that, with full CSS standards compliance
- They’ve even released their compliance test results to the public
- Win 7 ships with IE8, so we’re fully standards-compliant, out of the box
- We broke application compatibility
- With UAC, applications were forced to support running as a standard user
- It was painful
- We had good intentions and Vista is now more secure
- But we realize that UAC is still horribly annoying
- Most software now supports running as a standard user
- We delivered features, rather than solutions to typical user scenarios
- E.g. Most typical users have no hope of properly setting up a home network
- Microsoft failed to deliver the “last mile” of required functionality
- Much better in Windows 7, with things like automatic network configuration
The read-between-the-lines takeaway is we won’t make these same mistakes with Windows 7. That’s a clever message. The truth is that these shortcomings have basically already been addressed in Vista SP1. So because Windows 7 is essentially just the next minor rev of Vista, it inherits the same solutions.
But there is one shortcoming with Vista that Sinofsky failed to mention—branding. Vista is still called “Vista” and the damage is already done. There are users out there who will never upgrade to Vista, no matter what marketing messages we throw at them. For these users, we have Windows 7—a shiny new brand to slap on top of Vista, which is in fact a stable platform.
This is a completely reasonable tactic. Vista basically works great—the only remaining problem is the perception of its having not hit the mark. And Microsoft’s goal is to create the perception that Windows 7 is everything that Vista was not.
Enough ranting. On to Sinofsky’s list of things that Windows 7 provides for Windows developers:
- The ribbon UI
- The new Office ribbon UI element has proved itself in the various Office apps. So it’s time to offer it up to developers as a standard control
- The ribbon UI will also gradually migrate to other Windows/Microsoft applications
- In Windows 7, we now get the ribbon in Wordpad and Paint. (I’m also suspecting that they are now WPF applications)
- Jump lists
- These are new context menus built into the taskbar that applications can hook into
- E.g. For “most recently used” file lists
- Libraries
- Apps can make use of new Libraries concept, loading files from libraries rather than folders
- Multi-touch, Ink, Speech
- Apps can leverage new input mechanisms
- These mechanisms just augment the user experience
- New/unique hardware allows for some amazing experiences
- DirectX family
- API around powerful graphics hardware
- Windows 7 extends the DirectX APIs
Next, Steven moved on to talk about basic fundamentals that have been improved in Windows 7:
Decrease
- Memory — kernel has smaller memory footprint
- Disk I/O — reduced registry reads and use of indexer
- Power — DVD playback cheaper, ditto for timers
Increase
- Speed — quicker boot time, device-ready time
- Responsiveness — worked hard to ensure Start Menu always very responsive
- Scale — can scale out to 256 processors
Yes, you read that correctly—256 processors! Hints of things to come over the next few years on the hardware side. Imagine how slow your single-threaded app will appear to run when running on a 256-core machine!
Sinofsky at this point ratcheted up and went into a sort of but wait, there’s more mode that would put Ron Popeil to shame. Here are some other nuggets of goodness in Windows 7:
- Bitlocker encryption for memory sticks
- No more worries when you lose these
- Natively mount/managed Virtual Hard Drives
- Create VHDs from within Windows
- Boot from VHDs
- DPI
- Easier to set DPI and work with it
- Easier to manage multiple monitors
- Accessibility
- Built-in magnifier with key shortcuts
- Connecting to an external projector in Alt-Tab fashion
- Could possibly be the single most important reason for upgrading to Win 7
- Remote Desktop can now access multiple monitors
- Can move Taskbar all over the place
- Can customize the shutdown button (cheers)
- Action Center allows turning off annoying messages from various subsystems
- New slider that allows user to tweak the “annoying-ness” of UAC (more cheers)
As a final note, Sinofsky mentioned that as developers, we had damn well all be developing for 64-bit platforms. Windows 7 is likely to ship a good percentage of new boxes on x64. (His language wasn’t this strong, but that was the message).
Scott Guthrie
As wilted as we all were with the flurry of Windows 7 takeaways, we were only about half done. Scott Guthrie, VP, Developer Division at Microsoft, came on stage to talk about development tools.
He started by pointing out that you can target Windows 7 features from both managed (.NET) and native (Win32) applications. Even C++/MFC are being updated to support some of the new features in Windows 7.
Scott talked briefly about the .NET Framework 3.5 SP1, which has already released:
- Streamlined setup experience
- Improved startup times for managed apps (up to 40% improvement to cold startup times)
- Graphics improvements, better performance
- DirectX interop
- More controls
- 3.5 SP1 built into Windows 7
Scott then demoed taking an existing WPF application and adding support for Windows 7 features:
- He added a ribbon at the top of the app
- Add JumpList support for MRU lists in the Windows taskbar
- Added Multi-touch support
Scott announced a new WPF toolkit being released this week that includes:
- DatePicker, DataGrid, Calendar controls
- Visual State Manager support (like Silverlight 2)
- Ribbon control (CTP for now)
Scott talked about some of the basics coming in .NET 4 (coming sometime in 2009?):
- Different versions of .NET CLR running SxS in the same process
- Easier managed/native interop
- Support for dynamic languages
- Extensibility Component Model (MEF)
At this point, Scott also starts dabbling in the but wait, there’s more world, as he demoed Visual Studio 2010:
- Much better design-time support for WPF
- Visual Studio itself now rewritten in WPF
- Multi-monitor support
- More re-factoring support
- Better support for Test Driven Development workflow
- Can easily create plugins using MEF
Whew. Now he got to the truly sexy part—probably the section of the keynote that got the biggest reaction out of the developer crowd. Scott showed off a little “third party” Visual Studio plug-in that pretty-formatted XML comments (e.g. function headers) as little graphical WPF widgets. Even better, the function headers, now graphically styled, also contained hot links right into a local bug database. Big cheers.
Sean’s prediction—this will lead to a new ecosystem for Visual Studio plugins and interfaces to other tools.
Another important takeaway—MEF, the new extensibility framework, isn’t just for Visual Studio. You can also use MEF to extend your own applications, creating your own framework.
Tesco.com Demo of Rich WPF Client Application
Here we got our obligatory partner demo, as a guy from Tesco.com showed off their snazzy application that allowed users to order groceries. Lots of 2D and 3D graphical effects—one of the more compelling WPF apps that I’ve seen demoed.
Scott Redux
Scott came back out to talk a bit about new and future offerings on the web development side of things.
Here are some of the ASP.NET improvements that were delivered with .NET 3.5 SP1:
- Dynamic Data
- REST support
- MVC (Model-View-Controller framework)
- AJAX / jQuery (with jQuery intellisense in Visual Studio 2008)
ASP.NET 4 will include:
- Web Forms improvements
- MVC improvements
- AJAX improvements
- Richer CSS support
- Distributed caching
Additionally, Visual Studio 2010 will include better support for web development:
- Code-focused improvements (??)
- Better JavaScript / AJAX tooling
- Design View CSS2 support
- Improved publishing and deployment
Scott then switched gears to talk about new and future offerings for Silverlight.
Silverlight 2 was just RTM’d two weeks ago. Additionally, Scott presented two very interesting statistics:
- Silverlight 1 is now present on 25% of all Internet-connected machines
- Silverlight 2 has been downloaded to 100 million machines
IIS will inherit the adaptive (smooth) media streaming that was developed for the NBC Olympics web site. This is available today.
A new Silverlight toolkit is being released today, including:
- Charting controls, TreeView, DockPanel, WrapPanel, ViewBox, Expander, NumericUpDown, AutoComplete et al
- Source code will also be made available
Visual Studio 2010 will ship with a Silverlight 2 designer, based on the existing WPF designer.
We should also expect a major release of Silverlight next year, including things like:
- H264 media support
- Running Silverlight applications outside of the browser
- Richer graphics support
- Richer data-binding support
Whew. Take a breath..
David Treadwell – Live Services
While we were all still reeling from Scott Gu’s segment, David Treadweall, Corporate VP, Live Platform Services at Microsoft, came out to talk about Live Services.
The Live Services offerings are basically a set of services that allow applications to interface with the various Windows Live properties.
The key components of Live Services are:
- Identity – Live ID and federated identity
- Directory – access to social graph through a Contacts API
- Communication & Presence – add Live Messenger support directly to your web site
- Search & Geo-spatial – including mashups on your web sites
The Live Services are all made available via standards-based protocols. This means that you can invoke them from not only the .NET development world, but also from other development stacks.
David talked a lot about Live Mesh, a key component of Live Services:
- Allows applications to bridge Users / Devices / Applications
- Data synchronization is a core concept
Applications access the various Live Services through a new Live Framework:
- Set of APIs that allow apps to get at Live Services
- Akin to CLR in desktop environment
- Live Framework available from PC / Web / Phone applications
- Open protocol, based on REST, callable from anything
Ori Amiga Demo
Ori Amiga came out to do a quick demonstration of how to “Meshify” an existing application.
The basic idea of Mesh is that it allows applications to synchronize data across all of a user’s devices. But importantly, this means—for users who have already signed up for Live Mesh.
Live Mesh supports storing the user’s data “in the cloud”, in addition to on the various devices. But this isn’t required. Applications could use Mesh merely as a transport mechanism between instances of the app on various devices.
Takeshi Numoto – The Closer
Finally, Takeshi Numoto, GM, Office Client at Microsoft, came out to talk about Office 14.
Office 14 will deliver Office Web Applications—lightweight versions of the various Office applications that run in a browser. Presumably they can also store all of their data in the cloud.
Takeshi then did a demo that focused a bit more on the collaboration features of Office 14 than on the ability to run apps in the browser. (Running in the browser just works and the GUI looks just like the rich desktop-based GUI).
Takeshi showed off some pretty impressive features and use cases:
- Two users editing the same document at the same time, both able to write to it
- As users change pieces of the document, little graphical widget shows up on the other user’s screen, showing what piece the first user is currently changing. All updated automatically, in real-time
- Changes are pushed out immediately to other users who are viewing/editing the same document
- This works in Word, Excel, and OneNote (at least these apps were demoed)
- Can publish data out to data stores in Live Services
Ray’s Wrapup
Ray Ozzie came back out to wrap everything up. He pointed out that everything we’d seen today was real. He also pointed out that some of these technologies were more “nascent” than others. In other words—no complaints if some bits don’t work perfectly. It seemed an odd note to end on.
-
Archives
- January 2010 (1)
- July 2009 (1)
- June 2009 (3)
- May 2009 (1)
- April 2009 (3)
- March 2009 (3)
- February 2009 (2)
- January 2009 (7)
- November 2008 (7)
- October 2008 (19)
- September 2008 (4)
- August 2008 (4)
-
Categories
-
RSS
Entries RSS
Comments RSS





































































