Category Archives: microsoft

Windows Runtime flaws spoil new Windows Store (Metro) apps

The Windows Runtime, the new touch-friendly platform in Windows 8. It solves many problems. Not only is it tablet-friendly, but apps are sandboxed for security, and easy to deploy. No setup hassles, just one-click (or tap) install or uninstall. It also supports three types of development covering most tastes: native C++, .NET Framework, or HTML and JavaScript. In order to ensure responsive apps, Microsoft made many of the APIs asynchronous, so that users would not have the frustration of a frozen user interface or spinning hourglass during long operations.

At least, that is the theory. When I came to write my own simple app though, I was surprised how fiddly it was, and that something trivial like displaying a tweet including a working hyperlink turned out to involve Run elements, a ContentControl, a converter class and so on. Even then, I could not get the mouse cursor to turn to a hand icon when hovering over the link.

This hands-on experience gives me sympathy with others struggling to implement more complex projects. Some have posted about their experiences. Here is Frank Krueger, who has ported his neat iCircuit electronic circuit simulator from iOS and Android to Windows RT:

You would be shocked to see some of the crazy bits of code I had to put in because the Win8 platform, while very rich, is also very generic and doesn’t help you at all to build standard apps (document based, tools, etc.) That is to say, Cocoa is a very mature platform designed to make apps feature-rich and consistent while also making the developer’s life easy. WinRT on the other hand gives you rectangles and a blog post that says “good luck”.

He lists a number of problems, including having to reboot Windows constantly while testing the Share Charm; having to disable media elements in he app because of 500ms delays, no control over buffer sizes, and playback issues; and graphics issues:

I want to do real-time 2D vector drawing. Direct2D is perfect for this. But WinRT puts all sorts of limitations on onscreen rendering, most notably: you can only have 1 DirectX swap chain (view) per window. That means I can’t use Direct2D for rendering the scope which means the scope is slower than it needs to be. Dear Microsoft, go spend a few minutes and see how beautifully CocoaTouch and OpenGL work together on iOS. You might get inspired.

Next up is Media Monkey, a popular Windows media player which has been ported to the Windows Runtime platform. I was pleased to see this, as it lets me play FLAC music files on Surface RT. It is not very stable yet though, and I have had difficulty getting it to index the collection of FLAC files which I have on a network-connected drive.

image

What I found most interesting though were comments about the difficulty of displaying lists beyond a trivial size. One user complained:

When I first started MM scanning my music library, I was seeing the Album list grouped into sections headed up by the Alphabet letters. However, as more Albums got added, the heading letters vanished – and I now have an unbroken list of Albums – a great wodge that is very tiresome to navigate through by scrolling.

to which the Czech developer replied:

