Noel Paton said:
Exactly - and that's where .NET2.0 'fails' - there is NO ensured backwards
compatibility
because a lot of things changed between v1.x and v2.x...which is why you
still have to have both installed! (which is what I've been saying all
along!)
It WAS accepted - because many devs realised that the benefits of the
upgrade far outweighed the hassle involved in re-writing the limited
amount of .NET stuff that was available at the time - and there were,
IIRC, easy methods of semi-automating the port from v1.x to v2. ( I don't
code - so have no details!)
Like they say - never buy the first model car....it'll have more gremlins
than every follow-on model put together!
Well, I'll find out as the company I started at is in transition between
..Net 1.1 to version 2.0, only in concept thinking. Maybe, that's why they
have sent a couple of developers to school. In the meantime, it's hard
enough getting them to realize that the company Web Framework that was put
together by the .NET architect, a trainee .Net architect that quit but
downloaded everything from MS as is and used it unchanged. ;-), to use the
..NET Framework is a piece of trash and they need to be moving to a less
complicated company Framework.
Maybe, I can catch them in transition and take them away from this 7 logical
tier 3 physical tier solution to a to or 3 logical tier and 2 physical tier
solution.
I already have gotten rid of three logical tiers in this proto type
application I am doing that this other *clown* convinced them that they
needed and they wouldn't change while he and his partners in crime were
there. Now, they are gone and the other developers and business analysis are
saying good bye and don't come back to those who wouldn't listen to there is
something wrong with that damn Company Framework.
Unfortunately, the company the others went to that didn't have .Net is going
to get a dosage of what they did at the previous job. Believe me, if you
saw this you wouldn't believe it, as it's horrible. It's so bad that the
..NET IDE debugger and or IIS will terminate itself at the development
machine with all them convinced that it was a workstation problem and it's
not a workstation problem. I think I am now on the road to showing them it's
the piece of trash company Framework that's the problem, even though some
already knew this but couldn't prove it!
Duane