Schwieb

Shortly after the MacBU released Office 2008 SP1 yesterday, we started to receive reports that the update caused the Office Setup Assistant to launch every time, instead of their desired Office application. We started looking into it right away, and found that in nearly every case, the problem happens when users are running Office 2008 with an expired product license key.

When Office 2008 was released in January, all of the keys used in our private beta program expired, but it wasn’t until the SP1 update that we added code to enforce the expiration. While we communicated to all of the users in our beta program that their license keys were going to expire when the product became publicly available, one of the beta versions did escape onto the Internet in November and we didn’t know who was using it. During our work yesterday we found that some of our users installed their retail copy of Office 2008 over that beta version and ended up running the final release of Office with the beta key.

Our testing and user assistance team scrambled today and have put a new help topic about the problem up on Mactopia, along with another link to how to remove the old product key information and re-enter your valid key. This is about the fastest we’ve put up new help content — about 26 hours from first report of the problem to active help content!

Also, the English and Japanese versions of the SP1 update are now live in the Microsoft AutoUpdate tool, so rather than finding them on Mactopia for manual download, you can simply go to the Help menu in your favorite Office 2008 app and select “Check for Updates”. The autoupdaters for the European languages should be available soon.

Lastly, we actually put up a very minor revision to the SP1 installer today. The new package has a fix so that the update can actually be deployed via Apple Remote Desktop or via the command-line. If you want to deploy SP1 via ARD and downloaded the update yesterday, please redownload it. If your install is already done and working, there’s no need to redownload and reinstall the update — the fix was in the installer only, not in any of the actual application bits.

It’s finally here! The MacBU has just released Service Pack 1 for Mac Office 2008. You can download the update directly from the Mactopia website (it’s large — about 180 MB), or launch your favorite Office app and select Help/Check for Updates. There are well over 1000 fixes and improvements in this release, including the return of custom error bars and axis tick manipulation in Excel charts. The full release notes are available online as well, so go check them out to see if we fixed your personal pet peeve.

I’m particularly excited to see this update go live, because it’s been the project consuming most of my time for the last several months. Shortly after we shipped released Office 2008 to manufacturing in December 2007, my manager asked me if I’d be willing to act as the development lead for the SP1 project. I agreed, and have spent many hours working on the project since we kicked it off in early January. Since our fine UA department has already written up the list of highlighted changes, I thought I’d spend a little time today describing how we approached SP1 and how we did the work.

First off, while I was the development lead for SP1, I most certainly cannot take any majority of the credit. SP1 was a MacBU-wide effort, with significant contributions from every single developer, tester, program manager, content writer, lab engineer, builder, and all the other disciplines I’m forgetting at the moment. I am incredibly thankful for all the hard work that everyone around me did.

So, why SP1, and why now? Well, it’s no great secret that we released Office 2008 later than our original plans intended. Even after that delay, there was a decent list of issues in the product that were postponed during the original release cycle that we knew we wanted to fix, so we knew that we had to plan for an update sometime in 2008. Mac Office 2004 was first released in May 2004, and its first service pack came out in October 2004, about 5 months later, and that’s pretty much the same schedule we came up with for Office 2008. In addition to fixing the issues we know about internally, we like to have a few months of real user data in hand (crash reports, newsgroup/forum postings, etc) that help us to identify problems that we didn’t know about. I’ve been spending a bunch of time in Ars Technica’s Macintoshian Achaia forum over the last year or so, and have received a number of good bug reports from particpants there. (In fact, we have a ‘SWAT’ team of folks in the MacBU who participate in a whole variety of forums across the net.)

Anyway, the entire MacBU began development and testing work on 2008 SP1 in January. Initially, teams pretty much just took their list of issues postponed from the regular release and started fixing those bugs. Our test team once again dove into the product and found more issues that needed fixing, and we started to collect MERP logs (Microsoft Error Reporting Program — aka the dialog you see when an Office app crashes) from the wild. Devs took all those bug reports and began working on classifying them by severity and importance, and then started fixing them.

Like any release, however, there needs to be a modicum of control applied to the whole process. If everybody just keeps on checking in fixes, the product can actually end up being less stable than before. The Office codebase is large, and code changes in one part can have unintended consequences somewhere else, so we don’t let code churn run on forever. Many teams at Microsoft (and, I’d imagine, at other large software companies) have instituted ‘triage’ for bugs.

When we triage bugs, it basically means that we take a look at all the aspects of a bug before deciding whether to accept a fix it:

1. How bad is the bug? (Is it a crash? corrupted file? data loss? simple redraw glitch?)
2. How hard is it to encounter the bug? (every time on boot? Only when saving? On Feb 29? Only when dragging a shape across a page boundary when the page is in PubLayoutView and the shape has a semitransparent shadow and the document has never been saved?)
3. Can the user work around the bug? (use the mouse instead of the keyboard?)
4. How complicated is the fix? (simple typo (= instead of ==) or re-architecture of entire function?)
5. Where is the fix? (in the middle of Excel’s recalc engine? Or for populating a single popup menu in one dialog?)
6. How close are we to shipping? (Months, weeks, days?)

All of these factors come into play, and some combination of the magnitude of each of these leads to a decision of whether to fix a bug or not. It can get pretty complicated, and much of it comes down to a gut decision (although we try to collect hard data when we can, like ‘exactly how many MERP reports do we have of this one bug?’) In January, when we were 4+ months away from shipping SP1, pretty much any bug was allowed to be fixed. In April, when we were trying to lock down the code and minimize code churn in order to keep the product stable, we punted a known crashing bug because although the impact of the bug was large, the fix was a little complicated and the testing team didn’t think they could verify that the code change had no unintended side effects with the amount of time left before shipping.

So, what was my role in all this as development lead for SP1? I worked closely with one of our Program Managers and one of our Test Leads as the three-disciplined Sustained Engineering Lead Committee (I have no idea if we had some formal name, so that’s what I will call it here.) Scott, Pat, and I set the product schedule (kickoff, first day of triage, code-complete, zero bugs, release candidate target, etc) and acted as the final arbitrators in daily triage meetings, putting our roughly 33 (ok, now I feel old) combined years of software development experience to use. Mostly that meant that as teams brought their bugs to the triage meetings, we asked them about the above list of questions and tried to get a sense of how each bug fit in importance. We were responsible for using that information to ‘raise the bar’ each day/week — making it harder for bugs to qualify for fixing. That sounds somewhat anti-quality or antithetical to the purpose of a service pack, but actually it is a very important part of ensuring that we ship a high-quality, stable product for our users. It can be very hard to say no to a bug, particularly when people really are passionate about the specific problem or user scenario, but someone has to do it. The three of us all made a final call on each bug, and I think I tended to be the most hard-core about locking things down. Toward the end, a few people jokingly (at least, I hope they were joking) called me “Dr. No.”

As I said at the top, there are over 1000 fixes in SP1, including the re-addition of some features that were glaringly absent when compared to Office 2004. That doesn’t mean Office 2008 is now perfect — I know we haven’t fixed every bug in the product, and some folks are bound to note that we haven’t fixed some of the bugs they are most frustrated by. However, I hope you’ll agree that this update shows that I and the rest of the MacBU are committed to this product and to its future.

Update: I added a new post the other day about some installation problems people have been running into with SP1. If you are having difficulties with SP1 apps, please take a look and see if it helps you.

How does that old Chinese proverb go? “May you live in interesting times!” I have no idea how accurate it is, or whether it is a positive blessing or a curse, but I really do live (and work) in interesting times.

Almost two years ago, back at WWDC in August 2006, the MacBU announced that Office 2008 would not have support for Visual Basic. I blogged about it at the time, and that one post has proven to be my 15 minutes of Internet fame. It continues to be the most popular post on my site — 21 months later, it still accounts for almost half of all the hits I get each week. While most of our customers don’t require the cross-platform scripting enabled by VBA, a section of the Mac community spoke out very vocally against our decision, and I still hear echos of it to this day. At the time, I wrote about the challenges we faced in bringing it forward with the rest of Mac Office 2008 and why we ended up deciding to remove the feature, but while some people understood or at least accepted the details, some in the community did not. I’ve been told that we must have cut VB to intentionally drive users to use virtualization and Windows Office 2007 on Macs, or that we were ordered by upper Microsoft management to slowly kill the Mac, or any one of a zillion other “Microsoft is evil” conspiracy theories. None of these theories are true, but it’s rather hard to prove that, except by deeds.

This isn’t a done deed yet, but I’ve got a new commitment for you. Quoting from a press release that went out from the MacBU at 12:01am PST today:

VBA Returns to Future Versions of Office for Mac

The Mac BU also announced it is bringing VBA-language support back to the next version of Office for Mac. Sharing information with customers as early as possible continues to be a priority for the Mac BU to allow customers to plan for their software needs. Although the Mac BU increased support in Office 2008 with alternate scripting tools such as Automator and AppleScript — and also worked with MacTech Magazine to create a reference guide, available at http://www.mactech.com/vba-transition-guide — the team recognizes that VBA-language support is important to a select group of customers who rely on sharing macros across platforms. The Mac BU is always working to meet customers’ needs and already is hard at work on the next version of Office for Mac.