It’s a big problem, but not in MediaMonkey, but in system itself. Disabling groups is only crashes prevention because of system limitation :-(. Because of this we cannot use semantic zoom as well.

This has caused me to wonder whether part of the reason for the small number of excellent Windows Store apps is the difficulty developers have in getting them to work right. If so, that is a sad state of affairs for Microsoft’s shiny new platform.

In fairness, this is version 1.0, and the best hope is that a significant update to the platform will come before too long with improved controls, performance and features.

Xamarin 2.0 and Xamarin Studio announced, build for OSX, iOS and Android with C#

Xamarin has announced significant updates to its developer platform. Xamarin is the company formed around 18 months ago, when Novell discontinued its investment in Mono, a cross-platform implementation of C# and the .NET Framework. Its focus is on mobile platforms, in particular iOS and Android, though there is also support for the Mac. On Windows and Windows Phone, the presumption is that developers will continue to use Microsoft’s .NET Framework.

“If you look at what you can develop with C#, there’s about 1.2 billion Windows machines out there, but there’s now about a billion Android and iOS devices. Together we can make C# a universal language for application development and reach 2.2 billion devices,” Xamarin co-founder and CEO Nat Friedman told me.

“There’s a wonderful built-in audience of C# developers, millions of them, who need a bridge to mobile. We can help them take their existing skills and tools, and even code they’ve already written, and bring them to mainstream mobile platforms like iOS and Android.”

The key announcements:

  • Xamarin Studio is  an updated version of MonoDevelop, the Mono IDE. It runs on Mac and Windows.#
  • You can now develop iOS apps in Visual Studio for the first time
  • MonoTouch, the framework for iOS, has been renamed Xamarin.iOS
  • Mono for Android is now called Xamarin.Android
  • A new component store has pre-built components for download, some free, some commercial.
  • Xamarin now offers a free Starter edition, and pricing plans for independent developers, smaller businesses, and enterprises. Indie is $299 per platform per year, Business is $999 per platform/year, and Enterprise $1800 platform/year.

The Starter edition is not much use. It has a limited app size, and even the sample project I downloaded, an Employee Directory, exceeded that size and I had to register for a trial.

Xamarin’s philosophy is to share non-visual code, but to create a user interface that is native for each platform. This is a compromise in terms of the effort involved in supporting multiple platforms, but ensures a native experience on each device. “That’s fundamental to our platform,” says Friedman. “We tell our developers to separate the UI layer from the rest of the app. That allows them to share all the non-UI code across platforms, but to deliver a fully native UI, even though the whole app is written in C#. That’s what users demand now, people want native experiences.”

“We’ve been building tools that essentially project the underlying iOS APIs or Java [Android] APIs into C#”, explains co-founder Miguel de Icaza. “What it means is that people need to build a new UI for each platform.” He adds that Microsoft platform developers should be used to this, as Microsoft itself has several similar but incompatible .NET platforms. “There’s the one on Silverlight, the one on WPF, the one on Windows RT, and the one on the phone, it’s four,” he says. “Developers have had to resort to putting their logic into shared libraries, and build a per-platform UI. We’re reusing that knowledge.”

The ability to develop for iOS in Visual Studio is new. “It’s our most-requested feature of all time.” said Friedman.

I downloaded Xamarin Studio, which in my case was around 1.3GB including an updated Android SDK.

image

The IDE itself is clean and fast, and very much code-centric. It lacks the bloat of Visual Studio, though you will miss many of the features of Microsoft’s IDE.

image

I build the sample Employee Directory app and deployed it to an Android emulator which I use for Nexus 7 development. Deploying the runtime components took a long time, but after waiting patiently the app launched successfully.

image

If you want to do iOS development you will need a Mac of course. Although you can code on Windows, if you then the code is pushed over the the Mac side for compilation and debugging. In order to use Visual Studio, one option is to run Windows in a virtual machine on a Mac, as I have done with reasonable success using Embarcadero’s cross-platform tools.

Xamarin says it is growing fast. There have been 230,000 downloads of its tools, increasing by around 700 per day, and over 12,000 paying customers.

Despite Xamarin’s roots in the open source world (and Mono is still open source), a quick look at the pricing table shows that this is a fully commercial offering and priced accordingly. Presuming customers keep on subscribing, that is a good thing, ensuring the future of the platform; but it is not so good for the smallest developers who might otherwise give it a try.

Windows Phone 7.8 Live Tiles are buggy, say users

When Microsoft announced Windows Phone 8, one disappointment was that existing phones would not be upgraded to the new mobile operating system. In mitigation, Microsoft promised Windows Phone 7.8 instead, an upgrade to Windows Phone 7.5 that implements the most visible feature of WP8, a new Start screen with more flexible live tiles that can be sized small and other new features.

Some users are now receiving 7.8 upgrades, but the news is not all good. According to reports on the Windows Phone Central forum, many users find that the Live Tiles are not refreshing correctly after the upgrade.

image

The idea of Live Tiles is that they refresh in the background with the latest data, such as news alerts or incoming emails.

Developers Heathcliff writes in detail about the problem. He describes three methods to update a Live Tile. The basic ShellTile.Update method works OK, he says. However, if you use an external URL to update a tile, using ShellTileSchedule.Start, it “behaves erratically” and may trigger a problem that drains your battery and makes excessive use of your data connection. Finally, HttpNotificationChannel.BindToShellTile, which uses Microsoft’s notification servers, does not seem to work at all.

On WP 7.5 this method just works as expected. I actually hope I did something wrong here. Or else I don’t understand how this could ever get past the Microsoft Quality Assurance department.

he says.

Finally, users also complain of slower performance after the update, which makes starting apps more laggy.

If Microsoft has put more effort into its new Windows Phone 8 operating system than into an update for existing user, that is understandable, but short-sighted. Those existing users are the best possible evangelists for the platform as well as potential repeat customers; and Windows Phone with its tiny 2.6 per cent global market share, according to IDC, needs all the help it can get.

That said, with decent new WP8 phones like the Nokia 620 available cheaply (O2 in the UK offered this for £120 pay as you go earlier this week), existing Windows Phone 7 users who want to stay up to date are better off buying a new device.

Windows 8: Forget Surface Pro, what matters is the app platform

Microsoft has launched Surface Pro, its own-brand Windows 8 tablet, causing the usual agitation.

  • The 128GB model is sold out online, but has it sold well, or did Microsoft only make a few?
  • Is it too expensive for the spec?
  • Is the battery life too poor?
  • Can you type properly with it on your lap?

All reasonable questions, but to me rather unimportant.

When Microsoft “reimagined” Windows, its goal was to establish its operating system as a new tablet platform. Otherwise, there would have been no sense in upsetting millions of Windows users who were broadly happy with Windows 7, by imposing a new touch-friendly, blocky, mainly single-tasking platform on top of the old familiar Windows.

How is it doing so far? Not well. The reviews for Surface Pro are a symptom of this. It is being treated mainly as an Ultrabook with a detachable keyboard rather than as a tablet. That is a shame, since Surface (RT and Pro) is designed to be tablet-first, with the keyboard cleverly designed into the cover to mitigate the difficulty of using touch alone when you have to use desktop apps.

There are several reasons why Surface is seen as a kind of laptop rather than as a tablet.

First, Microsoft has so far failed to change the way Windows is perceived. People buy Windows devices to run Windows apps, by which they mean Microsoft Office, Skyrim, Foobar2000, and/or their corporate apps written in Visual Basic or C#. The existence of the new Windows Runtime platform is incidental and mainly annoying, since it can get in the way if you only want to run Windows.

This could soon change if there were numerous compelling apps on the new platform; but there are not, and that is reason number two. Which Windows Store apps are better (presuming you have a tablet) than their desktop equivalent, or which are great apps that have no desktop equivalent? It is a short list. Personally I would name the Wordament game, Maps, and the Weather app as examples; and yes, I know how lame that sounds.

Microsoft slipped up badly by spending so little effort on the built-in apps, especially Mail, but also Music and others. The result is that users spend little time in the new user interface (I am guessing but have anecdotal evidence). The further result is that the platform is unattractive to developers, despite the size of the Windows market.

Take a look at the MetroStore Scanner  and you can see that around two hundred apps are added most days (green is updates rather than additions).

image

That in itself does not tell us much. Just one hundred great new apps would be fantastic news for the platform. But no, they are mostly trivial and/or poor and/or repetitive and/or uninteresting.

Why are developers not building more and better apps? That indeed is the question. The main reason of course is that size of the market, not in terms of the numbers of Windows 8 users out there, but in terms of likely sales or adoption.

This is circular though. Good apps will increase the size of the market. So what else?

My views on this changed when I sat down to build my own app, simple though it is. This was harder than I expected, and there is still a z-order bug which I have not got round to fixing. A core question though is this: does the platform help developers to build apps that delight the user? In this respect it is not yet good enough. The kind of app you will build if you follow all the guidelines will be genuinely touch-friendly, but look a bit blocky and spaced out too much. There is also the problem of the disappearing menu bar and the fact that users do not always discover options hidden in the Charms bar. It is too easy to build apps that are not good enough. I regard the poor quality of apps like Mail as evidence of this.

Put another way, it is not yet a platform that inspires developers and makes them want to support it, despite its immaturity.

Windows 8 is not going well then; but I do not write it off. Better apps surely will appear. Further, Microsoft’s next go at this, whether it is called Blue or Windows 8.5 or Windows 9, should be better as the team fix annoyances and add compelling features.

As yet though, there is no sign of Microsoft averting the march of Windows towards being a business-oriented, desktop platform occupying an ever-smaller niche in a world of mobile and browser apps. If I were CEO Steve Ballmer, I would find that a concern.

Microsoft Dynamics CRM 2011 hassles: asynchronous processing service stopped

I installed Microsoft Dynamics CRM 2011 a few days ago – rarely a straightforward task, thanks to Active Directory dependencies and the complexities of Windows security. There also seem to be unfixed bugs in the setup. For example, I always find that the trace directory is incorrectly configured and has to be fixed via PowerShell, even with a new install on a new installation of Windows Server 2008 R2.

Never mind. This time I came across a new problem. After a successful install, users reported errors in scheduled jobs and imports. An attempted import resulted in the message Waiting for Resources.

The problem was that the two CRM Asynchronous Processing Services were not running. Start them manually, and everything works.

The event log reported Event ID 7000 after the last reboot – “the service did not respond to the start or control request in a timely fashion”.

The solution in my case was to set the start action on these services to Automatic (Delayed Start). They now start OK after a reboot.

I suspect this problem may be related to update rollup 12, since the very same problem appeared on another Dynamics CRM 2011 install after applying this.

I also wonder if the fact that SQL Server is on the same VM is related. If CRM starts before SQL Server is fully running, you get this kind of problem.

Microsoft’s Visual Studio and Team Foundation Server get Git integration

Microsoft has announced Git integration in both the Visual Studio IDE and the Team Foundation Service hosted source code management system. According to Technical Fellow Brian Harry:

1. Team Foundation Server will host Git repositories – and more concretely, Team Foundation Service has support for hosting Git repositories starting today.

2. Visual Studio will have Git support – and concretely, we released a CTP of a VSIX plugin for the Visual Studio 2012 Update 2 CTP today.

Git is an open source version control system originally designed by Linus Torvalds to support the development of the Linux operating system. It is a distributed version control system, which means every working directory is itself a full repository, enabling easy forking and offline work.

Team Foundation Service is a version of Team Foundation Server hosted by Microsoft.

Git integration was also recently added to Perforce, another version control system, in the form of the Perforce Git Fusion add-in, emphasising the fact that Git is now a mainstream, enterprise revision control system.

Microsoft financials: record revenue, signs of Windows 8 concern

Yesterday Microsoft released its financial figures for the last three months of 2012.

Quarter ending December 31st 2012 vs quarter ending December 31st 2011, $millions

Segment Revenue Change Profit Change
Client (Windows + Live) 5881 +1140 3296 +416
Server and Tools 5186 +171 2121 +409
Online 869 +85 -283 +176
Business (Office) 5691 -619 3565 -623
Entertainment and devices 3772 -466 596 +79

Although Microsoft reported record revenue, I do not consider these figures all that revealing. The transcript of the earnings call is more to the point. A few notable remarks from CFO Peter Klein and General Manager Investor Relations Chris Suh

  • 60 million Windows 8 licenses sold and 100 million apps downloaded. At 1.66 apps per license that shows lack of interest in the new Windows Store and raises suspicions that some of those sales may actually be downgraded to Windows 7. The remarks from Klein confirm that the new platform is off to a slow start:

It’s early days and an ambitious endeavor like this takes time. Together with our partners, we remain focused on fully delivering the promise of Windows 8.

While the number of apps in the Windows Store has quadrupled since launch, we clearly have more work to do. We need more rich, immersive apps that give users’ access to content that informs, entertains and inspires.

  • Suh states that Windows is selling better to businesses than consumers. Declining interest from consumers is obvious if you walk around a few retailers selling Windows PCs:

Within the x86 PC market, we saw similar trends to prior quarters, with emerging markets outperforming developed markets, and business outperforming consumer. The consumer segment was most impacted by the ecosystem transition, as demand exceeded the limited assortment of touch devices available.

  • System Center 18% revenue growth
  • SQL Server revenue 16% growth
  • Online revenue (this is Bing not Azure) up 11%
  • Windows Phone sales 4 times higher than last year
  • Skype calls up 59%

The company says little about Office 365 and Azure, but my perception is that both are growing fast though how significant they are versus traditional software license sales is less clear.

Trouble ahead? With Windows 8 struggling for acceptance, Office under threat from online and device alternatives, the games console business (overall not just Microsoft) probably in permanent decline, and Windows Phone not yet quite mainstream, you would think so. On the other hand, this is a company with a broad and deep product range and looking at the solid performance of the server products and continuing strength of Windows and Office in business, we may continue to be surprised at its resilience.

Why is Windows 8 not selling better?

The Register reports a rumoured blame game playing out between Microsoft and its OEM partners concerning why Windows 8 sales have not taken off in the hoped-for manner.

A separate source at a major Windows 8 PC maker confirmed frustration is simmering inside Microsoft, and the blame is settling on PC makers. He said [Microsoft] "is pinning the blame on the manufacturers for not having enough touch-based product".

PC makers on the other hand:

PC makers, though, are hitting back after Redmond’s finger-pointing – countering that if they’d followed Microsoft’s advice they’d have ended up building very expensive tablets and would have been saddled with the costs of a huge piles of unsold units. Those who did buy Windows 8 PCs ultimately bought the cheap laptops not high-end Ultrabooks or hybrids.

This is a silly discussion. I agree that not enough tablets were available at launch. On the other hand, the OEMs are correct: the market for high-end expensive hybrids is limited, and rightly so as they are not good value for most users.

What both sides seem to be ignoring is that Windows 8 was always going to be a hard sell. Microsoft made a conscious and deliberate decision to create a new tablet platform and bolt it on to desktop Windows in order to establish it. The added value for users who just want to run Office and other desktop apps is small, while the cost in terms of learning to find your way around a new Start screen is significant.

This could yet work out well for Microsoft. As the platform matures and better new-style apps appear, Windows 8 will become more attractive. Further, as users discover that Windows 8 is not really hard to use, the reasons not to upgrade will diminish. In theory, users will gradually be able to spend more time in the touch-friendly user interface rather than in the desktop, making pure tablet use of Windows 8 (no keyboard or mouse) more attractive.

The counter-argument is that Windows may never shake off its desktop inheritance and that the Metro-style platform will never be important.

Maybe Microsoft should have communicated "let’s have a low-key launch and build this slowly" rather than spending big on marketing in the hope that nobody would notice these issues.

It is true that there are big and long-standing problems with the way Windows machines are designed, built and marketed, problems that have caused Microsoft to create its own Surface devices (I am typing this on Surface RT) and to copy Apple by opening its own stores, selling "signature" PCs with third-party rubbish removed.

In addition, Microsoft made inexplicable mistakes with the launch of Windows 8 and Windows RT, such as building a mail app that is barely competent – one app that almost everyone will try and which could have been used to show off the potential of the new platform. Check the reviews; there is even something odd about the few five-star ratings.

That does not mean that the subdued launch of Windows 8 is mainly Microsoft’s fault, or mainly the fault of its partners. The reasons are more obvious and more fundamental.

Making sense of Microsoft’s Cloud OS

People have been talking about “the internet operating system” for years. The phrase may have been muttered in Netscape days in the nineties, when the browser was going to be the operating system; then in the 2000s it was the Google OS that people discussed. Most notably though, Tim O’Reilly reflected on the subject, for example here in 2010 (though as he notes, he had been using the phrase way earlier than that):

Ask yourself for a moment, what is the operating system of a Google or Bing search? What is the operating system of a mobile phone call? What is the operating system of maps and directions on your phone? What is the operating system of a tweet?

On a standalone computer, operating systems like Windows, Mac OS X, and Linux manage the machine’s resources, making it possible for applications to focus on the job they do for the user. But many of the activities that are most important to us today take place in a mysterious space between individual machines.

It is still worth reading, as he teases out what OS components look like in the context of an internet operating system, and notes that there are now several (but only a few) competing internet operating systems, platforms which our smart mobile phones or tablets tap into and to some extent lock us in.

But what on earth (or in the heavens) is Microsoft’s “Cloud OS”? I first heard the term in the context of Server 2012, when it was in preview at the end of 2011. Microsoft seems to like how it sounds, because it is getting another push in the context of System Center 2012 Service Pack 1, just announced. In particular, Michael Park from Server and Tools has posted on the subject:

At the highest level, the Cloud OS does what a traditional operating system does – manage applications and hardware – but at the scope and scale of cloud computing. The foundations of the Cloud OS are Windows Server and Windows Azure, complemented by the full breadth of our technology solutions, such as SQL Server, System Center and Visual Studio. Together, these technologies provide one consistent platform for infrastructure, apps and data that can span your datacenter, service provider datacenters, and the Microsoft public cloud.

In one sense, the concept is similar to that discussed by O’Reilly, though in the context of enterprise computing, whereas O’Reilly looks at a bigger picture embracing our personal as well as business lives. Never forget though that this is marketing speak, and Microsoft consciously works to blur together the idealised principles behind cloud computing with its specific set of products: Windows Azure, Window Server, and especially System Center, its server and device management piece.

A nagging voice tells me there is something wrong with this picture. It is this: the cloud is meant to ease the administrative burden by making compute power an abstracted resource, managed by a third party far away in a datacenter in ways that we do not need to know. System Center on the other hand is a complex and not altogether consistent suite of products which imposes a substantial administrative burden on those who install and maintain it. If you have to manage your own cloud, do you get any cloud computing benefit?

The benefit is diluted; but there is plentiful evidence that many businesses are not yet ready or willing to hand over their computer infrastructure to a third-party. While System Center is in one sense the opposite of cloud computing, in another sense it counts because it has the potential to deliver cloud benefits to the rest of the business.

Further confusing matters, there are elements of public cloud in Microsoft’s offering, specifically Windows Azure and Windows Intune. Other bits of Microsoft’s cloud, like Office 365 and Outlook.com, do not count here because that is another department, see. Park does refer to them obliquely:

Running more than 200 cloud services for over 1 billion customers and 20+ million businesses around the world has taught us – and teaches us in real time – what it takes to architect, build and run applications and services at cloud scale.

We take all the learning from those services into the engines of the Cloud OS – our enterprise products and services – which customers and partners can then use to deliver cloud infrastructure and services of their own.

There you have it. The Cloud OS is “our enterprise products and services” which businesses can use to deliver their own cloud services.

What if you want to know in more detail what the Cloud OS is all about? Well, then you have to understand System Center, which is not something that can be explained in a few words. I did have a go at this, in a feature called Inside Microsoft’s private cloud – a glossary of terms, for which the link is currently giving a PHP error, but maybe it will work for you.

image

It will all soon be a little out of date, since System Center 2012 SP1 has significant new features. If you want a summary of what is actually new, I recommend this post by Mike Schutz on System Center 2012 SP1; and this post also by Schutz on Windows Intune and System Center Configuration Manager SP1.

My even shorter summary:

  • All System Center products now updated to run on, and manage, Server 2012
  • Upgraded Virtual Machine Manager supports up to 8000 VMs on clusters of up to 64 hosts
  • Management support for Hyper-V features introduced in Server 2012 including the virtual network switch
  • App Controller integrates with VMs offered by hosting service providers as well as those on Azure and in your own datacenter
  • App Controller can migrate VMs to Windows Azure (and maybe back); a nice feature
  • New Azure service called Global Service Monitor for monitoring web applications
  • Back up servers to Azure with Data Protection Manager

and on the device and client management side, new Intune and Configuration Manager features. It is confusing; Intune is a kind-of cloud based Configuration Manager but has features that are not included in the on-premise Configuration Manager and vice versa. So:

  • Intune can now manage devices running Windows RT, Windows Phone 8, Android and iOS
  • Intune has a self-service portal for installing business apps
  • Configuration Manager integrates with Intune to get supposedly seamless support for additional devices
  • Configuration Manager adds support for Windows 8 and Server 2012
  • PowerShell control of Configuration Manager
  • Ability to manage Mac OS X, Linux and Unix servers in Configuration Manager

What do I think of System Center? On the plus side, all the pieces are in place to manage not only Microsoft servers but a diverse range of servers and a similarly diverse range of clients and devices, presuming the features work as advertised. That is a considerable achievement.

On the negative side, my impression is that Microsoft still has work to do. What would help would be more consistency between the Azure public cloud and the System Center private cloud; a reduction of the number of products in the System Center suite; a consistent user interface across the entire suite; and simplification along the lines of what has been done in the new Azure portal so that these products are easier and more enjoyable to use.

I would add that any business deploying System Center should be thinking carefully about what they still feel they need to manage on-premise, and what can be handed over to public cloud infrastructure, whether Azure or elsewhere. The ability to migrate VMs to Azure could be a key enabler in that respect.

Microsoft updates .NET Framework 4.5 for Windows 8, Server 2012 to fix performance, bugs

Microsoft has released an update for .NET Framework 4.5 which you may have noticed flying past if you keep an eye on Windows Update in Windows 8. The update is described here, and it is a big one. For example, in the Network Class Library:

Assume that you run a .NET Framework 4.5-based application that uses asynchronous APIs to read chunked responses. In this situation, the chunked responses may be read synchronously.

The HttpWebRequest class lets callers read an HTTP response either synchronously or asynchronously. However, if the response is a chunked HTTP response, then parts of the response are read by using synchronous I/O (Winsock calls) even when the caller uses the asynchronous code path. In this situation, the calling thread is blocked until data is received on the network.

Given this and other issues, the update is highly recommended. Maybe we will see fewer pauses in Windows App Store apps, some of which have not delivered on the “fast and fluid” promise.