Tag Archives: microsoft

Microsoft and the NHS: what went wrong?

Microsoft UK’s John Coulthard, Senior Director Healthcare and Life Sciences, has posted a comment on the decision by the NHS not to renew its EWA (Enterprise Wide Agreement) with Microsoft. His summary:

The bottom line is the NHS benefited from the productivity gains delivered through a suite of Microsoft software worth in excess of £270m per year. The actual cost to the NHS was £65m per year, delivering a saving of saving of £205m to the NHS and British taxpayers. For the next three years the cost would have risen to £85m as the NHS deploys more and more technology while the National Programme rolls out.

Software supplier whinging at loss of a lucrative contract? Of course; but at the same time I’d be interested to know whether this results in greater expense for UK taxpayers, of which I am one, and what is the real reason for the contract’s termination.

I’d like to think the decision is part of a strategy to end vendor lock-in and promote both competition and use of open source systems; but the truth may be less inspiring.

What are we to make of this report in Computer Weekly which says:

“Out of the blue, the Cabinet Office rejected the cut-down version of the renewal," said a source. "The noise from the top is that they are not sure national agreements work. It will be down to the trusts to make sure they are fully licensed."

One of the odd things reported is that the cut-down agreement was to have cost £21m, I presume annually; but the government is paying an immediate £50m to Microsoft:

The Cabinet Office did agree to pay Microsoft about £50m to cover software used in the previous agreement that was not licensed, but attributed the spend to the last administration’s budget.

That does not sound like a strategy to save money, when you consider the licensing costs now facing NHS trusts who no longer have an agreement in place.

Now, it is possible that the long-term effect will be to reduce lock-in, though that is optimistic; I do not know if any NHS trusts are actually planning to move away from Microsoft’s platform and even if they are, it is not something that can be done quickly. Another scenario is that most of them make their own agreements with Microsoft, the total cost of which exceeds what the EWA renewal would have cost.

Still, the outcome will probably please Google which has its own idea about how to provide IT for healthcare.

Nothing I’ve read really explains the decision and I would like to know more.

Stats that matter: Android grows in mobile, IE stops declining, eBooks take off

This should be three blog posts; but you’ve read this news elsewhere. Still, I can’t resist a brief comment on three recent trends.

Browsers

The first is that usage of Microsoft’s Internet Explorer has levelled off after a long period of decline. Microsoft says it is increasing but the numbers are too small to say that with confidence. StatCounter global stats for May to July show slight decline for IE (52.83% –> 52.37%) and FireFox (31.54%->30.88%), with Google Chrome the main beneficiary (8.81%->10.32%).

On this blog Chrome has grown from 4.2% to 12.4% in the last year. IE is still declining: 44.9% in July 09, 39.6% in June 10, and 38.2% in July 10.

My guess is that the success of Windows 7 might have brought back a few FireFox users. The interesting story though is where Chrome will be when it stops growing its share. My second guess is that it will be ahead of FireFox, though that is speculative. It is WebKit though, and I think that will be bigger than Mozilla’s Gecko thanks to adoption by Google, Apple, Adobe and others.

Mobile

Next, Google Android. Nielsen reports that it has pulled ahead of Apple iPhone in the US SmartPhone market; both are behind RIM’s Blackberry though that is in steady decline. RIM is announcing Blackberry 9800, the first on OS 6, later today; but I doubt it will disrupt Android’s growth. The developer angle is that Android is now equal to Apple’s iPad/iPhone in strategic importance, which will be a relief to Adobe – Flash runs on Android but not iPhone.

Android owners lack the satisfaction of Apple iPhone owners. 21% of them are eyeing the iPhone for their next upgrade, whereas only 6% of iPhone owners want Android next. Only 42% of Blackberry owners intend to remain loyal. It is all tending to confirm my speculation back in April that Android is the new Windows.

So in two years time, what will be the market share for RIM, Nokia Symbian/MeeGo, Windows Phone, HP Palm WebOS? It will not be easy for any of them.

eBooks

Finally, eBooks. The Kindle vs iPad vs Nook vs Sony is one story; but the bigger one is that the eBook is happening at last. David Carnoy’s recent articles on Amazon give the background. One is an interview with Amazon’s Ian Freed in which the retailer says eBook sales have tripled in the first quarter of 2010 vs that in 2009, and claims 70-80% of the market. Another looks at what Amazon didn’t say. However the market shares work out though, what matters is that screen, battery and wireless technology are now good enough, and publishers and authors willing enough, for eBooks to become mainstream, with huge implications for the media industry.

Windows Phone 7 briefing report: no enterprise app deployment at launch

I attended a Microsoft briefing on Windows Phone 7 (WP7) yesterday. Here’s a quick summary of what interested me.

It does appear to be a decent phone. Unfortunately I’ve not yet received a preview device, but there’s no doubt that the user experience is well ahead of that on previous Windows Mobile devices.

The user interface is distinctive as you have no doubt seen. Microsoft is building strong links with both Facebook and Windows Live, surfaced at various places, and hopes this will be the best phone for social networking. It also hooks into Xbox Live, though it does not enable real-time multiplayer games, only turn-by-turn.

It has Bing maps with GPS support, though I suspect it will not be the equal of Google Maps on iPhone or Android. However, at least Microsoft is not in Apple’s position where it relies on a competitor for this key application.

One significant aspect for both users and developers is Tile Notifications. Each installed app has a tile which the user can install on the Start (home) page. These tiles can display text and image notifications that can be customized for the user. For example, a travel app could show a red alert and a message if a plane was cancelled or delayed. A sports app could show the latest score for your favourite team. However, there is no multi-tasking, so most of the time the app is not even running. How does this work?

The answer is that Microsoft hosts a notification server through which app vendors can push notifications. The app vendor needs to store on its own server any user-specific data, such as which flight she has booked. The app vendor can then push notifications to the user via Microsoft’s service. A more detailed explanation is here.

I like this form of notification since it is non-intrusive for the user. If you do not want to see them at all, you can just remove the tile from the Start page.

Microsoft confirmed that in-browser Silverlight will not work on launch. This strikes me as surprising, since Silverlight is built into the OS. I guess it will come later.

I asked a few questions.

When will we get Windows Phone 7? Microsoft is only saying “for Christmas 2010”.

Will it support tethering? No comment at the moment.

Will there be any way to copy a file from your PC to the device? I thought this would get a straightforward answer, but it did not. I was told that the PC side of WP7 has not been announced yet. However, it will bear some relation to what has been done before for Zune – though the UK still might or might not get the Zune Pass subscription service. Prompted by this discussion, I downloaded the Zune software. It is nicer to use than Windows Media Player, for sure. Why does Microsoft have two free media players, a good one that is reserved for a small niche of US users, and a mediocre one that comes with every version of Windows? You tell me.

image

Will there be any way to deploy applications without going through the Marketplace? The answer is mostly “No”, though Microsoft knows this is necessary for corporate apps and says there will be an announcement on the subject later this year. That said, there is a developer portal, intended for testing your apps, where you can specify up to 5 or 10 users who can download and install an app. This is in effect a limited private deployment, though it is not intended for that purpose.

Deploying apps to Windows Phone 7 will be slightly more expensive than it is for Apple’s iPhone. The policies are explained here. You pay $99 to register, which gets you five free submissions, after which it is $19.99 per app. Each registration is limited to five free apps, but there is no limit on paid apps. There is a 70/30 revenue split. The idea is to limit the number of low quality apps. Not a bad thing considering the amount of junk in Apple’s App Store.

Microsoft cash cows alive and well, lame ducks still lame

Here is my quick summary of Microsoft’s just-announced quarterly results:

Quarter ending June 30th 2010 vs quarter ending June 30th 2009, $millions

Segment Revenue Change Profit Change
Client (Windows + Live) 4548 +1379 3063 +1134
Server and Tools inc. Azure 4012 +84 1546 +340
Online 565 +64 -696 -111
Business (Office) 5250 +683 3284 +578
Entertainment and devices 1600 +343 -172 -31

What’s notable about these figures? Well, the big-picture Microsoft question is how it is coping with industry transitions, in particular the transition from on-premise servers and desktop software to cloud services and mobile device clients. Of course you can debate the extent and speed of that transition, but I believe it to be real.

The story here is that Microsoft’s traditional products are still amazingly profitable, and that the effort invested in making Windows 7 a decent upgrade from Windows XP or Vista is paying off. Further, Microsoft Office sales actually exceed Windows sales. It does not really surprise me; despite the existence of capable cheaper or free alternatives, I rarely see business PCs that do not have Office installed; and Microsoft is busy locking in Enterprise customers with hooks between Office client and SharePoint server.

On the other hand, Microsoft’s progress in cloud and device looks amazingly bad. The figures are not all that easy to read, since Azure, Microsoft’s cloud platform, is part of the Server and Tools business; and BPOS, the cloud-based Exchange and SharePoint offering, probably sits there too. The “Online” business in the figures covers Bing and MSN, and earns its money primarily from advertising. This part of the business managed to turn in a loss greater than its revenue, which is remarkable considering how successful Google is with that same business model.

Entertainment and Devices is also hard to read. If you read the press release, it turns out that the reason revenue increased was not thanks to the success of Xbox or an unlikely rebound for Zune or Windows Mobile. Xbox actually declined, and so did Windows mobile, and the increase was thanks to increased sales of Windows Embedded:

Non-gaming revenue increased $35 million or 1% primarily reflecting increased sales of Windows Embedded device platforms, offset in part by decreased Zune and Windows Mobile revenue.

Windows Embedded is an interesting story. I don’t know how its figures break down, but I research things such as digital signage and point of service systems from time to time, and there is a lot happening in that space which deserves more attention from the technical press, especially as it directly touches our lives.

Despite the Embedded success, Entertainment and devices also turned in a substantial loss, though nothing like the horrors of Online.

Conclusions? One is not to write off Microsoft; it’s still a highly profitable giant. But the other is that the company desperately needs a big success outside Windows and Office to convince us that it really has a bright future. A sparkling launch for Windows Phone 7 would do nicely.

Dysfunctional Microsoft?

Microsoft watchers have been scrutinising the fascinating Mini-Microsoft post on the Kin smartphone debacle and what it says about the company. If it is even slightly accurate, it is pretty bad; and it must be somewhat accurate since we know that the hopeless Kin launch happened and that the product was killed shortly afterwards. Of course it would have been better to kill the project before rather than after the launch; the negative PR impact has affected the strategically important Windows Phone 7 launch.

Handsome profits from Windows and Office have enabled Microsoft to survive and even prosper despite mistakes like Kin, or the Xbox 360 “red ring of death”, or the Vista reset and related problems – mistakes on a scale that would sink many companies.

I see frequent complaints about excessively bureaucratic management with too many layers, and a tendency towards perplexing, ineffective but expensive advertising campaigns.

There are also questions about CEO Steve Ballmer’s suitability for the task. He nearly indulged in a disastrously over-priced takeover of Yahoo, saved only by the obstinacy of the target company’s leadership. He habitually dismisses the competition, such as Apple’s iPhone, and is proved wrong by the market. He failed to see the importance of cloud computing, and even now that the company is at least partially converted he does not set the right tone on the subject. I watched his keynote at the Worldwide Partner Conference (WPC) where he sounded as if he were trying unsuccessfully to imitate Salesforce CEO Marc Benioff from ten years’ ago. Microsoft needs to present a nuanced message about its cloud initiative, not someone shouting “oh cloud oh cloud oh cloud”.

Microsoft is also copying its competition as never before. Bing has a few innovations, but is essentially a recognition that Google got it right and an attempt to muscle in with a copy of its business model – search, advertising and data mining. Windows Phone 7 occupies a similar position with respect to Apple’s iPhone and App Store. Windows 8 also seems to borrow ideas from Apple.

Nevertheless, Microsoft is not yet a dying company, and it would be a mistake to base too much analysis of the company on something like comments to Mini-Microsoft’s blog – good though it is – since it is a magnet for disaffected employees.

While Ballmer’s effort at the WPC was poor, he was followed by Bob Muglia, president of server and tools, who was excellent. Windows Azure has come on remarkably since its half-hearted preview at PDC 2008; and Muglia comes over as someone who knows what he is trying to achieve and how he intends to get there. The Azure “Appliance” idea, shipping a pre-baked cloud infrastructure to Enterprise customers, is a clever way to exploit the demand for a cloud application model but on hardware owned by the customer.

The eBay announcement at WPC was also quite a coup. eBay will “incorporate the Windows Azure platform appliance into two of its datacenters” later this year; and while it is not clear exactly how much of eBay will run on Azure, these appliance kits represent significant hardware.

We’ve seen other strong releases from Microsoft – server 2008 R2, Exchange 2010, SQL Server 2008 R2, SharePoint 2010 which whatever you think of SharePoint is a solid advance on its predecessor, and of course Windows 7 which has done a lot to rescue Microsoft’s performance and reputation after the Vista disappointment.

I also continue to be impressed by Visual Studio 2010, which is a huge release and works pretty well in my experience.

What about Windows Phone 7? With the market focused on iPhone vs Android, clearly it is in a tough market. If there is something slightly wrong with it on launch, instability or some serious hardware or software flaw, it might never recover. Nevertheless, I do not write it off. I think the design effort is intelligent and focused, and that the Silverlight/XNA/.NET development platform along with Visual Studio is an attractive one, especially for Microsoft Platform developers. VP Scott Guthrie describes the latest SDK here. People still switch phones frequently – something I dislike from an environmental point of view, but which works in favour of new entrants to the market. If Windows Phone 7 is a decent device, it can succeed; I’d rate its long-term chances ahead of HP WebOS, for example, and will be keen to try it when it becomes available.

phonedev

Is there a lot wrong with Microsoft? Yes. Does it need a fresh approach at the very top? Probably. Nevertheless, parts of the company still seem to deliver; and even the Windows Phone 7 team could be among them.

Small Business Server “Aurora” based on Windows Home Server and will have hooks to the cloud

The most interesting session at TechEd in New Orleans last month was one I could not talk about until today. It concerned the next version of Small Business Server, no date announced yet. The next SBS will come in two editions. SBS 7.0 will be conceptually similar to today’s SBS, but updated to Server 2008 R2, Exchange 2010 and so on.

SBS code-name “Aurora” is the compelling one though. It is based on Windows Home Server (or at least the next version of WHS, “Vail”, but with Active Directory added. There are no other apps; you are expected to use cloud services.

The reason this matters is Microsoft’s work on federated Active Directory. What this means is that your local SBS simply manages users, computers and file shares, but the same user accounts also work on cloud-hosted services such as Exchange or SharePoint – or any others that support Active Directory federation.

I love this concept; it is exactly the right thing for SMEs who need to run a properly managed Windows network while using hosted email and other cloud services.

image

Questions remain of course. Will services other than Microsoft’s own BPOS or third-party hosted Exchange and SharePoint support SBS federated Active Directory? And will Microsoft and its partners really steer small businesses in this direction, or focus on SBS 7.0?

More details in this article on The Register.

PS This version of SBS is not too far removed from what I asked for in February 2006.

Bare-metal recovery of a Hyper-V virtual machine

Over the weekend I ran some test restores of Microsoft Hyper-V virtual machines. You can restore a Hyper-V host, complete with its VMs, using the same technique as with any Windows server; but my main focus was on a different scenario. Let’s say you have a Server 2008 VM that has been backed up from the guest using Windows Server Backup. In my case, the backup had been made to a VHD mounted for that purpose. Now the server has been stolen and all you have is your backup. How do you restore the VM?

In principle you can do a bare-metal restore in the same way as with a physical machine. Configure the VM as closely as possible to how it was before, attach the backup, boot the VM from the Server 2008 install media, and perform a system recovery.

Unfortunately this doesn’t work if your VM uses VHDs attached to the virtual SCSI controller. The reason is that the recovery console cannot see the SCSI-attached drives. This is possibly related to the Hyper-V limitation that you cannot boot from a virtual SCSI drive.

The workaround I found was first to attach the backup VHD to the virtual IDE controller (not SCSI), so the recovery console can see it. Then to do a system recovery of the IDE drives, which will include the C drive. Then to shutdown the VM (before the restart), mount both the backup and the SCSI-attached VHDs on the host using diskpart, and use wbadmin to restore each individual volume. Finally, detach the VHDs and restart the VM.

It worked. One issue I noticed though is that the network adapter in the restored VM was considered different to the one in the original VM, even though I applied the same MAC address. Not a great inconvenience, but it meant fixing networking as the old settings were attached to the NIC that was now missing.

I’ve appended the details to my post on How to backup Small Business Server 2008 on Hyper-V.

Don Syme on F#

I’ve posted a lengthy interview with Don Syme, designer of Microsoft’s functional programming language F#. It covers:

  • The genesis of F#
  • Why it is in Visual Studio 2010
  • How it differs from other ML languages
  • Who should use it
  • What it brings to parallel and asynchronous programming
  • Unit testing F#
  • Future plans for F#
  • Book recommendations

One of the questions is: if I’m a C# or C++ developer, what practical, business-benefit reason is there to look at F#? Worth a read if you’ve wondered about that.

Setting up RemoteApp and secure FTP on Windows

I spent some time setting up RemoteApp and secure FTP for a small business which wanted better remote access without VPN. VPN is problematic for various reasons: it is sometimes blocked by public or hotel wifi providers, it is not suitable for poor connections, performance can be poor, and it means constantly having to think about whether your VPN tunnel is open or not. When I switched from connecting Outlook over VPN to connecting over HTTP, I found the experience better in every way; it is seamless. At least, it would be if it weren’t for the connection settings bug that changes the authentication type by itself on occasion; but I digress.

Enough to say that VPN is not always the best approach to remote access. There’s also SharePoint of course; but there are snags with that as well – it is powerful, but complex to manage, and has annoyances like poor performance when there are a large number of documents in a single folder. In addition, Explorer integration in Windows XP does not always work properly; it seems better in Vista and Windows 7.

FTP on the other hand can simply publish an existing file share to remote users. FTP can be horribly insecure; it is a common reason for usernames and passwords to passed in plain text over the internet. Fortunately Microsoft now offers an FTP service for IIS 7.0 that can be configured to require SSL for both password exchange and data transmission. I would not consider it otherwise. Note that this is different from the FTP service that ships with the original Server 2008; if you don’t have 2008 R2 you need a separate download.

So how was the setup? Pretty frustrating at the time; though now that it is all working it does not seem so bad. The problem is the number of moving parts, including your network configuration and firewall, Active Directory, IIS, digital certificates, and Windows security.

FTP is problematic anyway, thanks to its use of multiple ports. Another point of confusion is that FTP over SSL (FTPS) is not the same thing as Secure FTP (SFTP); Microsoft offers an FTPS implementation. A third issue is that neither of Microsoft’s FTP clients, Internet Explorer or the FTP command-line client, support FTP over SSL, so you have to use a third-party client like FileZilla. I also discovered that you cannot (easily) run a FTPS client behind an ISA Server firewall, which explained why my early tests failed.

Documentation for the FTP server is reasonable, though you cannot find all the information you need in one place. I also found the configuration perplexing in places. Take this dialog for example:

image

The Data Channel Port Range is disabled with no indication why – the reason is that you set it for the entire IIS server, not for a specific site. But what is the “External IP Address of Firewall”? The wording suggests the public IP address; but the example suggests an internal, private address. I used the private address and it worked.

As for RemoteApp, it is a piece of magic that lets you remote the UI of a Windows application, so it runs on the server but appears to be running locally. It is essentially the same thing as remote desktop, but with the desktop part hidden so that you only see the window of the running app. One of the attractions is that it looks more secure, since you can give a semi-trusted remote user access to specified applications only, but this security is largely illusory because under the covers it is still a remote log-in and there are ways to escalate the access to a full desktop. Open a RemoteApp link on a Mac, for example, and you get the full desktop by default, though you can tweak it to show only the application, but with a blank desktop background:

image

Setup is laborious; there’s a step by step guide that covers it well, though note that Terminal Services is now called Remote Desktop Services. I set up TS Gateway, which tunnels the Terminal Server protocol through HTTPS, so you don’t have to open any additional ports in your firewall. I also set up TS Web Access, which lets users navigate to a web page and start apps from a list, rather than having to get hold of a .RDP configuration file or setup application.

If you must run a Windows application remotely, RemoteApp is a brilliant solution, though note that you need additional Client Access Licenses for these services. Nevertheless, it is a shame that despite the high level of complexity in the configuration of TS Gateway, involving a Connection Authorization Policy and a Resource Authorization Policy, there is no setting for “only allow users to run these applications, nothing else”. You have to do this separately through Software Restriction Policies – the document Terminal Services from A to Z from Cláudio Rodrigues at WTS.Labs has a good explanation.

I noticed that Rodrigues is not impressed with the complexity of setting up RemoteApp with TS Gateway and so on on Windows Server 2008 R2:

So years ago (2003/2004) we had all that sorted out: RDP over HTTPS, Published Applications, Resource Based Load Balancing and so on and no kidding, it would not take you more than 30 minutes to get all going. Simple and elegant design. More than that, I would say, smart design.

Today after going through all the stuff required to get RDS Web Access, RDS Gateway and RDS Session Broker up and running I am simply baffled. Stunned. This is for sure the epitome of bad design. I am still banging my head in the wall just thinking about how the setup of all this makes no sense and more than that, what a steep learning curve this will be for anyone that is now on Windows Server 2003 TS.

What amazes me the most is Microsoft had YEARS to watch what others did and learn with their mistakes and then come up with something clean. Smart. Unfortunately that was not the case … Again, I am not debating if the solution at the end works. It does. I am discussing how easy it is to setup, how smart the design is and so on. And in that respect, they simply failed to deliver. I am telling you that based on 15+ years of experience doing nothing else other than TS/RDS/Citrix deployments and starting companies focused on TS/RDS development. I may look stupid indeed but I know some shit about these things.

Simplicity and clean design are key elements on any good piece of software, what someone in Redmond seems to disagree.

My own experience was not that bad, though admittedly I did not look into load balancing for this small setup. I agree though: you have to do a lot of clicking to get this stuff up and running. I am reminded of the question I asked a few months back: Should IT administration be less annoying? I think it should, if only because complexity increases the risk of mistakes, or of taking shortcuts that undermine security.

Ten years of Microsoft .NET – but what about the next ten?

Technology products have many birthdays – do you count from first announcement, or release to manufacturing, or general availability? Still, this week is a significant one for Microsoft .NET and the C# language, which was first unveiled to the world in detail at Tech-Ed Europe on July 7th, 2000. The timing was odd; July 7th was the last day of Tech-Ed, whereas news at such events is normally reserved to the first day or two – but the reason was to preview the announcement at the Professional Developers Conference in Orlando the following week. It was one of the few occasions when Europe got the exclusive, though as I recall most of the journalists had already gone home.

It is interesting to look back, and I wrote a piece for The Register on .NET hits and misses. However you spin it, it’s fair to say that the .NET platform has proved to be one of Microsoft’s better initiatives, and has delivered on at least some of its goals.

It is even more interesting to look forward. Will we still be using .NET in 2020?

There is no sign of Microsoft announcing a replacement for .NET; and little sign of .NET catching on in a big way outside the Microsoft platform, so in part the question is about how the company will fare over the coming decade. Still, it is worth noting that the role of the .NET framework  in that platform still seems to be increasing.

Most predictions are wrong; but the general trend right now is towards the cloud+device computing model. The proposition is that both applications and data belong in the cloud, whether public, private or hybrid. Further, it seems plausible that we will fall out of love with personal computers, with all their complexity and vulnerability to malware, and embrace devices that just work, where the operating system is locked down, data is just a synchronised local cache, and applications are lightweight clients for internet services. Smartphones are already like this, but by the end of this year when Apple’s iPad has been joined by other slates and small computers running Google Android, Google ChromeOS, Intel/Nokia MeeGo and HP WebOS, it may be obvious that traditional laptop and desktop computers will decline.

It turns out that the .NET Framework is well suited to this model, so much so that Microsoft has made it the development platform for Windows Phone 7. Why stop at Windows Phone 7 – what about larger devices that run only .NET applications, sandboxed from the underlying operating system and updated automatically over the Internet? Microsoft cannot do that for Windows as we know it, because we demand compatibility with existing applications, but it could extend the Windows Phone 7 OS and application model to a wider range of devices that take over some of the tasks for which we currently use a laptop.

In theory then, with Azure in the cloud and Silverlight on devices, the next ten years could be good ones for the .NET Framework.

That said, it is also easy to build the case against. Microsoft has it all to do with Windows Phone 7; the market is happily focused on Apple and Google Android devices at the high end. Microsoft’s hardware partners are showing signs of disloyalty, after years of disappointment with Windows Mobile, and HP has acquired Palm. If Windows Phone 7 fails to capture much of the market, as it may well do, then mobile .NET will likely fail with it. Put this together with a decline in traditional Windows machines, and the attraction of .NET as a cloud-to-client framework will diminish.

Although developer platform VP Scott Guthrie, C# architect Anders Hejlsberg and others are doing an excellent job of evolving the .NET framework, it is the success or failure of the wider Microsoft platform that will determine its future.