Yep, you read that right. VB is (well, will be) back, baby! When we came to the realization in 2006 that there was no way for us to keep VB in the product and still ship Office 2008 on any semblance of the schedule we wanted, we announced its removal, but kept looking at how to bring it back into the suite even before we shipped. Many of the technical challenges I wrote about then still remain, but for a while now I and several others have been working with a group of people who know a heck of a lot about the internals of VB, and once we determined that we could achieve the revival VB in the new schedule for the next version of Mac Office, we locked it into place on the feature list.

Personally, I think it’s really cool that we’re announcing this now. For all the wringing-of-hands and gnashing-of-teeth in the Mac community over the lack of VB, Mac Office 2008 has been selling really well (Craig Eisler, our General Manager and all around cool-boss-guy, said “The response has been amazing — since we launched in January, the velocity of sales for Office 2008 is nearly three times what we saw after the launch of Office 2004″ in that same press release) which seems to indicate that most of our users don’t find the lack of VB to be a major issue. I think our management is confident enough in our ongoing sales of Office 2008 to tell you about something very significant in the next version, even if that defers some sales to that next version. Based my own experiences talking with people in various Internet forums, I don’t think too much of that will happen, though. And if you were wondering, the delta between Office 2004 and 2008 was longer than we normally expect between versions, so my understanding is that this next version will be available somewhat sooner than 2012 (I can’t give any specifics at this time, however.)

So, if you have a dire need for Visual Basic, you can continue to run Mac Office 2004 (it will even run side-by-side with Office 2008) and we’re publicly committing to VB as good (maybe even better, if things go well) in the next version. My team is responsible for that reintegration, and I’ve been meeting frequently with a number of people as we’ve planned exactly what we’re doing and how we’re bringing VB back. This seems to me to be a strong example for the MacBU naysayers that we’re really listening to what all of our users want, and that we’re most definitely not slow-marching to some bagpiper’s funereal drone!

I’m excited to be able to blog about this now, after almost two years of keeping my lips zipped, and I can’t wait until we reveal everything else about the next version of Mac Office. In the meantime, let me ask you something. What parts of the Visual Basic experience are most important to you? The IDE? Macro UI, such as dialogs? Object model parity between Mac Office and Windows Office? (and if so, which features in the Windows object model do you most want brought to the Mac?) Or something else altogether? I can’t promise to achieve anything in particular, but I’d love to hear how we might be able to improve upon the 2004 VB experience for you.

(Made a few edits this morning, and added a link to the press release.)

Well, the nerve, it’s not so good. I had an MRI last week and saw Dr. Peter Nora for a neurosurgical consult on Monday. There’s no immediate damage or need for surgery, but the MRI showed a definitive herniation at L5-S1 (not my personal MRI, but a decent example of one like mine), just like I’ve had twice before. Dr. Nora strongly recommended I take several weeks to minimize prolonged periods of sitting and standing, to take pressure off the disk and give my body a chance to solve the nerve irritation on its own.

That’s a great idea, but what about work? I’m still quite mentally fit (aside from the foggy effects of taking Percocet to dull the pain) and didn’t relish the idea of spending 3 weeks staring at the ceiling. Luckily, Microsoft has a great HR and benefits team, and I have an understanding manager (who happens to be a long-time friend and is actually the very first person I met at Microsoft on my first day as an intern in 1995!). Together with my general doctor, we crafted a formal ‘accomodation’ plan that acknowledges my limitations and still allows me to work from home part-time (and account for the rest of my time with sick leave). This way I get to be productive, keep my mind off of my back, and yet not stress my system with long commutes or hours sitting at my desk. I’ve got a laptop at home and can use Apple Remote Desktop to drive my Mac Pro at work, and thus can do pretty much anything from my bed that I could do at work.

The one tricky thing is that as a development lead, I have several people who report to me, and I need to be able to meet with them on a regular basis. Handily enough, between the new A/V capabilities of Microsoft Messenger 7 and the nice corded mic on my cell phone, I can attend meetings and talk to all my direct reports face to face. I did a number of one-on-one meetings that way today, and it seemed to work rather well.

So, I’m spending my days lying on my nice comfy bed with a couple of pillows and a freaking hot MacBook Pro. Not exactly where I’d like to be, but given the circumstances, I’ll take that over a stay in the hospital or a blah view of my ceiling. And, *knock on wood*, with any luck I’ll avoid a third surgery and be physically back in the office soon.

We’ve just launched the Mac Office 2008 Sneak Peek site, with short video clips and descriptions of a bunch of new features in Mac Office 2008. The video clips are a little small, but they should give you a good idea of the new UI (more adoption of common OS X UI elements, extensive use of Core Graphics) including the new Elements Gallery and some Word and Excel features. Nadyne has just put up some commentary on how the design of the Elements Gallery evolved out of the Win Office ribbon and some of our own internal User Experience testing. Some of the other folks I work with in the MacBU will be posting to Mac Mojo over the next few days talking about their work in designing, developing, and testing the new capabilities.

On a more personal note, I’ve not posted here in a very long time. As you might imagine, I’ve been very busy at work over the last several months, with more to do before Office 2008 becomes available in January. Instead of blogging, I’ve been spending my free time at home playing with my kids and doing small fixit projects (I replaced two faucets over the weekend so that my son could reach the handles and turn on the water by himself.) I do hope to write more regularly soon.

So last night was the Bill & Steve confab at the All Things Digital conference. It was a pretty mellow discussion as they go (although apparently contrary to popular opinion, BillG is not Fake Steve!)
Both Bill and Steve made some nice comments about the MacBU. Check out this link from roughly 2:35 to 3:05.

I’ve talked about the relationship that the MacBU has with Apple developers before, and it’s nice to hear Steve himself say that “it’s one of our best developer relationships.”

At MacWorld 2007 this past January, Apple released their new 802.11n Airport Extreme Base Station with support for sharing a USB hard drive. Since that release, we’ve seen a few reports here and there that Mac Office 2004 applications are unable to save files to such a shared disk. One of my colleagues had run into the problem at home and reported the bug internally here as well, and it ended up on my plate.

I obtained a new AEBS from our lab and set it up in my office. I rebooted my Intel iMac into Tiger, applied all the recent security updates (that Mac has been running Leopard seeds for a while, so the Tiger partition was a little out of date) and installed the new AEBS software. I then booted up Office 2008 (since that’s easier to debug right now) and tried to reproduce the problem. No luck — Excel and Word both had no problems saving to the wirelessly-mounted disk drive. So, I tried Office 2004. Again, it just worked! So, I sent the bug back to my colleague saying I couldn’t reproduce the problem.

Today, he brought his own AEBS in from home and we tested it. Sure enough, we could reproduce the problem on his AEBS. So, we pondered the problem for a little while and realized that when I set up our lab’s AEBS the other day, the first thing I did was update the AEBS firmware as prompted when I first ran the Airport Utility tool. Comparing the two AEBSs showed that the one I set up was using firmware v7.1, whereas my colleague’s was using v7.0. A quick update of his AEBS and a new test, and the problem went away!

I then dug around on Apple’s web site and found the release notes for the new firmware update. Lo and behold, the new firmware says that it has “improved support for third party applications saving files to a USB disk.”

So, if you are having problems saving files from Office 2004 applications to your new whiz-bangy Aiport Express Base Station, go to your Airport Utility and check to see if you have the latest AEBS firmware. Your Office installation will thank you (or at least, save your files…)!

After my posts this past August about the removal of VB from Mac Office 2008, lots of people asked about how to convert VB code into AppleScript. I had always intended to write up a post with some simple examples but never actually found the spare time to do so. However, Paul Berkowitz, along with the help of some other stellar Microsoft MacBU MVPs has written an excellent tutorial with some concrete and very relevent examples of VB macros and their AppleScript equivalents.

MacTech Magazine announced on Wednesday that their upcoming April 2007 issue will contain the entire 150-page book! I saw a slightly-pre-release copy of the book at MacWorld and I think it will be an excellent reference/HowTo for anyone who has created custom solutions in VB for the Mac.

I know this doesn’t address the cross-platform issues surrounding VB but it should give you some ideas of the richness of AppleScript and our support for it in Mac Office 2008.

I got back to Seattle on Thursday night, only to find that I couldn’t actually get all the way home due to ice on the roads. I had to park my car a block and a half away in a nearby parking lot because the snow (!) that fell on Wednesday had been packed down and subsequently frozen into a solid sheet of ice. What is with this year’s weather anyway? Snow, ice, wind, torrential rain, gale-force winds, more snow, more ice — what’s next?!

