Page 1 of 2
.NET Framework sucks!
Posted: Wed Jan 25, 2006 10:04 pm
by techjunkie
Maybe the idea is good, but .NET Framework seems more and more like a Microsoft hack and when you run it in a production environment its a mess.
If you install several .NET Framework applications on a webserver it all seems ok, but then... when the update begins.
Application #1 demands .NET Framework version 1.0 and doesn't work if version 1.1 is installed
Application #2 demands .NET Framework version 1.1 and doesn't work if version 2.0 is installed
Application #3 demands .NET Framework version 2.0
and so on...
and if you look at Microshit... ehhh - sorry... Microsoft KB824643
http://support.microsoft.com/kb/824643/
you begin to think Bill is playing a prank!!
(Seems like you must have one virtual server / .NET Framework version in the future) :roll:
Posted: Wed Jan 25, 2006 10:08 pm
by Trond
Why is there no option for "sucks like only the .NET framework can and those responsible should be jailed and tortured until every reference to it is destroyed"?
Posted: Wed Jan 25, 2006 10:09 pm
by techjunkie
Trond wrote:Why is there no option for "sucks like only the .NET framework can and those responsible should be jailed and tortured until every reference to it is destroyed"?
Ohhh... Sorry! My misstake!
Posted: Wed Jan 25, 2006 10:14 pm
by Berikco
Posted: Wed Jan 25, 2006 10:21 pm
by utopiomania
I miss a (0) Sucks bad if you just aren't up to it.
Posted: Wed Jan 25, 2006 10:23 pm
by Shannara
Huh? Here at work, we have 1.0, 1.1, and 2.0 running side by side on our web servers. And they are working ok ... what's the issue here?
Posted: Wed Jan 25, 2006 10:25 pm
by thefool
Shannara wrote:Huh? Here at work, we have 1.0, 1.1, and 2.0 running side by side on our web servers. And they are working ok ... what's the issue here?
no problem here either.
But its stupid because 2.0 should allow running 1.0 and 1.1 too!
Posted: Wed Jan 25, 2006 10:25 pm
by techjunkie
Shannara wrote:Huh? Here at work, we have 1.0, 1.1, and 2.0 running side by side on our web servers. And they are working ok ... what's the issue here?
Bad application programmers! A five years old monkey can do a .NET application without understanding what they are doing.
[Edit]
But even well known applications (for example some of Dantz's applications) doesn't work with 2.0 installed, while others demands 2.0 - so you have a conflict there. All programming companies doesn't update their applications at the same time.
Posted: Wed Jan 25, 2006 10:42 pm
by techjunkie
techjunkie wrote:Bad application programmers! A five years old monkey can do a .NET application without understanding what they are doing.
I'll quote myself... How cool isn't that?!?! Hehe...
a correction...
"A five years old
DEAD monkey can do a .NET application without understanding what they are doing.
"
Hmmm... That seems logical! Now I understand why .NET applications are so bad!!
Posted: Wed Jan 25, 2006 10:47 pm
by netmaestro
@techjunkie: How did the monkey die? What did you do, spank him to death?
Posted: Wed Jan 25, 2006 10:48 pm
by utopiomania
Bad application programmers! I five years old monkey can do a .NET application without understanding what they are doing.
What's the problem with that ?? If you think it's that simple, think about what people who
do know what they are up to can do instead.
Posted: Wed Jan 25, 2006 10:54 pm
by techjunkie
netmaestro wrote:@techjunkie: How did the monkey die? What did you do, spank him to death?
I wish!!
Posted: Wed Jan 25, 2006 10:55 pm
by techjunkie
utopiomania wrote:Bad application programmers! I five years old monkey can do a .NET application without understanding what they are doing.
What's the problem with that ?? If you think it's that simple, think about what people who
do know what they are up to can do instead.
Yeah that's true - I'll better hold on to the dead monkey!
Posted: Wed Jan 25, 2006 11:05 pm
by Fred
are you sure than v2.0 doesn't run v1.0 or v1.1 apps ?
Posted: Wed Jan 25, 2006 11:25 pm
by Straker
We needed a poll for this question?