If you have several machines that you want to install the Windows Phone 7 Series developer tools on and don’t want to have to wait for the download on each machine, here’s a little tip for how you can make yourself an “offline” installer:

1. Start with a clean Win 7 machine.

2. Download the web installer (vm_web.exe) from Microsoft and save it to a folder of your choice (let’s say C:\WinPhone7). Start the install.

3. Let the download happen, but when the install itself starts, temporarily cancel it (you can let it finish after step 5).

4. Go to %Temp% using Windows Explorer.

5. Copy the folder 30128.39 to your folder of choice from step 2.

6. Create a Install_WP7_Tools.cmd file containing the following:

xcopy 30128.39 %temp%\30128.39 /I /E
vm_web.exe
pause

7. Copy the folder of choice to a USB storage device.

8. Use the Install_WP7_Tools.cmd file on your other systems. The tools should install and skip most of the downloads quickly.

If you don’t start with a clean Windows 7 machine, the files that the vm_web.exe tool collects in the 30128.39 folder may not contain all the files needed for the install, so you may see a few things extra get downloaded while using the .cmd file on other machines.

On my clean 64-bit Windows 7 machine, I got the following files as part of the toolset:

C:\WinPhone7\30128.39\1033\VM_EXP\Ixpvm.exe
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\dotnetframework\dotNetFx40_Full_x86_x64.exe
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\help\HelpSetup_x64.exe
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\mtpack\NetFx_DTP.cab
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\mtpack\NetFx_DTP.msi
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\rdbg\vs_expbsln_x64_enu.cab
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\rdbg\vs_expbsln_x64_enu.msi
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\silverlight4\Silverlight.4.0_Developer.exe
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\silverlight4\Silverlight4_Tools.exe
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\silverlight4\silverlight_sdk.exe
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\vcruntimes\x64\vc_runtime_x64.cab
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\vcruntimes\x64\vc_runtime_x64.msi
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\watson\dw20shared.msi
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\windowsphone\sde_xde64-enu.cab
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\windowsphone\sde_xde64-enu.msi
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\windowsphone\vs_sdeprolightup-enu.cab
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\windowsphone\vs_sdeprolightup-enu.msi
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\windowsphone\WindowsPhoneDeveloperResources.msi
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\windowsphone\WindowsPhoneExtensions.msi
C:\WinPhone7\30128.39\1033\VM_EXP\wcu\windowsphone\XNAGS40_setup.exe

A total of about 320 MB.

If you see me at PDC, say hi, and I may be able to hand you one of these puppies. I only have a limited supply, though. 15 to be precise.

Check out the pictures:

Front of the card

Back of the card

Back of the card with USB memory stick flipped open/out

Front of the card with USB memory stick flipped open/out

(Someone was cleaning up a bunch of old floppy disks at work. I happened to come across them because I needed a floppy for updating the BIOS of a really old laptop.)

Just an interesting little factoid for your geek trivia…

My computer runs backups over night (I use MozyHome), which shouldn’t be a problem, really. But as part of the backup, a volume shadow copy snapshot is made, and this step caused the blue screen error.

In addition to adding a SATA controller, I had also bought a bigger hard drive to hold my ever expanding collection of pictures, vacation videos, etc. When I installed it, I cloned the old drive (which was a PATA drive) to carry all the information forward onto the new drive.

Apparently, after you install a cloned a hard drive, some information is retained on the system about the old drive, and this affects volume shadow copies.

I had to go to Device Manager and turn on “Show hidden devices”:

Then, under Storage Volumes, I had to delete one in particular that seemed to have gotten a corrupted name (something like Generic Volume□□□ [not shown in this screenshot, since it’s fixed now]):

Just for good measure I deleted all of them (although they didn’t seem to really disappear), ignoring the request to reboot after each prompt to do so.

When I was done, a couple of reboots of Windows recreated the necessary information about these volumes from the (old and new) hardware. After that the volume shadow copy snapshots no longer failed and I was able to run my backups without blue screen errors.

Credits for this find go to the folks in this thread: http://www.techspot.com/vb/topic94820-2.html

Now Microsoft has published special early upgrade pricing to entice people to rush out and get Windows 7 “while supplies last”. And they’re at it again. Guess what the upgrade price for Windows 7 Ultimate is:

Yup.

$219.99!

Sorry to shout there. At least this time there’s no promise of “Extras”. Only BitLocker and Language Packs (in addition to the Professional features). Not sure that’s worth $120 over the Professional Upgrade or $170 over Home Premium (even considering XP mode.)

