Tag Archives: windows

Microsoft Build Sessions published: Windows Phone XAML and HTML/JS apps, new Azure APIs and more

Developing for Windows Phone is now closer to developing for the Windows 8 runtime, according to information from Microsoft’s Build sessions, just published.

Build is Microsoft’s developer conference which opens tomorrow in San Francisco.

image

Building a Converged Phone and PC App using HTML and JavaScript states that “An exciting part of Windows Phone 8.1 is that you can now start building applications natively in HTML and JavaScript.”

Other sessions refer to the Common XAML UI Framework, which seems to refer to a shared UI framework for Windows Phone and WIndows 8, but using XAML rather than HTML and JavaScript.

This is in addition to Silverlight, not instead, judging by this session:

We’ve been doing a lot of work with new converged XAML app support on Windows Phone 8.1, but what about legacy Windows Phone Silverlight XAML based apps?  Come learn about all the new features we’ve enabled with Silverlight 8.1.

Microsoft has also come up with new APIs for applications that integrate with its Azure cloud platform and with Office 365. The Authentication library for Azure Active Directory lets you build both Windows and mobile applications that authenticate against Azure Active Directory, used by every Office 365 deployment. There is also talk of using Azure for Connected Devices, meaning “Internet of Things” devices using Azure services.

Some other sessions which caught my eye:

Connected Productivity Apps: building apps for the SharePoint and Office 365 platform.

What’s new in WinJS: the road ahead. XAML vs HTML/JS is a big decision for Windows developers.

Anders Hejlsberg on TypeScript

Automating Azure: “The Azure Management Libraries and Azure PowerShell Cmdlets allow this type of automation by providing convenient client wrappers around the Azure management REST API”

Authentication library for Azure Active Directory: The Active Directory Authentication Library (ADAL)

Panel discussion on desktop development: is there a future for WPF? Maybe some clues here.

Miguel de Icaza gets a session on going mobile with C# and Xamarin. I recall when de Icaza ran sessions on Mono, the open source implementation of the .NET Framework which he initiated shortly after Microsoft announced .NET itself, in nearby hotels at Microsoft events; now he is inside.

Learning from the mistakes of Azure: Mark Russinovich on what can go wrong in the cloud.

Looks like both cloud and apps for Windows Phone/Windows 8 are big themes at Build this year.

Entering Microsoft’s XAML labyrinth: is it worth it?

I spent some time at the weekend working on a Bridge game for the Windows Store. I am writing it in XAML and C#. The UI is hardly demanding, given that Bridge is a card game, but it has made me take a fresh look at XAML, the markup language for a Windows Store App user interface (unless you use HTML and JavaScript). XAML is also used in Windows Presentation Foundation and in Silverlight/Windows Phone.

As part of the game, the user selects a “bid” which consists of a number from 1 to 7 and a suit of cards (or double, redouble or pass). Most bridge games show this as a grid though functionally it is like a combo-box (choosing from a pre-defined range of options).

Naturally I looked for the easiest way to accomplish this. The solution I came up with was to nest TextBlock controls in Border controls in Grid cells. Then I wrote C# code that detects which cell the user taps and updates the background of the selected Border accordingly.

image

I have in mind to replace the text with graphics and make the numbers a bit smarter at some future date. My solution works fine; here it is at runtime:

image

At the weekend I happened to be chatting with a developer more expert in XAML than myself, who told me I had done it wrong. In XAML everything should be in Style definitions. I should use a ListView and design it in Blend.

Well, I knew that I had somewhat subverted how XAML is meant to work, so I sat down to investigate this different approach. A ListView looks nothing like what I want out of the box.

image

However, with the magic of XAML it can be transformed. I made the ListView horizontal by defining an ItemsPanelTemplate in Application.Resources:

<ItemsPanelTemplate x:Key="ItemsPanelTemplate1">
  <StackPanel Orientation="Horizontal"/>
</ItemsPanelTemplate>

and adding 

ItemsPanel="{StaticResource ItemsPanelTemplate1}

as an attribute of the ListView.

Then I added an ItemTemplate to draw the kind of block that I wanted:

