Ugh! .NET 1.1 Maintenance
-
General moan. I joined a new team at work as tech lead and the app stack is written almost entirely in .NET 1.1 (with some good ol' VB6 and hacked .bat's for good measure). It's not the code itself that's bugging me - it's the IDE. I've never liked the 1.1 IDE. Maybe others here will differ but to me it's slow and fugly. Ick. I'll be porting it over .NET 4 from around mid July so there's hope. Just fired the 2003 IDE up, felt a bit ill and decided to run here for solace and procrastination. Haven't used it for the last 6 years and it irks me that I feel like taking the position was a step backwards (even tho' it's actually a really good opportunity for me). Anyone else still using .NET 1.1? Brothers in arms - I feel your pain!
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine Allen -
General moan. I joined a new team at work as tech lead and the app stack is written almost entirely in .NET 1.1 (with some good ol' VB6 and hacked .bat's for good measure). It's not the code itself that's bugging me - it's the IDE. I've never liked the 1.1 IDE. Maybe others here will differ but to me it's slow and fugly. Ick. I'll be porting it over .NET 4 from around mid July so there's hope. Just fired the 2003 IDE up, felt a bit ill and decided to run here for solace and procrastination. Haven't used it for the last 6 years and it irks me that I feel like taking the position was a step backwards (even tho' it's actually a really good opportunity for me). Anyone else still using .NET 1.1? Brothers in arms - I feel your pain!
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine Allen -
General moan. I joined a new team at work as tech lead and the app stack is written almost entirely in .NET 1.1 (with some good ol' VB6 and hacked .bat's for good measure). It's not the code itself that's bugging me - it's the IDE. I've never liked the 1.1 IDE. Maybe others here will differ but to me it's slow and fugly. Ick. I'll be porting it over .NET 4 from around mid July so there's hope. Just fired the 2003 IDE up, felt a bit ill and decided to run here for solace and procrastination. Haven't used it for the last 6 years and it irks me that I feel like taking the position was a step backwards (even tho' it's actually a really good opportunity for me). Anyone else still using .NET 1.1? Brothers in arms - I feel your pain!
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine AllenStill stuck using VB6 and FoxPro :( .NET 1.1 isn't so bad, lack of generics is annoying though. But can't you just port it straight to .NET 2 without code changes? Might have a few warnings but should work and will let you use a newer ID - or do the client machines only have the 1.1 runtimes installed?
-
Co-incidence? Yeah, I'm in your place! :) Although, I've already ported to 4.0, things inside are still stale as 1.1! Look at it this way, there's lots of scope of work and making things look (and work) better!
- Jk
Jyothikarthk wrote:
Look at it this way, there's lots of scope of work and making things look (and work) better!
This suite of apps is, officially, supposed to be decomissioned but it's still under active development :doh: I think I'm safe for the next 2 years at least.
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine Allen -
Still stuck using VB6 and FoxPro :( .NET 1.1 isn't so bad, lack of generics is annoying though. But can't you just port it straight to .NET 2 without code changes? Might have a few warnings but should work and will let you use a newer ID - or do the client machines only have the 1.1 runtimes installed?
Dave Parker wrote:
port it straight to .NET 2 without code changes?
I'm a-goin' the whole hog and porting to .NET 4. Well... going "half hog" insofar as there will be no code changes (yet), only target the newer runtime and new tooling.
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine Allen -
General moan. I joined a new team at work as tech lead and the app stack is written almost entirely in .NET 1.1 (with some good ol' VB6 and hacked .bat's for good measure). It's not the code itself that's bugging me - it's the IDE. I've never liked the 1.1 IDE. Maybe others here will differ but to me it's slow and fugly. Ick. I'll be porting it over .NET 4 from around mid July so there's hope. Just fired the 2003 IDE up, felt a bit ill and decided to run here for solace and procrastination. Haven't used it for the last 6 years and it irks me that I feel like taking the position was a step backwards (even tho' it's actually a really good opportunity for me). Anyone else still using .NET 1.1? Brothers in arms - I feel your pain!
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine AllenDave Sexton wrote:
Anyone else still using .NET 1.1
Yep. The gig i just started is using 1.1. The 2 existing programmers have never ventured beyond the VS 2003. Not even on their own. They don't know what's waiting for them in the jump we are planning to 2010. I'm pushing for that jump to happen as soon as possible. Oh, and VSS 6 Gah!
-
Dave Parker wrote:
port it straight to .NET 2 without code changes?
I'm a-goin' the whole hog and porting to .NET 4. Well... going "half hog" insofar as there will be no code changes (yet), only target the newer runtime and new tooling.
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine AllenYou should pretty much have no issues going anything from 2.0 up to 4.0. I remember 1.1 being a real pain in the *** though for upgrade. I wonder if the old internal 1.1 sites are still runing in my previous company? No-one wanted to touch the stuff and only I worked on and it was oldish when I already got my hands on it. Left nearly 3 years ago already.
-
You should pretty much have no issues going anything from 2.0 up to 4.0. I remember 1.1 being a real pain in the *** though for upgrade. I wonder if the old internal 1.1 sites are still runing in my previous company? No-one wanted to touch the stuff and only I worked on and it was oldish when I already got my hands on it. Left nearly 3 years ago already.
Mario Luis wrote:
I wonder if the old internal 1.1 sites are still runing in my previous company? No-one wanted to touch the stuff and only I worked on and it was oldish when I already got my hands on it. Left nearly 3 years ago already.
Going on past experience, chances are it's the flagship product these days :)
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine Allen -
Dave Sexton wrote:
Anyone else still using .NET 1.1
Yep. The gig i just started is using 1.1. The 2 existing programmers have never ventured beyond the VS 2003. Not even on their own. They don't know what's waiting for them in the jump we are planning to 2010. I'm pushing for that jump to happen as soon as possible. Oh, and VSS 6 Gah!
thrakazog wrote:
Oh, and VSS 6 Gah!
Yep, we were the same. Thankfully already started moving to SVN but that's gonna be painful as well...
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine Allen