Oh, and you can’t do an edition “downgrade” from Vista to 7. You can buy the upgrade package, but you’ll have to use it to do a “custom install” (i.e. clean install) and then reinstall all your programs and data. Despite that inconvenience, I’ll go for the Home Premium upgrade, thank you very much. I’m done being an Ultimate customer. Or is that Ultimate fool?

(And just for the record, Windows 7 is a fantastic product in my opinion. I hope Paul Thurrott is right when he says it may be the next Windows NT. Unfortunately he also seems to be right about how Microsoft can mess things up with their pricing)

I’ve included a few photos in the pack that I managed to have included in the Spring 2009 software for the HP TouchSmart PC. They’re in the Personalize – Background area, should you be interested in finding them. Here’s one you may recognize:

While I didn’t put this one in the Theme Pack, I did pick a similar shot of downtown Seattle. Come to think of it, maybe this post will be inspiration for doing a “picture of the day” type of thing. Hmm. Been wanting to do that for a while.

All I can do now is hope the size of the pack (12 MB or so) won’t blow my bandwidth allowance…

THAT’S WHEN BAD THINGS HAPPENED. Apparently the speech recognition software turned that phrase into a command and proceeded to empty the nine page paper of all content without hesitation. On top of that, the undo feature of Word seemed to not have noticed the command (or been bypassed somehow), so she couldn’t get the document back via undo either!

This all happened while I was in a meeting at work right before lunch. When I got back to my desk I had several panicked voice messages. Luckily, five pages from the day before could be salvaged because my wife had the presence of mind to close the document without saving, which let her recover all but the about four hours of work that had gone in before the disaster struck.

I went home over lunch to see if I could salvage any more. I decided that I needed support from Microsoft. Well, the call with Microsoft Product Support was less than pleasant (as support calls usually are) and didn’t get us the four pages back, either. Best I could tell nobody had ever reported such an issue before.

I’m surprised this glaring problem escaped all testing at Microsoft. One of the cardinal rules of software development was violated in this case: “Never, EVER, lose the user’s data.” I can’t believe there was no prompt to confirm if she really intended to delete everything in response to the phrase “delete document”. I can’t believe there was no undo possible.

I just can’t believe it. Yet, it’s true.

The PDC keynote this morning was amazing to me. It felt like the HP TouchSmart PC was utilized for about half of the entire keynote by Steven Sinofski and Julie Larson Green. Four machines on stage, front and center.

Since the HP TouchSmart doesn’t have VGA out, there was a camera guy up on stage during the demos, which I thought worked out really well, sort of bringing the audience up on stage with Julie.

Naturally, the machines had been wiped clean and had a Windows 7 build with the new taskbar installed (6933, the build on “The Goods” is 6801 and doesn’t have it). NextWindow, the people making the touchscreen, are making a Windows 7 compatible driver available so you can start developing for Windows 7 touch today, using the TouchSmart. Of course, I’d rather you develop something for the HP TouchSmart UI that we’ve created, and you’ll be able to download some documentation for that soon, from the community site TouchSmartCommunity.com.

But I digress.

If you ever doubted that .NET and WPF were ready for “prime time”, doubt no longer. According to Scott Guthrie’s keynote, Visual Studio 2010 will have its user interface migrated to WPF. That almost blew my mind. Microsoft transitioning their bedrock developer tool to WPF – they wouldn’t do that lightly. Here’s a shot of how WPF in VS 2010 will enable useful visualizations and hookup to external tools:

Scott, too used TouchSmart for his keynote:

And Tesco used it for their demo as well:

And the machines that were all covered up tightly in the big room yesterday:

Yup, all TouchSmarts, ready for Multi Touch hands-on-labs:

The Windows 7 booth had one:

The WPF team did too, although I don’t have a picture of it.

The coolest “giveaway” of PDC 2008 has to be the Sensor development kit from the Windows 7 team. It’s got a hardware board from Freescale with a bunch of sensors, accelerometer and LEDs, all powered via USB, and accessible via the new Sensor APIs in Windows 7. Here’s a shot of the booth:

I can’t wait to play with it.

What a day. Not sure it gets much better than that.

Windows Azure (hmm, hard to pronounce for non-U.S. people, wonder if they ever consider things like that). Ozzie was great, knew his material, delivered well! Wonder what they’ll charge once it’s ready. Red shoes on the dev team, nice touch.

