Skip to main content

Thoughts on the Surface 2 Pro

I've recently been lucky enough to get a Surface 2 Pro to play with - the top of the range 8GB RAM, 256GB storage version. I'd been looking at the Surface 2 for a while, wanting to see what Windows 8 is like on a small touch screen device - I still think the surface could go either way, it's not getting the traction of other mobile devices / platforms and Windows 8 is certainly not without it's critics. Over the past couple of years I've owned Android devices, iPhones and iPads, a windows 8 mobile and now the surface 2 Pro. I can still remember being impressed with the iPad as it just worked, everything you wanted it to do it did quickly and well. Similarly I was really impressed with the UI on the Windows phone - the battery life was a little bit disappointing and it was frustrating that you had to remember to shut down all the apps to maximise the battery but UI really liked the UI and it seemed to take the concept of exposing social updates for your contacts that Android started to a new level. The Surface 2 Pro has impressed me, but for other reasons. Obviously the "Pro" part means it will run desktop applications, and it does that well - Visual Studio 2013 starts up in under 3 seconds - many factors faster than the parallels VM running on my work MBP (and that has 16GB, plus SSD, etc.). The touch keyboard, whilst stupidly expensive, is great - back lit and tactile, has a trackpad too. A nice feature is if you swing the cover all the way round the keyboard switches itself off so you don't have to worry about pressing any keys whilst holding it. What I've really liked is the stylus and one-note; it's the closet thing I've come to replacing a pen and paper notebook in meetings; in fact I think once I get a little bit more used to it, it will eventually replace the notebook. Battery life has also been really good; easily getting 4 or more hours without having to worry about plugging it in. It can get a bit hot when doing processing work and when the fan kicks in; it's not as quiet as you'd expect a mobile device to be. Windows 8.1 works really nicely on the touch screen too, switching between touch and the keyboard is natural and easy. I'm writing this article with the device on my lap, the keyboard sits well and the kick stand keeps the screen at a nice angle; it's replacing the laptop when I just have something quick to do but needing a bit more power / typing that would be comfortable on an iPad / phone. Eventually I want to see about getting a wireless keyboard/mouse and hook it up to a monitor to see if it can replace a windows laptop completely.

Comments

Popular posts from this blog

Mocking HttpCookieCollection in HttpRequestBase

When unit testing ASP.NET MVC2 projects the issue of injecting HttpContext is quickly encountered.  There seem to be many different ways / recommendations for mocking HttpContextBase to improve the testability of controllers and their actions.  My investigations into that will probably be a separate blog post in the near future but for now I want to cover something that had me stuck for longer than it probably should have.  That is how to mock non abstract/interfaced classes within HttpRequestBase and HttpResponseBase – namely the HttpCookieCollection class.   The code sample below illustrates how it can be used within a mocked instance of HttpRequestBase.  Cookies can be added / modified within the unit test code prior to being passed into the code being tested.   After it’s been called, using a combination of MOQ’s Verify and NUnit’s Assert it is possible to check how many times the collection is accessed (but you have to include the set up calls) and that the relevant cookies have …

Injecting HttpContextBase into an MVC Controller

It is a shame that when the ASP.NET MVC framework was released they did not think to build IoC support into the infrastructure. All the major components of the MVC engine appear to magically inherit instances of HttpContext and it’s related objects – which can cause no end of problems if you are trying to utilise Unit Testing and IoC. Reading around various articles on the subject just to get around this one problem requires the implementation of several different concepts and you are still left with a work around. The code below, along with the other links referenced in this article is my stab at resolving the issue. There’s probably nothing new here, but it does attempt to relate all the information needed to do this for Castle Windsor. The overview is that all controllers will need to inherit from a base controller, which takes an instance of HttpContext into it’s constructor. It then overrides the property HttpContext in the main controller class, supplying it’s own version…

Unit Testing Workflow Code Activities - Part 1

When I first started looking into Windows Workflow one of the first things that I liked about it was how it separated responsibilities. The workflow was responsible for handling the procedural logic with all it's conditional statements, etc. Whilst individual code activities could be written to handle the business logic processing; created in small easily re-usable components. To try and realise my original perception this series of blog posts will cover the unit testing of bespoke code activities; broken down into: Part One: Unit testing a code activity with a (generic) cast return type (this post)Part Two: Unit testing a code activity that assigns it's (multiple) output to "OutArguments" (Not yet written)So to make a start consider the following really basic code activity; it expects an InArgument<string> of "Input" and returns a string containing the processed output; in this case a reverse copy of the value held in "Input".namespace Ex…