Migration

Into Each Engineer’s Life, Some Migration Must Fall

Thu, 10 Sep 2009 10:45:00 EDT

Into each engineer’s life, some migration must fall. What started out as a simple necessity when something broke; has evolved over the years into something that gets done about once every three to five years. Hardware doesn’t break as quickly as technology changes, creating a double-edged sword for the folks on the front lines of the technological revolution. Instead of an easy and manageable flow of workloads from one platform to another, we’re instead faced with a mad dash to get everything onto the new hardware platform before 1) the old one gets so outdated nothing works properly anymore or 2) the end-users threaten us with bodily harm because there’s too much downtime for the migration.

Blogs on WCF4, WF4, C#4, Azure, and Goodies Coming Up

Tue, 21 Jul 2009 07:30:00 EDT

A couple of weeks ago my family and I started packing boxes in preparation for fleeing the great state of New Jersey. We packed everything up, threw as much as we could in the minivan and trekked up to Connecticut where I have taken a new position with a new company as a .NET Architect. As any of you who have moved before know, it's an incredibly stressful experience and the logistics involved are absolutely ridiculous. It's a miracle I still know where my car keys, sneakers, and computers are. At one point I was sure I'd left the cat on the roof of the minivan.

Migrating Database Applications from JDBC to ADO.NET

Fri, 13 Feb 2004 00:00:00 EST

Today, more than ever, enterprises are faced with the necessity of migrating applications from one platform to another. Here, we try to take some of the pain out of migrating a database application written in Java to ADO.NET.

Navigating to .NET

Mon, 16 Dec 2002 00:00:00 EST

The .NET Framework is stuffed full of treats for the VB developer. Long-awaited improvements such as strict type checking, structured exception handling, and true object-oriented support extend the power of the language dramatically - but at a price. The only way a Visual Basic 6 program can be brought to the .NET world is through a painful migration process that rarely runs without incident. In this article, we'll consider some of these ugly problems - and the insights you can gain from them.