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.
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.
Well, in a scant few hours I'll be off to Austin, Texas, for KaizenConf. It will be a fun packed couple of day dealing with some very interesting topics. In all honestly, I don't exactly know which of the topics I want to attend - the pretty much all are of interest to me. Makes me wish I could clone myself. My plane lands early afternoon, so if you're kicking around Austin and want to entertain an easily amused Canuck, give me a holler (comments here, or on twitter).
Lately I've been experimenting with TypeMock Isolator, and it's new AAA syntax. For the past two years I've been a diehard Rhino.Mocks kind of guy, but figured that it's time to check out other tools. Anyway, I had a situation where a unit test of mine was failing when I ran it with TestDriven.NET, but would pass when I ran it using the unit test runner in Resharper 4.1.
Usually when I develop, I write individual tests and then run individually with TestDriven.
Lately I've been experimenting with TypeMock Isolator, and it's new AAA syntax. For the past two years I've been a diehard Rhino.Mocks kind of guy, but figured that it's time to check out other tools. Anyway, I had a situation where a unit test of mine was failing when I ran it with TestDriven.NET, but would pass when I ran it using the unit test runner in Resharper 4.1.
Usually when I develop, I write individual tests and then run individually with TestDriven.
Most who know me are aware that, despite being a .NET developer and a Microsoft MVP, I'm a bit of a Linux freak at heart. I actually prefer Linux to Windows. Linux has come a long way in the past 18 years, although I've only been tinkering with it off and on for the past 9 years or so. I will admit that perhaps Linux on the desktop isn't quite there for the average consumer, but for me it.
Today was my last full time day on this contract. Tomorrow I start up full-time with another. Personally, I've gotten in the habit of looking a my past contract and conducting my own personal retrospective on what I learned or how I would do things differently. I figured that because my memory is getting worse in my old age, I'd started putting these things down on my blog.
For a greenfield project, don't use the database someone hands off to you
