I was just wondering if there's a bug database for .NET framework. The
reason I'd like to see one if that I can be aware of bugs in the framework
and won't have to find the bugs the hard way (where I have to eventually
realize something doesn't work because of a bug, not because I'm doing
something wrong).

Jerry

Re: Bug database by Keith

Keith
Fri Aug 29 16:31:09 CDT 2003

I ran into a specific need for this feature. Recently, I ran into a problem
where an MD5 cryptographer that I wrote started having CSP issues deep
inside the framework (the serviceprovider had a very long lifetime, and I
wasn't init'ing it). Apparently, it was an issue in 1.0, and supposedly
fixed in 1.1. Well, I was seeing in in 1.1, so I was very curious to read
about the nature of the bug so that I could hopefully track down the cause,
but that bug is nowhere to be found on Google or MSDN.
So count me in on the list of those who would love to see the bug list for
.Net.

"Mark" <caveno@cs.com> wrote in message
news:026501c36e70$3cdc5110$a601280a@phx.gbl...
> I've never heard of a bug database, usually when I
> encounter a problem which I believe to be a bug, I search
> MSDN or Google and almost always find the answer.
> There are not a lot of bugs anyway.
> Mark
>
> >-----Original Message-----
> >I was just wondering if there's a bug database for .NET
> framework. The
> >reason I'd like to see one if that I can be aware of bugs
> in the framework
> >and won't have to find the bugs the hard way (where I
> have to eventually
> >realize something doesn't work because of a bug, not
> because I'm doing
> >something wrong).
> >
> >Jerry
> >
> >
> >.
> >



Re: Bug database by Jon

Jon
Sat Aug 30 01:26:43 CDT 2003

Keith Patrick <richard_keith_patrick@nospamhotmail.com> wrote:
> I ran into a specific need for this feature. Recently, I ran into a problem
> where an MD5 cryptographer that I wrote started having CSP issues deep
> inside the framework (the serviceprovider had a very long lifetime, and I
> wasn't init'ing it). Apparently, it was an issue in 1.0, and supposedly
> fixed in 1.1. Well, I was seeing in in 1.1, so I was very curious to read
> about the nature of the bug so that I could hopefully track down the cause,
> but that bug is nowhere to be found on Google or MSDN.
> So count me in on the list of those who would love to see the bug list for
> .Net.

Likewise. Having seen them used to great effect for Eclipse and Java
itself, I'm a big fan.

--
Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too