Well,
Just imagine, you used to write your own name like Miha, you wrote a lot of
documents, articles, etc., then somebody wants to change it to mikha or miha
just because it's upgrade and the standard was changed. You will never
recognize your own name from that moment. Will you accept that? Listen, it's
not SQL where you can select is it a case sensitive or not, it's something
different, don't you think? And what could be the reasons leading the same
..NET 1.1 working on Windows Advanced Server 2000 and Windows XP Pro to the
different results WITH or WITHOUT leading underscore in the CurrentURL? I
had to fix this idiot's bug with my own code. And you could just imaging how
easy was to debug and find that on the production server. And not only that.
There are a lot of "improvements" like these above. And I actually didn't
ask your opinion that "somebody had a reason to do that". If the same API
call returns DIFFERENT results from version to version it's crap. We'll
never be able to write good programs using this kind of environment. That's
the reality. Btw, have you ever seen the complete list of "improvements"
done by M$. I doubt it's published in a full value.
Just D.
----- Original Message -----
From: "Miha Markic" <miha at rthand com>
Newsgroups: microsoft.public.dotnet.framework.adonet
Sent: Thursday, October 11, 2007 12:38
Subject: Re: someobject.GetType() - low case
[quoted text, click to view] >
> "Just D" <no@spam.please> wrote in message
> news:2ctPi.758$W06.284@newsfe17.phx...
>> As well as the price of working with Windows... Every new upgrade is
>> unpredictable and the new version of the same API will not necerrarily be
>> compatible. Geeee...
>>
>> I'm sure the class name should be presented as it was created and called
>> without any stupid "improvements" made by some crazy contractor guys
>> writing the API implementation for different versions.
>
> Look, where you are doing major upgrades you have breaking changes. Now,
> if you don't read what those changes are before you are upgrading it is
> your fault.
> I am sure they have their reasons.
> Furthermore, nobody is forcing you to upgrade if you don't want. If you
> feel comfortable with 1.1. then stick with it - you can run .net versions
> side by side.
>
> --
> Miha Markic [MVP C#, INETA Country Leader for Slovenia]
> RightHand .NET consulting & development
www.rthand.com > Blog:
http://cs.rthand.com/blogs/blog_with_righthand/