<ListView.ItemTemplate>
    <DataTemplate>
        <Border BorderThickness="1" Height="130" Width="130" BorderBrush="Black">
            <TextBlock FontSize="24" FontWeight="Bold" HorizontalAlignment="Center" VerticalAlignment="Center"
                       Text="{Binding Name}" Foreground="Black" />
        </Border>
    </DataTemplate>
</ListView.ItemTemplate>

Note that I am using a DataTemplate because the ListView is bound to an ObservableCollection in the proper XAML way.

At this point I am close to what I want – never mind that the numbers are missing, they can easily be added with a second ListView:

image

However I do not want that little tick mark appearing, the selected background colour is not to my taste, and the spacing of the items is wrong. How do I fix that?

My search led me to this post which explains a far-from-obvious series of steps you can take in Blend. The steps did not quite work for me but got me on track to create a new Style resource which I called ListViewItemStyleNoGlyph and which lets me adjust the margin and also a previously hidden property called SelectionCheckMarkVisualEnabled. Blend generated a substantial block of code for this:

image

This has helped and now my ListView looks like this:

image

Well, it is nearly there and I can see that with a bit more effort I can get what I want. Even so, I am beginning to wonder whether my initial approach, in which I understood all the code, had advantages over this exploration into the labyrinth.

Is XAML well loved out there? I came across this post by Paul Stovell from a couple of years back which seems relevant. “I’ve lived and breathed the technology for the last six years”, he says, but writes:

What’s disappointing is that WPF started out quite positively during its time. Concepts like dependency properties, styles, templates, and the focus on data binding felt quite revolutionary when Avalon was announced.

Sadly, these good ideas, when put into practice, didn’t have great implementations. Dependency properties are terribly verbose, and could have done with some decent language support. Styles and templates were also verbose, and far more limited than CSS (when WPF shipped I imagined there would be a thousand websites offering high quality WPF themes, just like there are for HTML themes; but there aren’t, because it is hard).

Data binding in WPF generally Just Works, except when it doesn’t. Implementing INotifyPropertyChanged still takes way too much code. Data context is a great concept, except it totally breaks when dealing with items like ContextMenus. ICommand was built to serve two masters; the WPF team who favored routed commands, and the Blend team who favored the command pattern, and ended up being a bad implementation for both.

Stovell mentions the verbosity of XAML, and that it is hard, both of which sound right to me. He contrasts the way ASP.NET has evolved, with ASP.NET MVC a great improvement on web forms. Read the full post for more detail.

It seems to me that XAML does offer much that is wonderful: flexibility, capability, and the ability to separate presentation from data. At the same time, neither XAML nor Blend are intuitive tools for developers; they may make more sense to designers, but it seems to me that removing a tick mark from a ListViewItem should be more straightforward. Perhaps it is, in which case there is a failure of documentation or tooling rather than functionality, but it makes little difference to the developer.

Thirty years of mainly not the Mac

It’s Mac anniversary time: 30 years since the first Macintosh (with 128K RAM) in 1984 – January 24th according to Wikipedia; Apple’s beautiful timeline is rather sketchy when it comes to details like actual dates or specs.

My first personal computer though was a hand-me-down Commodore PET 4032 with only 32K of RAM, which pre-dated the Mac by about 4 years (though not by the time I got hold of it).

image

The PET was fun because it was small enough that you could learn almost everything there was to know about it though a book called The PET Revealed that listed every address and what it did. I had a word processor called Wordcraft that was excellent, provided you could live with only having one page in memory at a time; a spreadsheet called VisiCalc that was even better; and a database that was so bad that I forget its name. You could also play Space Invaders using a character-based screen; the missiles were double-dagger (ǂ)characters.

The small company that I was a little involved with at the time migrated to Macs almost as soon as they were available so I had some contact with them early on. The defining moment in my personal computer history though was when I needed to buy a new machine for a college course. What would it be?

If all the choices had cost the same, I would have purchased a Mac. My second choice, since this was a machine for work, would have been a PC clone. Both were expensive enough that I did not seriously consider them.

Instead, I bought a Jackintosh, sorry an Atari ST, with a mono 640 x 200 monitor and a second disk drive. It had the GEM graphical user interface, 512K RAM, a Motorola 68000 CPU, and built-in MIDI ports making it popular with musicians.

The ST exceeded expectations. Despite being mainly perceived as a games machine, there were some excellent applications. I settled on Protext and later That’s Write for word processing, Signum for desktop publishing, Logistix for spreadsheets, Superbase for database, the wonderful Notator for messing around with MIDI and music notation, and did some programming with GFA Basic and HiSoft C.

If I had had a Mac or PC, I would have benefited from a wider choice of business applications, but lost out on the gaming side (which I could not entirely resist). The ST had some quirks but most things could be achieved, and the effort was illuminating in the sense of learning how computers and software tick.

Despite the Mac-like UI of the Atari ST, my sense was that most Atari owners migrated to the PC, partly perhaps for cost reasons, and partly because of the PC’s culture of “do anything you want” which was more like that of the ST. The PC’s strength in business also made it a better choice in some areas, like database work.

I was also doing increasing amounts of IT journalism, and moving from ST Format to PC Format to Personal Computer World kept me mainly in the PC camp.

For many years though I have found it important to keep up with the Mac, as well as using it for testing, and have had a series of machines. I now have my desktop set up so I can switch easily between PC and Mac. I enjoy visiting it from time to time but I am not tempted to live there. It is no more productive for me than a PC, and Microsoft Office works better on a PC in my experience (no surprise) which is a factor. I miss some favourite utilities like Live Writer, dBpoweramp, and Foobar 2000.

That said, I recognise the advantages of the Mac for many users, in terms of usability, design, and fewer annoyances than Windows. Developers benefit from a UNIX-like operating system that works better with open source tools. There is still a price premium, but not to the extent there was when I picked an Atari ST instead.

Happy Anniversary Apple.

Something Microsoft has never fixed: why Windows is slow to start up

One of the most common complaints I hear about Windows is that it is slow to start up. Everything is fine when a machine is new (especially if it is a clean install or purchased from a Microsoft store, and therefore free from foistware), but as time goes on it gets slower and slower. Even a fast PC with lots of RAM does not fix it. Slow boot is one of many factors behind the drift away from PCs to tablets, and to some extent Macs.

image

As far as I can tell, the main reason PCs become slow to start is one that has been around since DOS days. Some may recall fussing about TSR – Terminate and Stay Resident – applications that would run at startup and stay in memory, possibly causing other applications to fail. Windows today is generally stable, but it is applications that run at startup that cause your PC to start slowly, as well as having some impact on performance later.

I install lots of software for testing so I suffer from this myself. This morning I took a look at what is slowing down my desktop PC. You can view them easily in Windows 8, in Task Manager – Startup tab. A few of the culprits:

  • Adobe: too much stuff, including Service Manager for Creative Suite, Creative Cloud connection, Acrobat utilities
  • Intel Desktop utilities – monitors motherboard sensors
  • Intel Rapid Storage Technology – monitors on-board RAID
  • Sync applications including SkyDrive, Dropbox, SkyDrive Pro (Groove.exe)
  • Seagate Desktop, manage your Seagate NAS (network attached storage)
  • Google stuff: Google Music Manager, Google update, some Chrome updater
  • Plantronics headset updater
  • Realtek HD Audio Manager
  • Fitbit Connect client
  • SpotifyWebHelper
  • Microsoft Zune auto-launcher
  • Microsoft Lync, famously slow to start up and connect
  • Roccat Gaming mouse settings manager
  • Flexera “Common software manager” (InstallShield updater)

Many of these applications run in order to install a notification app – these are the things that run at bottom right, in the notification area of the taskbar. Some apps install their own schedulers, like the Seagate app which lets you schedule backup tasks. Some apps are there simply to check for updates and inform you of new versions.

You can speed up Windows startup by going through case by case and disabling startup items that you do not need. Here is a useful guide. It is an unsatisfactory business though. Users have no easy way to judge whether or not a specific app is doing an important or useful task. You might break something. When you next update the application, the startup app may reappear. It is a mess.

Microsoft should have addressed this problem aggressively, years ago. It did put great effort into making Windows boot faster, but never focussed on the harder task of bringing third-parties into line. A few points:

  • If Windows had a proper notification service, many of these apps would not need to exist. In Windows 8, it does, but that is little help since most applications need to support Windows 7 and even in many cases Windows XP.
  • The notification area should be reserved for high priority applications that need to make users aware of their status at all times. The network connection icon is a good case. Printer ink levels are a bad case, aside from reminding us of the iniquity of printer vendors selling tiny ink cartridges at profiteering prices. In all cases it should be easy to stop the notification app from running via a right-click preference. The Windows 7 idea of hiding the notification icons is counter-productive: it disguises the problem but does not fix it, therefore making it worse. I always set Windows to show all notifications.
  • Many tasks should be done on application startup, not on Windows startup. Then it is under the user’s control, and if the user never or rarely runs the application, no resources are grabbed. Why do I need to know about an update, if I am not running the application? Have the application check for updates each time it runs instead.
  • It is misguided to run a process on start-up in order to speed up the first launch of the application. It may not be needed.
  • If a background process is needed, such as for synchronisation services, why not use a Windows Service, which is designed for this?
  • Windows has a scheduler built in. It works. Why write your own?

Of course it is too late now for desktop Windows. Microsoft did rethink the matter for the “Metro” personality in Windows 8, which is one reason why Windows RT is such a pleasure to use. Apple does not allow apps to run on startup in iOS, though you can have apps respond to push notifications, and that strikes me as the best approach.

Update: I should mention a feature of Windows 8 called Fast Boot (I was reminded of this by a commenter – thanks Danny). Fast Boot does a hybrid shutdown and hibernation:

Essentially a Windows 8 shutdown consists of logging off all users and then hibernating.

This is almost another subject, though relevant. Microsoft has for years sought to address the problem of slow boot by designing Windows never to switch off. There are two basic approaches:

Sleep: the computer is still on, applications are in memory, but in a low power state with screen and hard drives off.

Hibernation: the computer writes the contents of its memory to disk storage, then powers off. On startup, it reads back the memory and resumes.

My own experience is that Sleep does not work reliably long-term. It sometimes works, but sooner or later it will fail to resume and you may lose data. Another issue on portables is that the “low-power state” is not as low power as it should be, and your battery drains. These factors have persuaded me to shut down rather than sleep.

My experience of hibernation is better, though not perfect. It usually works, but occasionally fails and again you lose data.

Fast boot is a clever solution that works for some, but it is a workaround that does not address the real issue which I have outlined above: third-party and Microsoft applications that insist on automatic start-up.

What next for Windows as Microsoft announces Build 2014?

Microsoft has announced Build 2014, its premier developer conference for Windows, April 2-4 in San Francisco.

image

In his blog post on the subject, developer evangelist Steve Guggenheimer mentions the Windows 8 app platform and Xbox One, and promises that Microsoft will talk about “what’s next for Windows, Windows Phone, Windows Azure, Windows Server, Visual Studio and much more.”

How is the buzz around Microsoft right now? Here are a few things that are not so good:

  • The Windows 8 app platform continues to struggle, despite picking up slightly from its dismal launch. Most of the conversation I hear around Windows 8 looks back to Windows 7 rather than forward to the new tablet platform: will the Start menu return?
  • The decline of the PC remains in full flow, while the non-Windows mobile platforms iOS and Android continue to grow
  • Xbox One, with its focus on Kinect and family entertainment, is falling behind Sony’s PlayStation 4 in terms of which console is most desired. Sony’s cheaper price and higher resolution on games like Call of Duty Ghosts make it a better for buy for gamers who can live without Kinect

On the other hand, a few positives:

  • Microsoft’s cloud platforms Office 365 and Windows Azure are growing fast, as far as I can tell
  • Server 2012 R2 is a solid upgrade to an already strong server product, and Hyper-V is making progress versus VMWare in virtualisation
  • Windows Phone 8 is making some progress in market share, though whether it will cross the point at which it becomes important enough for companies with apps to feel they have to support it remains an open question (currently they mostly do not)

What does that mean for Build? We may of course just see more of the same: improvements to Windows 8.x, further convergence with Windows Phone and Xbox platforms, new features for Windows Server and Azure, early previews of the next Visual Studio to support the new stuff.

I wonder though whether we may also see some new directions. Microsoft is supporting Xamarin for cross-platform mobile development and it would not surprise me to see more being made of this, or possibly some new approaches, to promote the use of Microsoft’s cloud services behind apps that run on iOS and Android.

Microsoft still intends for Windows 8/Windows Phone to be a major mobile platform alongside iOS and Android but its progress in reaching that point is slow. The task of building its cloud platform seems to be going better, despite competition from the likes of Amazon and Google, and in this context deep integration with the Windows client could be as much a liability as an advantage.

It may seem perverse; but it could pay Microsoft to focus on improving how well its server offerings (and Office) work with iOS and Android, rather than pushing for Windows everywhere as it has done in the past.

Will Microsoft scrap Windows RT? Here’s why it might not matter

At the UBS Global Technology Conference (aimed at investors, since UBS is an investment bank), Windows Executive Vice President Julie Larson-Green was interviewed about the future of Windows, and Microsoft has helpfully posted the audio and full transcript.

Larson-Green was asked about the viability of the “dual track” for Windows, or put another way, does Windows RT have a future?

I will interject an anecdote here. A neighbour came to me this weekend with a Windows XP laptop. Internet Explorer 8 no longer worked, and as no other web browser was installed, she could no longer get to the web on that machine. Microsoft has advice on reinstalling IE8; you re-run setup. We downloaded the setup from another machine and re-ran setup. It made no difference.

The only clue was an icon in the notification area for secure search. What was it? My neighbour did not know. She mentioned that she had been offered a free backup service and had started installing it. The service informed her that her backup was too large and she would have to pay. She thought she had cancelled and uninstalled it successfully, but maybe this toolbar, which redirects all searches to conduit.com, came along for the ride. Removing the toolbar from add/remove programs brought IE 8 back to life; if she is lucky, that will be end of the incident, if not, there could be other surprises.

It is just hopeless; and although later versions of Windows have improved security, users ultimately have full control of their machines and therefore the ability (with the help of unscrupulous third parties) to break them.

Now listen to Larson-Green’s description of Windows RT, evidence that Microsoft understands these issues very well:

Windows on ARM, or Windows RT, was our first go at creating that more closed, turnkey experience, where it doesn’t have all the flexibility of Windows, but it has the power of Office and then all the new style applications. So you could give it to your kid and he’s not going to load it up with a bunch of toolbars accidentally out of Internet Explorer and then come to you later and say, why am I getting all these pop-ups. It just isn’t capable of doing that by design.

That said, in its first year on the market Windows RT has largely failed. OEMs like Lenovo and Dell, who produced Windows RT tablets last year, have abandoned it. Microsoft is now the only Windows RT vendor, with Surface RT and Surface 2, other than Nokia with the Lumia 2520 – wait, that’s Microsoft too, following the Nokia acquisition.

Why has RT failed? Performance is an issue on most first generation devices (solved on Surface 2), users have been infuriated and/or flummoxed by the inability to install desktop applications, and even those (like myself) who understand and like the Windows RT concept run into functionality gaps, where there is no suitable Windows Store app and nothing built into the desktop that will do.

Nevertheless, something like Windows RT is necessary if Windows is to survive as a mainstream client operating system. What are Microsoft’s plans?

We have the Windows Phone OS. We have Windows RT and we have full Windows. We’re not going to have three. We do think there’s a world where there is a more mobile operating system that doesn’t have the risks to battery life, or the risks to security. But, it also comes at the cost of flexibility. So we believe in that vision and that direction and we’re continuing down that path.

You can read this as saying that Windows RT will be scrapped, to be replaced by Windows Phone OS adapted for larger form factors (which is what some of us thought Microsoft should have done three years ago). Some have drawn that conclusion, even in the mainstream press. However, this is not what Larson-Green said. Rather, she confirmed what has been strongly hinted for some time, that Windows Phone and Windows RT will converge. In fact, the company has already said that there will be a single development platform for Windows Store / Phone apps at some future date. Note that Windows Phone 8 is no longer built on Windows CE, the cut-down version of Windows, but uses the full Windows kernel, so some convergence has already taken place.

There are rumours of a battle within Microsoft: should Windows Phone adopt Windows RT, or vice versa? Windows Phone is increasing its market share, whereas Windows RT struggles, so from a marketing perspective the phone may be the winner here, though from a technical perspective it might be better to adapt Windows RT for the phone so that desktop Office remains possible on future devices.

If Microsoft gets this right, it will not matter to end users which way it goes. Here is what makes sense to me. Microsoft should converge the development platforms for Windows Phone and Windows Store apps so that both types of apps run on both platforms (though developers should be able to specify a minimum display size to avoid issues with apps designed for a larger screen), and a single project in Visual Studio should be able to target both platforms.

The most interesting question is the future of the desktop on Windows ARM tablets. I love having the desktop on Surface RT and Surface 2, because it greatly increases the utility of the devices; my perspective is that it’s great to have the Windows desktop and Office on a locked-down device, rather than lamenting the inability to install new desktop applications. However, it is a compromise that needs keyboard and trackpad or mouse for optimum operation, and means that Windows RT devices suffer from the same dual personality issues as full Windows 8.

If Microsoft managed to implement a decent version of Office as a Windows Store app, could we live without the desktop? Maybe, though I doubt it will be easy to match the full Windows version of Office (even without VBA) in the Windows Runtime environment.

Microsoft Surface 2: still a hard sell at retail

I am a fan of Microsoft’s Surface 2; but looking at the display at Dixons in Heathrow’s Terminal 3 it is obvious that Microsoft has work to do in terms of retail presence.

There are no clues here as to why anyone might want to buy a Surface, and no indication that Surface 2 runs anything other than standard Windows 8, other than the two letters RT which you can read on the spec summary.

Windows RT is both better and worse than Windows on Intel. It is worse because you cannot install new desktop applications, but it is better because it is locked down and less likely to suffer from viruses or annoying OEM add-ons and customisations that usually result in a worse user experience.

Why did Microsoft not come up with a distinctive brand name for RT, such as AppWindows or StoreWindows or WinBook? I am open to negotiation should Microsoft wish to use one of my brand ideas 🙂

Surface 2 has excellent performance, Microsoft Office is bundled including Outlook (though without the ability to run Visual Basic macros), and it is expandable using Micro SD cards or USB 3.0 devices, all features I miss when using an Apple iPad.

I do use the desktop a lot on Surface 2. Simple applications like Paint and Notepad are useful especially since they have, you know, cool resizable and overlapping windows so you can have multiple applications on view.

The Apple iPad is better displayed and I am sure its greater prominence is more than justified by relative sales.

 

Users report SkyDrive issues: sync failures, Microsoft Account problems

SkyDrive, Microsoft’s cloud storage service, is critical to the company’s strategic direction for Windows. It is the means by which content and settings are kept in synch across different Windows machines; or more precisely, user accounts across different Windows machines.

Content in SkyDrive is accessible via any web browser, and there are clients for Windows and for various mobile devices. Office Web Apps are also built-in so you can create and edit documents in the cloud.

In principle it is an excellent service, but since the release of Windows 8.1 a few problems have emerged. Specifically:

Some users report problems synching. Check out this thread which begins with users of the 8.1 preview but continues through to the release. The main issue mentioned is that synchronisation simply fails for some users, but others report duplicate documents created with names like somedoc-mypc.xls and somedoc-mylaptop.xls, where “mypc” and “mylaptop” are the names of computers used with the service. Working out which document is the most current can be tricky.

I have encountered this myself, even on some occasions with a document created and edited solely on one machine. Somehow SkyDrive manages to think there is a conflict.

Another problems is unnecessary network traffic. Here is an example of some of these issues:

My brand new shiny Surface Pro 2 was set to have the documents available offline and everything else online only.  The sync has stalled just like everyone else reports in this thread.  I changed the folder to "online only" and the sync claimed to complete.  I then changed the folder back to "available offline" and it proceeded to redownload thousands of files, finally stalling again with a little more than 200 left.  The Metro app says that the files have completed yet they are still in the pending queue.

Many users express what seems to me a valid complaint, that Windows 8.1 gives you less information and control than was in Windows 8.0.

Some users dislike being tied to a Microsoft account. SkyDrive is a consumer service, and you can only use it with a Microsoft account (MSA) – a descendant of what was once called Passport. In Windows 8 and earlier, which had standalone SkyDrive clients, that was not too bad. You can sign into SkyDrive just as you would into Dropbox or any cloud service. In Windows 8.1 though, SkyDrive is baked into the operating system, which means that you have to sign in centrally to a Microsoft account.

There are several reasons users struggle with this, including privacy concerns, inconvenience if you have more than one SkyDrive account you want to use, and complications when you have a corporate login to a Windows domain as well as SkyDrive:

When I login with my domain account and connect my MSA to it, Skydrive still won’t sync, it keeps creating "Skydrive" folders in the user directory each time it tries to start. I can’t find anything in the logs to help.

If I instead login with the MSA account to the computer it will sync.

SkyDrive is a free service and Microsoft has good reason to encourage users to sign in with one of its accounts, which gives access to the Windows Store, Xbox Music and other services. I can see why users object, but also why Microsoft wants to encourage users to sign in.

It is harder to understand why the service does not work reliably. The impression I get is that this is more to do with the client, especially in Windows 8.1, than with the cloud service; but it is hard to be sure.

How extensive are the problems? Again, it is hard to get firm data. I find it works reasonably well for me, though I get the duplicate file problem as well as regular issues saving Office documents. The notorious Office Upload Center reports a problem and you have to re-open the document in Office and save to resolve it.

Asus Transformer Book Trio combines Windows and Android – but what is it for?

Microsoft has one idea about how to combine desktop Windows with a tablet OS: mash them together into a single operating system and call it Windows 8.

Asus has another idea. Put Windows in the keyboard dock, Android in the tablet, and allow the tablet to be docket to form a Windows or Android laptop.

This is the Transformer Book Trio, just launched and on sale from 11 November 2013 at £899.99.

image

All my instincts say this a terrible idea. Let Windows be Windows and Android Android, do not try to combine them.

Trying the machine though I found it was good fun. Just press the little Android button and it switches.

image 

and it becomes an Android laptop:

image

The dock mechanism is a bit ugly but looks robust:

image

There is the question still: what will you do with the keyboard when not in use? In a home context that is not a problem, but when on the road I find the most convenient place to keep a detachable keyboard is to attach it, making it more of a laptop than a tablet in practice.

Having two computers in one gives you a few options, which I did not have time to explore in detail. As I understand it, you can share storage in order to open a document prepared in Windows on Android, for example, and with two batteries there is scope for charging one from the other.

This is two separate computers though. It should really be called Duo, but Asus calls it Trio on the grounds that you can use it as a laptop or a desktop machine, with an external display.

The PC runs an Intel Core i5 4200U, and has 4GB RAM and 500GB hard drive. The display is 1920 x 1080 and supports capacitive 10-point multi-touch. Connectivity includes 802.11ac (dual-band) wi-fi, Bluetooth 4.0, 2 USB 3.0 ports, Mini DisplayPort, and Micro-HDMI 1.4.

The tablet has an Intel Atom Z2560 with 2GB RAM and 16GB storage. Connectivity includes   802.11n (2.4GHz), Bluetooth 3.0, Micro-USB 2.0, microSD card slot.

Fun then; but what is the use case for this machine? This is where I am still having difficulty. It is somewhat expensive (though with a Core i5 performance is decent), and I have a hunch that users will end up sticking with one or the other OS most of the time – probably Windows given the price.

Oddly, it would make more sense to me to have a high-end Android device with the ability to run Windows when needed. This would address the case where a user wants to migrate to Android but occasionally needs a Windows app.