1,596 problems in .Net 1.1

[Jim Hubbard]

Are you up to speed on the difficulties in using the 1.1 .Net framework?
Not if you are unaware of the 1,596 issues listed at KBAlertz
(http://www.kbalertz.com/technology_3.aspx).

If you are going to use .Net......I highly recommend signing up for the free
KBAlertz newsletter at http://www.kbalertz.com/default.aspx.

Looking at all of the errors and quirks sometimes makes me wonder if this
thing is really ready for prime time.

I still think Microsoft is using us as the world's largest beta test group
for it's own internal initiatives. But, that's just my paranoia shining
through........ isn't it?

Jim Hubbard

[Michael A. Covington]

"Peter van der Goes" <p_**********@t oadstool.u> wrote in message
news:u4******** ******@TK2MSFTN GP09.phx.gbl...

Maybe you're just having trouble adapting to change. Every major
development tool has long lists of open "bugs", including the now *very*
mature VS 6. Microsoft, unlike some competing vendors, chooses to make the
issues public so we *are* aware of potential problems. Try getting a list
of open "bugs" from Oracle.

Well said. Does nobody remember what IBM mainframe operating systems were
like in the 1970s? I think the last version of OS/360 was v. 21 G.

Some manufacturers reveal the issues and release frequent patches. Other
manufacturers keep quiet about them and never fix them. Which is better?

[Radek Cerny]

Funny, we've been using c# extensively since beta 1, and experienced no
problems. Mind you, we have writen our own stuff from primitives, such as
O/R mapper and dont used datasets etc, but we've got a full ERP system
hosted as Web Services with stateful user sessions. So far, so memory
leaks, no crashes, no hacks. Thats in over 4 years totals, and about 2
years live in production. If there are bugs, they are not in the core
functionality. Overall, .NET and the CLR are one of the best things MS has
ever done (although I do miss MI, and see no need for so many languages - c#
will do fine).

Radek

"Jim Hubbard" <re***@groups.p lease> wrote in message
news:0Y******** ************@gi ganews.com...

Are you up to speed on the difficulties in using the 1.1 .Net framework?
Not if you are unaware of the 1,596 issues listed at KBAlertz
(http://www.kbalertz.com/technology_3.aspx).

If you are going to use .Net......I highly recommend signing up for the free KBAlertz newsletter at http://www.kbalertz.com/default.aspx.

Looking at all of the errors and quirks sometimes makes me wonder if this
thing is really ready for prime time.

I still think Microsoft is using us as the world's largest beta test group
for it's own internal initiatives. But, that's just my paranoia shining
through........ isn't it?

Jim Hubbard

[idi_amin]

"Jim Hubbard" wrote:

Are you up to speed on the difficulties in using the 1.1 .Net framework?
Not if you are unaware of the 1,596 issues listed at KBAlertz
(http://www.kbalertz.com/technology_3.aspx).
Yea, im sure all 1500+ issues affect typical day-to-day development. We've
been doing large, complex apps with .NET since beta and I can think of maybe
3 or 4 times a KB item has applied.
If you are going to use .Net......I highly recommend signing up for the free
KBAlertz newsletter at http://www.kbalertz.com/default.aspx.

Looking at all of the errors and quirks sometimes makes me wonder if this
thing is really ready for prime time.
Are you aware that there are even more KB items for your favorite tool VB6?
And VC++ 6.0 has almost twice as many as .NET? So in your professional
opinion VB6 and VC++ 6.0 may not be ready for primetime. Thanks for the tip.
I still think Microsoft is using us as the world's largest beta test group
for it's own internal initiatives. But, that's just my paranoia shining
through........ isn't it?

Jim Hubbard

If this is the typical of the logic and reasoning skills you use in your
daily job, its no wonder that you are having difficulties adjusting to .NET
development, which really isnt difficult at all as long as you stop wasting
brainpower on constantly crying "but it didnt work like this in VB6 or ASP!"

[Peter van der Goes]

"Jim Hubbard" <re***@groups.p lease> wrote in message
news:mr******** ************@gi ganews.com...

Correction: Microsoft's list.

Please note that all 1,500+ are listed in the Microsoft KB.

What would be cool is if Microsoft allowed you to actually download the
fixes WITHOUT having to call and talk to a Microsoft rep. This calling
for every fix is beyond stupid. Not to mention it's absolutely atrocious
customer service.

If the .Net framework (which has an integrated browser) checked for fixes,
told us what the fixes affected and allowed us to select which fixes to
install it'd be more on par with the Windows Update service.

But, doing so would show that the .Net framework is no the end-all-be-all
solution that Microsoft said it was.

If you apply a "fix" to your development boxes, you can be damned sure
that 99.9% of your external users will NOT have this "fix" installed.
That makes the .Net runtimes incompatible. Now we're right back where we
were with DLL Hell - except it's "fixes" missing instead of overwritten
files.

.Net has not and cannot deliver the experience Microsoft has promised
without automatic updates (including fixes) to all .Net-capable desktops.

And (joy of joys), if a customer installs a "fix" for another vendor's
application, it may cause unintended consequences in your .Net
application. And, again - you are screwed. Like it or not, Thinstall app
are immune from this "fix" issue.

Don't throw FUD at me just because you are unfamiliar with the tool that
you are placing your company's future on.

Jim Hubbard

Maybe you're just having trouble adapting to change. Every major development
tool has long lists of open "bugs", including the now *very* mature VS 6.
Microsoft, unlike some competing vendors, chooses to make the issues public
so we *are* aware of potential problems. Try getting a list of open "bugs"
from Oracle.
It appears to be you who wants to apply the "chicken little" spin to the
situation.

[Michael A. Covington]

"Peter van der Goes" <p_**********@t oadstool.u> wrote in message
news:u4******** ******@TK2MSFTN GP09.phx.gbl...

Maybe you're just having trouble adapting to change. Every major
development tool has long lists of open "bugs", including the now *very*
mature VS 6. Microsoft, unlike some competing vendors, chooses to make the
issues public so we *are* aware of potential problems. Try getting a list
of open "bugs" from Oracle.

Well said. Does nobody remember what IBM mainframe operating systems were
like in the 1970s? I think the last version of OS/360 was v. 21 G.

Some manufacturers reveal the issues and release frequent patches. Other
manufacturers keep quiet about them and never fix them. Which is better?