Well, it’s coming up on fall, which is traditionally the time of year for the Edmonton Code Camp.  It seems that there is still a spot or two left for speakers, so if you’re in Edmonton why not think of something programmy and give a talk.  Doesn’t have to be .NET – anything that is related to software development will do. Anyway, I’ve put my name down for a talk at ECC.

(Note:  this article is pretty dated, and used IntelliJ 8.  I plan a follow-up covering IntelliJ 9) So I have this semi-fancy Google Android Dev Phone 1.  Lately I've been devoting part of my spare time to learning about programming for Android (the OS of the phone).  Google (probably because they didn't ask for my opinion and/or input) decided to use Java as the lingua franca for Android programming.  If you ask me - and I know you will - they should have used C# and Mono (I might be a bit biased here).

Over the Easter long weekend, I experience my own resurrection of sorts.  On Thursday just before Easter I noticed that my NAS, a Thecus N3200 Pro with three Seagate Barracuda 7200.11 drives in a RAID5 array, was beeping and displaying a “RAID degraded” message.  I didn’t worry about it to much, as it was late on Thursday, and I figured I was safe/okay with three drives in a RAID5 array.

Figured I was due to spend some time setting up a Linux VM and learning how to program my Android Dev Phone 1.  Eclipse is what is recommended, so I thought I’d give that a try first.  So, with the help of Suse Studio, I quick built myself a VM with Java 1.6 (Aside:  I love Suse Studio, I can provision a VM in minutes).  I figured it would be pretty straight forward.

One of the nice things about Dependency Injection is that it can really help write a more flexible, modular application.  These days, it seems that there is no shortage of choice in the .NET community when it comes to IoC frameworks: StructureMap Castle Windsor Ninject Autofac Unity Spring.NET And probably others that I’m missing. Ironically, when you first start using an IoC framework, you might find that in trying to make a loosely-coupled, modular, application you end up shackling yourself to the framework you’re using for IoC.

After a bit of tinkering, I managed to provision my ADP1 setup without a SIM card.  A bit of google, and here is what I did: Download the Android SDK.  In my case, I unzipped it to C:\android-sdk-windows-1.1_r1. Connection the phone via the USB cable to my computer.  When the phone asks for a device. You'll get the new hardware dialog, when prompted for the drivers, you'll need to specify the location.

After an uneventful flight from YEG to PSP, I'm settled in with my family.  After spending some time with beer at the pool, I'm sitting down with my Android Dev Phone 1 that I ordered last week (ship to PSP). First impressions:  it seems like a nice phone, and I like the fact it has a keyboard.  I don't have a SIM card to help with provisioning the phone, so all I get is this message saying "No SIM in phone" and "Emergency call".

If you using a unit testing framework such as NUnit, you're no doubt familiar with the [Ignore] attribute. (Note: I haven't used MbUnit in a while, but I'm pretty sure that all this applies there as well.) For those who aren't, when you adorn your [Test] with this attribute, then your test runner should pay no heed to this particular [Test]. Instead of going green or red, your test turns up as yellow in your test runner.

One of the nice things about Dependency Injection is that it can really help write a more flexible, modular application. These days, it seems that there is no shortage of choice in the .NET community when it comes to IoC frameworks: StructureMap Castle Windsor Ninject Autofac Unity Spring.NET And probably others that I'm missing. Ironically, when you first start using an IoC framework, you might find that in trying to make a loosely-coupled, modular, application you end up shackling yourself to the framework you're using for IoC.

Update November 20th:  Well, a quick search of StackOverflow.com, and it turns out that I’m not exactly alone in this matter.  According to this post (and Grant in the comments of this post), in versions of IE < 8, one must use the click event, and not the change event. I ran into an interesting issue today.  I don't really know the answer, but I figured I would blog about it so that I don't completely forget it.