Anyway, as far as work goes, MacWorld was pretty good this year. I met a number of interesting folks in the Microsoft Blogger Lounge and answered a ton of questions over at the main Microsoft booth. Apparently I’m a “docile developer” — I’m glad that Brandon liked the personal tech support. On Tuesday evening I got to chat with Jacqui Cheng of Ars Technica at the Microsoft Press Party. Apparently Jade had wandered off to someother event so I didn’t get to experience the full snark effect, but Jacqui and her friend Herschell (sp?) were quite pleasant to talk to. I’ve been following a few threads on the Ars Macintosh forum, where a few commenters insist on dragging the MacBU through the mud as often as they can (and you can see a few of their comments on some of my other posts here). Somehow Jacqui and I got to talking about the perceptions you get as you scan people’s comments. So many of them are negative that it is easy to get kinda down about blogging. I mean, who really wants to share some personal insights only to get cursed out all the time? It’s a little odd, but most of the positive comments I get are sent to me in private email, whereas the people who have some issue or complaint about me or the MacBU usually post public comments (dare I call them diatribes, at times?). Jacqui said she’s noted the same thing with her columns on Ars. I wonder why that is? Are there any human behaviorists reading this who care to hazard a guess?

On Wednesday at the Blogger Lounge I spent a long time talking with Eric Albert, a former Microsoft employee (although not with the MacBU) who’s now been involved with development on both the Intel Macs and the new iPhone. We chatted about the development of Xcode, including his perceptions of how easily 3rd party (ie, non-Apple) developers would be able to switch their codebases to it (hint — not as easily as Steve Jobs said!) and the various experiences we’ve both had with various chip and system architectures. I asked him about working on the iPhone, and aside from the normal “I can’t tell you that” sorts of stuff, it sounds pretty cool. He had some funny anecdotes to share about the secrecy involved, including having to stand guard around the demo model with his coat flared out for privacy at 5 or 6am the morning of the keynote as someone else ran through the demo to ensure it worked! (Here you can see Eric chatting with Nadyne and myself. I’m in the center wearing black with the yellow Office logo all over my shirt, Nadyne the red-haired woman to my left, and Eric is facing us wearing a grey shirt.)

Oh, and I’d like to welcome all you Macintouch and MacFixIt readers — it seems that my post on VB is making the rounds again. I guess that will be my 15 minutes of Internet fame, doled out in little bits a month or so at a time. Some of the comments I’ve seen recently about Office 2008 wonder why we didn’t demo much in the booth at MacWorld. I’m not in any position to answer that, but I do know there’s a lot more to Office 2008 than you’ve seen. There are a bunch of screenshots that show visuals for features we haven’t demoed publicly yet. By the way, all those rows of buttons in the Elements Gallery collapse — they are only expanded while you are working in the EG, so it doesn’t take up so much screen real estate on a permanent basis. I’ve asked some folks in MacBU to get a screenshot of the default state so you can see the difference. In the meantime, AppleInsider has a few rough camera shots from our booth demo that show the EG in a collapsed state.

So beyond all that, what’s up? Lots more coding at work. My manager and I got a large new chunk of code to link on Friday that we’ve been working on for several weeks, and that removes the block on the Excel converter work I’m scheduled to do next. I’ve got some work to do on integrating Cocoa nibs into our localization process, so that we can apply localization transforms to them automatically, rather than doing them by hand each time the English nib changes, which in turn lets us autogenerate a complete localized build every day (something that we haven’t had working for the internal builds yet this cycle, yeesh!)

Ok, I’d better go to sleep so I can get something done tomorrow. If you hear me whistling on the bus tomorrow morning, say hi!

I’m sitting in the Microsoft Blogger Lounge on the MacWorld show floor as I write this. I missed the SteveNote today as I was somewhere around 35,000 feet over Oregon as the show was going on, but it sounds like some neat gadgets were revealed today. Too bad I don’t use Cingular as my cell phone provider…

Anyway, the big news for MacBU today was our announcement of Mac Office 2008. (Finally, I can stop calling it “the next version of Office” all the time!)

There’s a couple of screenshots over on Ars Technica (along with some good old Charles Jade commentary — I see he had fun tlaking to Geoff) and MacFixit has a short writeup as well.

Please let us know what you think. There’s still more to come; we’ve got converters coming out in beta in a few months, as well as more information on new Office 2008 features in the months leading up to our release in the 2nd half of this year.

I spent a little while at the main Microsoft booth today. One person asked me about VB and another about file converters, but most of the questions were about things that users didn’t know they could do in Office 2004. It’s always nice to be able to show someone how to solve their problem on the spot!