Home > .net 1.1, .net 2.0, c#, Insanity! > Making the programmer cry…

Making the programmer cry…

March 7, 2007

My task over the past few weeks (and for the next few) is to infuse life into an array of old applications developed in the free time of two prior coworkers.  *insert dramatic music here*

The applications share the following characteristics:

  • Visual Basic.NET (I’m a C#’er, but can read/write VB if need be)
  • .NET 1.0 (not 1.1 even)
  • Heavy, heavy Crystal Reports reliance (along with 10,000 of their closest .dll friends)
  • Hardcoded, often changing variables, like user names, passwords, even IP addresses of servers.
  • Zero, zip, zilch OOP.   Authentication, authorization, database calls, even the page title is recreated and destroyed on every single page.
  • 800+ line methods with a 30+ variable signature (Setting the page title: requestAdd(“Add New”, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false))

So, my first thought—discover, evaluate, and rebuild using .NET 2.0+, C#, and the tools that I’m comfortable with since, I have a feeling, these are now my babies due to proximity.  Nope; need it done tomorrow (figuratively).  Ehh.

*sigh* So, I set about editing…

 

Categories: .net 1.1, .net 2.0, c#, Insanity!
%d bloggers like this: