October 2014 Blog Posts
Fixing wireless on a Surface Pro 3 under WTP 9860

There are no doubt other ways to do it, and this worked on my machine, so YMMV.

First, go here and download the driver packs.  I think you only need the Surface Pro 3 zip file, but I downloaded all of them for the hell of it.

Next, uninstall your wireless driver from Device Manager, choosing to delete it from your machine.

Then, unzip the zip file (making sure to unblock it, if needed by right-clicking, choosing properties, and choosing unblock).

Then, in device manager, you should have an unidentified network adapter/ethernet controller/whatever, so right-click it, choose to install a driver for it, manually navigate to the unzipped directory, and install it.

You should be good to go, though you will need to reenter your network key when you reconnect to your wireless network.

posted @ Thursday, October 23, 2014 7:28 AM | Feedback (0)
Issues with Windows Technical Preview Build 9860

Note that these are on my machine, which is a Surface Pro 3.  In other words, YMMV.

I see two major issues.

1) My WI-FI connection on my home network is now limited and cannot access the internet (I am writing this using my Clear USB device).  WI-FI has always been squirrely on the Surface Pro 3, but at least it was always able to connect.

2) Visual Studio 2014 CTP can no longer open any solutions properly, throwing errors on Rosyln packages and other things.  Then, when I try to close Visual Studio itself, it says that an array of that object type cannot be null  Going into my AppData folder and clearing out the component cache resolved this issue.

I’m installing the build on another machine to see if it has also broken the WI-FI connection, to see if it is more a Surface Pro 3 thing or WTP thing.


Update: it appears the wireless issue is Surface Pro 3 only, or at least, it is not having the same issue on a Dell XPS machine.

posted @ Tuesday, October 21, 2014 9:34 PM | Feedback (0)
Mongo Repository: You probably shouldn’t do this type of thing

Reading this on InfoQ, I was struck by this:

“The reason for the existence of MongoRepository, to me, is simple: it provides a very 'narrow' abstraction on top of the underlying MongoCSharp Driver that, to me, mostly hides all awesome possibilities it provides behind a simple interface that, basically, supports CRUD. This way you don't get too tempted to use all sorts of Mongo-specific functionality and thus high coupling between a project and mongo is minimized so that, should one ever decide to use a different persistence layer, the 'switch' can be made a bit easier.”

Unless you need to use this sort of thing, you probably shouldn’t use this sort of thing.  And if you need to use this sort of thing.  You should think about if you really need to do this sort of thing.

To be clear, I’ve no doubt MongoRepository itself is well coded and does what it is designed to do.

But, you aren’t going to need to switch persistence layers.  And if you are going to need to switch persistence layers, you are going to need to do work.  And ignoring the functionality of your persistence layer technology almost guarantees that you are going to end up with ‘lowest common denominator’ coding that, almost guaranteed, is going to suck more than if you used the technology of your persistence layer.

You probably also shouldn’t be using the Repository pattern either, but that’s another story.

posted @ Tuesday, October 07, 2014 9:37 AM | Feedback (0)
Windows 10 Technical Preview: The Desktop Window Manager has encountered a fatal error (0x8898008d) – Workaround for my Surface Pro 3

In a previous post, I mentioned one issue that I am running into an issue where my desktop session disappears on my Surface Pro 3, so all open apps/docs/whatever go bye-bye.  This is obviously inconvenient (I would point out that this first preview is supposedly geared towards desktop machines, and so specifically not tablet/laptops like the Surface Pro 3, but that goes without saying, so I won’t mention it).

After some research (more than a minute, less than 20), it seems to be related to sleep.  When the machine goes to sleep, it (almost?) always loses the session.  So, by turning off sleep, it works around the problem.

Except when you need to transport the thing.  You close the Type Cover, it goes to sleep.  Well, let’s just hibernate the thi…… Oh, where’s the hibernate option on the power button?  It isn’t there by default (at least not on mine), because they want the magic “come to life instantly” behavior (or something).  Since I’d rather not lose the desktop session, I can go ahead and do without the magic for the moment.

You can enable hibernate by following the instructions here.  Note that it isn’t clear whether InstantGo still works (in the 3 minutes I’ve spent working on it, my guess is no).


posted @ Monday, October 06, 2014 10:33 AM | Feedback (0)
Nokia Lumia 1520 Battery Life

I just noticed/recalled that I hadn’t charged my phone since yesterday.

After 29 hours since last charge, it has 51% battery left.

Admittedly, I’ve only made a call or two, surfed a couple of pages, and took 4 photos.  But still, damn.  My 1020 would be at –35% or something.

posted @ Saturday, October 04, 2014 9:12 PM | Feedback (0)
Windows 10 Technical Preview: The Desktop Window Manager has encountered a fatal error (0x8898008d)

This is the first significant issue that I’ve run into with the new WTP.  I’ve never seen it happen as it is happening, but a few times now I’ve come back to the machine after locking it, or transporting my Surface Pro 3, and the desktop is totally ‘clear’ (as if I was just logging into it after a reboot, but it hasn’t rebooted that I can tell).

I have no idea what’s causing it yet.

posted @ Saturday, October 04, 2014 5:06 PM | Feedback (0)
Running Windows 10 Technical Preview on a Surface Pro 3

Even though I read somewhere about why you shouldn’t do this on your main development machine, after installing the preview on two other machines without issue, I made the possibly irresponsible decision to go ahead and do it.

Overall, I’m very pleased.  There is a runDLL error on startup involving a single DLL, but otherwise, I have yet to notice any significant problems with it.  I can’t say that I find anything particularly immediately exciting about it, mind you, as I really don’t care about the start menu, but I do like the whole windowed Store app thing.

posted @ Thursday, October 02, 2014 9:37 PM | Feedback (0)
Repost: Beware of Selector Nesting in Sass

This happens to be rather timely for me, as I am in the middle of converting a 1000 line CSS file to SCSS.

I like selector nesting for a number of reasons, but there is a lot of good advice in here of how to be careful about it.


posted @ Thursday, October 02, 2014 9:34 PM | Feedback (0)