>>It would be interesting to know how many of those NET 1.1 visionary (right religion) apps died by now already, along with poor customer's money/time waisted.
>
>Died only if they weren't architected right to begin with. Our application Framework was developed back in the 1.1 days and hasn't changed substantially since. And, we have several successful apps and more being developed ... all on our "old" Framework. Sure, we've added some additional features that take advantage of 2.0 and 3.0 stuff (Workflow comes to mind, which we're still working on), but the bulk of our Framework still lives in the 1.1 realm and works flawlessly.

Hi Bonnie

This was one less then innocent {g} parallel to thesis that FoxPro apps were by default dissasters, FoxPro icon on the desktop
raising suspicions etc. FoxPro projects failed as well, especially in times when OOP was newbie amongst us, people were confused by which guru to follow first and that kind of stuff <g> But then VFP matured, people learned their lessons and development became more predictable and consistent. Platform stopped being moving target.

What I can conclude from your success story, is that your organisation was lucky to have you on the team,
and that is about it.
But how mature, risk free, pleasure to develop with, was NET 1.1 back then ? You know the story; Corporate environment, lowsy project leader (still blinking funny after last technology firework/show), mediocre team of NET youngsters still digesting free pizza from NET boot camp... {vbg}

What was the chance of average NET team to cut up deacent app back then ?