I’m pleased to announce that the Windows Phone SDK 7.1.1 Update is now available for your download; it’s the final version of the CTP we released last month, and enables Windows Phone developers to do two things:
While I’ll circle back to these two points in a moment, I’d like to take a moment and highlight what’s actually in this update.
The 7.1.1 Update is really just that – it’s an update to the existing WPSDK: it doesn’t add much in the way of new features to your WPSDK installation; it updates your existing install to do a few new tricks:
Installing the patch is pretty straightforward process, with a standard three-step install process (accept; install; finish). Because the patch contains two virtual OS images (256 MB device image; 512 MB device image), the patch is pretty beefy (weighing in at just under 300 MB) and it can take time to install as it initializes each image as part of the installation. During the virtual image initialization process, each Windows Phone OS device image is booted up and then paused at the point where the OS is ready to accept an app install; while the initialization process adds some pain up front, it saves you lots of time in the long-run as you don’t have to watch the OS boot-up screen every time you start up the emulator to deploy/debug your code.
On my machine, I was looking at the following screen for about 15 minutes:
After you’ve installed the update, the most noticeable change for most folks is you’ll now see a couple nifty entries in your target selection drop-down box:
Selecting one of these will launch the selected emulator, just as you would expect. Something that you may try to do (well, the first thing I did) is launch your app in the 512 MB emulator and then also launch it also in the 256 MB emulator, so that you can compare your WP app running in both emulators, side-by-side, to compare performance; needless to say, running both emulators at the same time doesn’t work.
As Larry discussed earlier this month, the WPSDK 7.1 didn’t run on the Windows 8 Consumer Preview release. The issue involved three elements: an issue with XNA Game Studio, an issue with the Windows Phone emulator, and a requirement for .NET 3.5. The only remaining blocker for folks successfully developing for Windows Phone on Windows 8 was the emulator. I’m happy to report that this patch removes that final roadblock, and enables our mobile developer community to bring their WPSDK with them as they evaluate the new OS.
There are two caveats I should provide around running the WPSDK 7.1.1 on your Windows 8 machine:
That being said, this update goes a long way to making it easier for folks to build apps that target both Windows Phone and Windows 8; the WPSDK 7.1.1 runs quite well side-by-side with Visual Studio ‘11’. Particularly with the Consumer Preview out, the ability to run the IDEs side-by-side has been a major request from our developer community. As you are starting to evaluate your strategy of targeting both platforms, we still continue to believe that code reuse via XAML and C#/VB.NET will continue to be your best strategy; and this side-by-side support should help make your life much easier as you can develop and debug side-by-side, as well. Look for information on this topic from Larry in the coming weeks.
I won’t drill into this topic too much given it has been covered on this blog and others; not to mention you probably already have a good understanding of this topic already if you installed the CTP.
If you haven’t yet looked what to keep in mind as you tailor your apps for 256 MB devices, here are a couple good starting points:
As Todd mentioned a couple weeks ago, these new devices, coupled with the 23 new markets that went live last week, account for a nearly 60% increase in total addressable market for your apps. If you haven’t already returned to the App Hub and opted into the new markets, it’s a great time to do so. Just sayin’…
Yes, in fact you can update without having to uninstall the CTP! The engineering team tells me that you should be able to install the RTW release of this patch (the one I’m announcing here; RTW being ‘Release to Web’ since these tools don’t ever really go to ‘manufacturing’) either on a pristine install of the WPSDK 7.1 or one that had been previously updated using the CTP release of this update (no need to uninstall the CTP version of the 7.1.1 Update before running the RTW patch).
An important note to make about this update is that it is, in fact, an update, and not a full installation. As such, you won’t find it listed in the ‘Add/Remove Programs’ area of your Windows developer machine. To locate the installation, you’ll need to go to the ‘View Installed Updates’ section of your Windows Control Panel (screen shot below, for your convenience).
Once in the Installed Updates section of the Control Panel, you’ll see a very very long list (at least my list is lengthy ) of updates that you’ve installed to applications over time. For the WPSDK 7.1.1 update, you’ll find it listed under a variety of headers (because it touches a variety of installed components), but the primary entry will be found under Windows Phone SDK 7.1 (screen shot below again, for your convenience; because I have the English localization, the actual listing is ‘Windows Phone SDK 7.1 – ENU).
It’s also noteworthy to point out that the update’s installation entry uses the KB entry to denote the installation (for English: KB2669191) instead of the actual patch name; and, if you’re comparing notes with me after you’ve installed the 7.1.1 Update for a different locale, you’ll also notice that your KB number is a bit different. Have no fear, everything is good in the world as each patch binary is required to have its own KB entry, and so this is just the way of the world [of patches].
Lastly, returning to the ‘what’s in a name’ point; which is invariably the second question I frequently get when discussing this patch. As you look at what is contained in this patch, it really is a patch that updates and improves the capabilities that have previously been delivered in the WPSDK instead of a big release with lots of net-new features. Furthermore, since the OS isn’t incrementing (the OS is still 7.10.8773 under the covers), a couple options had been considered: either the WPSDK 7.1.1 Update and WPSDK 7.1 March 2012 Update. Given the choice between those two options and the feedback we received last year around patch naming (for the WPDT, we released two updates: the Oct 2010 Update and the Jan 2011 Update), we went with WPSDK 7.1.1 Update. We think it clearly communicates what the Update does and it’s relation to the WPSDK 7.1.
So, all of that being said, it’s a great update, and well worth the time to download and install. Go grab it, and let us know what you think. If you have any issues, definitely poke your head into the ‘Tools for WP7’ App Hub forum and give our most excellent support guys a holler.
Hi, Is there a way to use windows sdk 7.1 in visual studio 2012 ultimate (both installed in windows 7)?
Did anyone else experience problems after installing Windows Phone SDK 7.1.1 (e.g. see Mahesh's experience)?
Running Windows Phone SDK 7.1 at the moment and everything works fine (also XDE) on a Vista (32 bit) and Windows 7 (64bit) machines and I like to avoid to break my development systems ...
I am trying to install Windows Phone SDK 7.1 along with update 7.1.1 on Windows 8 Pro RTM machine. I have installed Windows 8, enabled .NET framework , installed office, Visual studio 2012 ultimate RTM and then Windows Phone SDK. I also followed instructions given blogs.msdn.com/.../10274694.aspx . installation completed successfully but I am not able to Run windows Phone emulator. it try start Emulator and then shows an error message that "Windows Phone Emulator has stopped working". is they other patch required to install other than 7.1.1 ?
This seems like the right place to ask my question. I'm wondering is it possible to Develop WP apps with a VS 2012 RC? And if possible how?
Can it [the WP SDK (7.1 + 7.1.1)] be installed/used in a W8 CP (64-bits) running in an Oracle VirtualBox ?
@Bryan - thanks for the followup! I'm very sorry to hear about your laptop, but I'm glad to hear the experience went well on your desktop. Happy coding!
@Cliff Thanks for the reply! "On the metal" is a term I'm unfamiliar with, but I'm assuming that it means that it's running without being hosted within another OS. In that case, I am running "on the metal". Turns out that the install may have been a possible hint at what was to come. My laptop began bluescreening last night and is a completely unstable environment now. It's still under warranty and I'm backed up just fine so I'm not going to lose more than a few minutes worth of work (whew!). I'll check back in when my laptop issues are resolved. I just finished installing it on my desktop with no issues (actually took longer to write this response than it did for the install to complete). Thanks again! Have a great one!
@Naresh - I would imagine that you could do what you want by using Google Calendar's APIs. I haven't done this before myself, but a quick Bing search and a few clicks brought me over to a .NET Client library (both binary and with source) for accessing their APIs (including their Calendar APIs) - You can find the project over @ code.google.com/.../GettingStarted
I'm unsure what .NET version the DLL/binary is for, but given you also can grab the source, I would imagine that you should be able to get it into .NET 4 without a problem.
Best of luck!
@Bryan - You're likely getting caught in the two emulator initializations. These can be either pretty quick (if you're running Windows on the metal) to extremely long (if you're running within a VM such as Virtual PC or within Parallels). Beyond the hardware, what's your execution environment look like?
Having problems with installing this update. Let it run for 45 minutes and then cancelled. Had to kill the msiexec.exe tasks to get rid of the installation UI's. It locks up at the same place where you say that you saw that screen for 15 minutes. My machine is suitably fast running on an i7 with 8 GB RAM. It seems to lock up on some custom actions regarding some registry changes. These are the last 2 lines in the log before I cancelled the installation:
MSI (s) (88:90) [10:17:31:880]: Executing op: CustomActionSchedule(Action=CA_DtptPrxyPortReg64_2_Install.4BCBE540_25FC_4E5E_848E_BB38A2754150,ActionType=3073,Source=BinaryData,Target=CAQuietExec64,CustomActionData="C:\Windows\system32\reg.exe" IMPORT "c:\Program Files (x86)\Common Files\Microsoft Shared\CoreCon\5.01\Misc\DtptProxyPortsAdd2.reg")
MSI (s) (88:AC) [10:17:31:882]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIA006.tmp, Entrypoint: CAQuietExec64
Any ideas on what I can try? Thanks for the hard work and good luck!
I want to add events to Google calendar by a WP7 App. I am able to do this by adding a class library of 2.0 framework to the WP7 app. But now I want to remove the class library. If there is any other way then please tell me.
Also unable to add the google dll in wp7 directly . Please help me
I want to add events to Google calendar by a WP7 App directly. I am able to do this by adding a class library of 2.0 framework to the WP7 app. But now I want to remove the class library. If there is any other way then please tell me. Thanks.
Oh... You are right, the machine was installed old WP SDK 7.1 (RC!) I just installed 7.1.1 successfully now (and log collecting...). Its seems I was installing from wrong iso file on my disk... Thank you Cliff!
@Kaoru: I heard back from engineering...
Can you verify that you're running the RTM version of the WPSDK 7.1? The easiest way to verify this is to run "vpdexpress.exe" at the run command, and go to "help" | "About". You should then get to a screen that has a line along the lines of "Version WPDTRTMRel - 40219.209" - verify that that is, indeed RTM.
If you do have the RTM, can you try and install the 7.1.1 patch again, and collect the logs from the '%temp%' folder by using the collect tool from www.microsoft.com/.../details.aspx - you can mail me the vslogs.cab file, and I'll get it to the right folks.
@pkzsoftware - Syntax for specifying the 90mb memory requirement (which opts you out of being installable on 256mb devices) can be found here: msdn.microsoft.com/.../hh855081(VS.92).aspx
I saw this in a tech blog. before i clicked, i thought maybe the SDK was getting some very much needed APIs, but as you can read, i am wrong...
•IntelliSense now supports specifying the 512 MB device requirement in your manifest file, should you choose to opt your app out from running on the new 256 MB devices....
OK..so if I want to run on 256MB devices I do nothing right? What do I change in the manifest if I want to opt out? Not seeing it w/ intellisense.
And thanks for your responses!
@Roger - you can submit apps now
When could we expect to submit apps to marketplace with SDK 7.1.1?
@entegy; @pkzsoftware: No need to do a recompile any more than you did for 8107; think of the 7.5 Refresh release as similar to 7.5 Update 8107 - it's in a very different class of updates from NoDo or Mago.
@Kaoru: I'll inquire with our tools team; thanks for the detailed info!
@Michael: To your questions:
1. Provided you have the WPSDK 7.1 installed, you should be able to install the 7.1.1 update with no issues.
2. The Win8 support is a bonus in this release; the primary purpose with this patch is to enable folks to build and debug against Update 8773, which added support for 256 MB devices.
3. I'm not sure if there's anything to come clean on - you can use the WPSDK to build apps that target Windows Phone using either XAML apps (aka Silverlight) or XNA. I'm totally unable to comment on Windows' support plans for XNA, but we continue to support the XNA platform and the games written on it - on 7.5 and [at least] in the next major release. We've said this much at BUILD last year, and it continues to be true. Your existing code and skills will continue to be good on Windows Phone, both for XAML+C#/VB.net AND for XNA.
3b. As I said in #3, I can only comment on the Windows Phone developer platform.
@anatolyl: Great suggestion on #1, I'll pass along to the tools team, but if it isn't already up on UserVoice, please put it up there. For your second point, what about doing a <Ctrl>+<f5> or using 'Deploy...' option to run the code in the emulator without locking the IDE into debug mode?
@cesarfong: Glad to hear you figured out your issue; and thanks for reporting back! :)
@twisterjosh: The 7.1.1 update was a patch; not much in the way of net-new capabilities. If you haven't already, lend your voice to BT APIs and USB-to-serial items on there. Both of those capabilities are on the team's radar as something the dev community is interested in seeing the dev platform provide, and your thoughts/comments/voice help them in deciding feature prioritization.
Solved! Installed lastest WIndows Phone 7.1 SDK (RTW version) and now 7.1.1 is installing
Is there any talk of adding a Bluetooth API or USB-to-serial communication? I'd really like to start building external accessories for WP7!
Thanks Cliff for reply my dev machine is all in ENU. It seems i am working with RC (40219.166) instead of RTW (40219.209)
Windows Phone SDK 7.1 (RC) - ENU 10.1.40219
Windows Phone SDK 7.1 Add-In for VIsual Studio 2010 (RC) - ENU 10.0.40219
Windows Phone SDK 7.1 Assemblies (RC) 10.0.40219
Windows Phone SDK 7.1 Extensions for XNA Game Studio 4.0 4.0.30708.0
I will update my SDK 7.1 and try installing again
It's about time to
1) enable simulators to maintain preferences across multiple sessions like real device and like ios and android simulators are capapble to.
2) make it so that the simulator does not lock the IDE, so we can continue to write code while the simulator is running.
that would be very helpful
thanks for this release great
i have some ? can somone from the windows team answher them please
1. i have not installed the CTP , does the pacth still works or shood i unstall the old one and install the new one
2. you say in the text like this words
That being said, this update goes a long way to making it easier for folks to build apps that target both Windows Phone and Windows 8; the WPSDK 7.1.1 runs quite well side-by-side with Visual Studio ‘11’.
is this refresh only for windows 8 and can we right click and create a windows version of xna game on windows 8
it makes developerment easy not have to transfere the files all the time to device or emulator
3. you can come clean now , will xna game studio run on tablets , ultrapc, and notebooks, desktop,lattop systems
that runs windows 8, so we do not have to have installed 2 OS just to develop for the tablet and the phone , and in the future a new os for developerment on xbox
3. if it runs why do you not allow us to develop our games in xna and sell them at the windows 8 store, so we only have to build once and deploy to all windows devices , wicth sony has managed to do in just 14 days from now there we can use c# and a framework look and fell 70% like XNA , but we can build once and deploy to phone,tablets,vita and so forth
i hope you can answhere this ? , corse it is hard to managed 2 os and 3 defferent dev kit at the end
I can't install to W8CP like Necroman too. The followings is msi loggin output...
env: Windows 8 Consumer Preview Jpn x64, VS2010 SP1 Jpn Premium, WPSDK7.1 Jpn, Async CTP v3, VS11 Beta Ultimate Jpn, Zune Software 4.8.2345.0 Jpn, Samsung Series 7 Slate XE700T1A-A04US
OS Version = 6.2.8250, Platform 2
OS Description = Future OS - x64 Unkonw Edition (ProductType=74)
CommandLine = c:\320f7eb0f82522c2379157\Setup.exe /log C:\Users\...\wpsdkinstall.log
Using Simultaneous Download and Install mechanism
Package Name = KB2669196
Package Version = 10.0.40219
User Experience Data Collection Policy: UserControlled
Logging all the global blocks
1.KB2669196 は適用されないか、お使いのコンピューターの別の条件によって妨げられています。詳細については、go.microsoft.com/fwlink を参照してください。
Final Result: Installation failed with error code: (0x000013EC), "A StopBlock was hit or a System Requirement was not met." (Elapsed time: 0 00:00:03).
To ensure full compatibility with Tango and 256MB devices, should we recompile our apps and resubmit like we did with Mango?
@Karios - I don't believer we've ever had an explicit x64 version of the WPSDK (I could totally be wrong on that one, though).
@Elad - I don't believe any there wsa any additional BiDi love in this patch. I'll followup with the PM who handles that and see if I can get some additional clarity (and maybe a workaround) on your issue.
Nice of you to add Israel to the market, but there are some urgent and serious RTL bugs currently in the OS, mainly the PIvotControl which goes hay-wire if you set it Right-To-Left, and scrolls the wrong way if it has any RTL items nested within it.
I can't seem to find the x64 version. Is it not available yet?
@DjiXas - I just get the SDKs out there - and this one works for building apps that run on both the 256 MB and 512 MB devices running the Windows Phone 7.5 Refresh; needless to say, hopefully soon. :)
@Necroman - This should work just fine with the Async CTP - let me know if it gives you issues. Also, as @Paulos pointed out - the update requires the base WPSDK 7.1 to be installed so it can patch it.
@rwalrond - I assume you meant before this was installed; hopefully you have your screenshotting (via emulator) back again!
@cesarfong - Which patch you run depends on the base install you have. Which language were you trying to install, and which WPSDK 7.1 language do you already have installled?
I have the same issue like Necroman. I haven't unistalled anything just saying me the same message.
My is a w7 in macbook core 2 duo, 3gb ram x86
Just have installed Visual Studio Express for Windows Phone 7.1 and Visual Studio Ultimate
Necroman: You have uninstalled your existing WP SDK 7.1, that's why you can't install this patch. It's a patch (= update) after all.
Cannot install here, just ending short after the extraction with "KB2669191 does not apply, or is blocked by another condition on your computer. Please see go.microsoft.com/fwlink for more details."
My machine: Windows 8 CP x64, I got VS11 Ultimate beta and VS2010 Ultimate SP1 installed too. Just before installing the SDK 7.1.1 I uninstalled the SDK 7.1. VS2010 repair did not helped :(
Yes!, I upgraded all my machines to W8CP and then realized I couldn't take screen shots of my WP7 App updates.
Just a quick question, does the Async CTP work with this SDK? :)
When can we expect Tango update for the high end?