Best presentation, HANDS DOWN: Surface! Cool technology, excellent demos, super easy SDK. One word: wow! Sorry, no pics. Sure you can find plenty elsewhere.

Biggest surprise for me on a personal level: Meeting Nathan Dunlap from IdentityMine (Hi, Nathan!). Seeing their components demoed, running on HP TouchSmart, no less: fabulous.

Other HP TouchSmart sightings: DevExpress demoing their wares on TouchSmart too. More sightings to come tomorrow after the Windows 7 keynotes.

Handed out about three handfuls of USB drives with TouchSmart development guidelines (to some that might be an SDK, but it really is just a document with some high level guidelines). In other words: yes, you can write your own programs for HP TouchSmart and yes, this will be available for download some time soon (pending a software update that is needed for the IQ 500 series, IQ 800 series should be good to go as-is). If you’re not at PDC – sorry, you’ll have to wait a little longer to get it. Someone from Microsoft said it was the nicest USB drive he had seen so far.

My OpenSpace session on TouchSmart development happened, sort of. I just didn’t get to talk much with anyone completely new to HP TouchSmart with an interest in developing for it. Was nice to see some familiar faces, though (Hi, Mark, in case you read this!)

Check out my photos on Flickr.

Deprecated features

The following features have been deprecated:

• Hosting for Microsoft .NET Framework 3.0 Extensible Application Markup Language (XAML) browser applications (XBAPs).
• The Triple-tap/Soft-keyboard ActiveX control for hosted HTML applications.
• Support for using alternative shells to run and host HTML applications.

The reason I’m surprised is that Microsoft announced the support for WPF based extensibility apps at PDC05 with some fanfare.

I guess interest among developers just hasn’t been there for WPF-based Media Center apps, and Microsoft needs to make judgment calls on where to invest in their extensibility platform. The rest of the deprecated features seem to have been made for the same reason: limited interest among developers for these features. In addition I think there might be issues of an architectural nature that just make the three things that got dropped too expensive to maintain or improve.

I’m sad about this development, mostly because I still don’t see a great set of development and design tools around for MCML. WPF seems to me to have a whole lot more momentum than MCML (WPF has the Expression suite of tools and has been billed as the “GDI for the next 20 years”), but who knows what may be coming for Windows 7, or even an earlier interim update for Media Center?

Then the phone rang. Someone wanted to talk to my wife. She was in the process of reading a good-night story to my older daughter. The caller couldn’t wait. So I volunteered to read another chapter of the story.

When I got back, Windows was at the logon screen. Dammit, the Windows Update had gone through with the restart, with me not there to dismiss the countdown dialog.

And Windows Live Writer hadn’t saved a draft.

Both programs violated two cardinal rules for software: Don’t ever do something the user didn’t ask for, and don’t ever, ever, ever lose the user’s data. It’s worse than what Jeff Atwood talked about recently, since there were no crashes involved.

I’m so mad I’m not even sure I’ll want to re-write that other post. It has the potential to help out a fellow developer. Maybe I’ll do it. But right now I hate Windows Update. Or Windows Live Writer. Take your pick.

Today I repeated my search – and Google found a site that mentioned the same problem: http://west-wind.com/WebLog/posts/9849.aspx

The solution was given by Matthijs van der Vleuten in the comments of that post: Remove the ProcessExplorer registry tree. You’ll have to reconfigure everything in ProcessExplorer afterwards, but that’s a small price to pay for getting the tree view back.

If your ntldr goes missing, here’s one way to fix it:

• Boot from your Windows XP SP2 CD.
• Choose the “R” option to repair using a recovery console.
• copy ntldr and ntdetect.com from the i386 folder on the boot CD to the windows hard drive root.

• Double check that the boot order of the hard drives in the BIOS is still how it should be (for some reason my order was messed up, so the system tried to boot from the wrong drive, which puzzled me quite a bit.)

That last point messed me up for a good twenty minutes this time around.

But now everything is good again.

What I’ve been waiting for is also ready: the ability to request a key for your Vista development system. I’ve got mine and am writing this from Windows Live Writer running on my shiny new Vista Ultimate work laptop. Yay!

I’m going to properly uninstall these add-ons so they’re completely gone and then I’ll be a happy IE 7 user!

Thank you Peter G for getting in touch!

Not good. Looks like I’m going to stick with IE 6 / Firefox for a long time.

Uninstalled.