If you’re the type of person who likes to test-drive the latest and greatest software (or you’re the type of person who reads an Office Engineering blog…), then you’re probably familiar with the pain that can be part of trying out new software for the first time. My name is Paul Barr, Lead Program Manager for the Click-to-Run team in Office 2010, and we’ve built Click-to-Run with you in mind. What follows is a more in-depth post on the technology introduced in the New Ways to Try and Buy Microsoft Office 2010 announcement.
Delivering rich programs like Office over the internet hasn’t changed much in the last decade. Sure, we have self-extracting executables, securely signed files, and download managers, but all of these fall short of solving what we think are the biggest problems with downloading and installing large applications:
What is Click-to-Run?
Click-to-Run is a new software delivery mechanism built by the Office product team. It’s based on core virtualization and streaming technologies from the Microsoft App-V team in Cambridge, MA. Click-to-Run is optimized for home users on broadband connections (at least 1Mbps), and there are three key pillars of the investment:
Click-to-Run products also take up about half the disk space of normal products, they repair more completely, and they won’t break other software installed on the PC because they have private copies of all of their files and registration.
Click-to-Run is not a new Office “product”, it’s a new way of delivering and updating the products with which you are already familiar. Click-to-Run delivery is available for both the Office Home and Student 2010, and Office Home and Business 2010 products. It has full language support, and will work on both 32-bit and 64-bit Operating Systems (although only the 32-bit version of Office is actually run on both platforms).
How does Click-to-Run work?
Products delivered via Click-to-Run execute in a virtual application environment on the local Operating System. This means that they have private copies of their files and settings, and that any changes they make are captured in the virtual environment. The effect is they don’t end up modifying any other software installed on the System. With few exceptions, only user data actually passes through the virtual environment to the local System. Click-to-Run users may notice that they have a virtual Q: drive on their PCs, this is the virtual file system used by Office.
Click-to-Run products also support streaming. Think of this in the same way you think about streaming video. You get to watch the first part of the video before the entire file downloads. With Click-to-Run, users can start using their Office programs before the entire suite or product has been downloaded, enabling them to get to work much faster. While the user is running their application, the rest of the products are being downloaded in the background. The initial installation process is very different than what users may be used to. The experience of getting Click-to-Run Office is more like downloading a big web control than doing a traditional Office install:
If a user tries to use a feature or application that is not yet downloaded, Click-to-Run retrieves the required functionality from the internet immediately. In this case, the application may pause briefly, and users might see an experience like the below:
Users can see the current progress of the product download by launching the Click-to-Run Application Manager in Windows Control Panel:
Once fully downloaded, the product is cached locally, and users are free to disconnect from the internet and continue using their Office products:
Click-to-Run in the Office 2010 Beta and beyond…
Users will see that the Office Home and Business 2010 Beta product is available to download using the Click-to-Run technology. This option is optimized for high bandwidth connections (low bandwidth users should download the Office Professional 2010 Beta). When Office 2010 releases, Click-to-Run delivery will be available for a wider range of Office products. Users who download an Office 2010 product using Click-to-Run delivery also have access to the “normal” self-extracting version, as well as the native 64-bit version if those better suit their needs.
Home users may notice that a handful of things behave differently when using a Click-to-Run version of the Office 2010 products. For instance, there is a Click-to-Run specific destination in the Backstage for each application in the product. This section gives details about the status of applied updates, and links to more information about Click-to-Run:
It’s also possible that users will notice that some add-ins, or other integration points with the Office client, behave differently or are broken when using a Click-to-Run product. The vast majority of these will have no issues. All macros, in-document automation, and cross-Office application interoperability work fine. But sometimes the Office product group must make changes that cause some integrated solutions to require updating (building 64-bit versions of the applications is another good example of this). In some cases, add-ins might have trouble locating the Click-to-Run Office products on the machine, or they might have issues communicating with Office products when they are running in the virtual environment.
We expect these issues to be limited in scope. You will see more from us on how to resolve these both for users, and developers that wish to extend Office. In the Beta timeframe, if you are a developer, or are having issues with an add-in that you believe is compatible with Office 2010, you may want to obtain the Professional version of the Office 2010 Beta.
Wrapping it up…
As you’ve seen through the other posts on this blog, the Office 2010 rich clients bring a great new set of features and functionality to users. Click-to-Run is about getting that value into the hands of users easier, faster, and safer than ever. We’re very excited to pioneer the next generation of software delivery over the internet, and we look forward to your feedback.
<P>I've been impressed in general with the Office 2010 blogs, but this one is so good that I need to finally say something. Great job!</P>
<P>Looks awesome. Is this technology going to be available for companies to host themselves for company wide deployments? When can Technet/Connect folks expect the Beta to arrive?</P>
<P>Keep up the good work, Office 2010 looks better every day!</P>
<P>i would like to try office 2010</P>
<P>let try office 2010447</P>
<P>The first Technical Preview release of click to run worked well but the applications took a little too long to start up.</P>
<P>Hopefully the public beta version 14.0.4622.1000 will have increased application startup times.</P>
<P>Now where do we go to download this latest build?</P>
<P>Ooops typo...that should be decreased application startup times. I.e. faster startup times.</P>
<P>Thanks for the comments folks. </P>
<P>Dave: Similar (although not identical) functionality will be available for Enterprise customers using Microsoft App-V to deploy Office 2010. Look for more info specifically on this topic when Beta releases.</P>
<P>Des: Thanks for the positive feedback on the Technical Preview build. If you liked that, you will be amazed by the progress in the coming Beta. Application boot and runtime has improved tremendously.</P>
<P>I like automatic updates in the background. If there is a problem with an update, will there be an automatic removal of the update until the problem can be fixed?</P>
<P>Will Click-to-Run Office 2010 Home and Student run in XP SP3? [Asking for relatives who still run XP.]</P>
<P>Another thing that is positive with the Click-to-Run delivery / virtualization is side-by-side compatibility with older versions of Office. That gives us more time to migrate. We can quickly zip back to 2007 to get something done quickly that we are not up to speed on in 2010.</P>
<P>Thanks for all the work on the 2010 TP, beta and click-to-run.</P>
<P>vanilla / sharon</P>
<P>just making sure i understand this, when you run office (click to run) it downloads the main parts of office and after that it fetches other parts as the user needs them.</P>
<P>are they downloaded to the C:\program files\office directory or are they temp files that may be deleted over time and need downloading again?</P>
<P>Paul, does this form of application installation require admin rights ?</P>
<P>The downloaded bits are available only to the current user or also other users on the machine?</P>
<P>Isn't it like JLNP for Java? </P>
<P>The idea can be interesting for trials, but in a day to day work, the app have to start-up in a flash. And what about having multiple instances because you are working on several documents/presentations at the same time?</P>
<P>With time, we'll probably see of far and easy this can be.</P>
<P>My 2 cents</P>
<P>I don't really see the benefit of this. Sure installing the full version of Office takes a little while, but how often do you do it? I would guess most people do a full install less than once per year.</P>
<P>I'd rather take the time to do a full install once and not have to worry about whether the feature I now want to use is already installed or not.</P>
<P>In the end, it's just the difference between taking the time to do a full install once or taking the same amount of time to do little installs bit by bit. It seems much less disruptive to do it all at once.</P>
<P>I was wondering if there is an official date yet for the beta?</P>