.net Framework SERIOUS bug in Events and Delegates

Dear All,
    First I would like to thank you all for this beutifull long awaited site and it is really something to be remembered with, so strait to the subject, ok.
I found a serious bug in .net framework 1.x in the Events, Delegates handling and I'm not to reveal it in this e-mail, but i would like someone to point me in the right direction to report it under my name [I'd love a free version of VS.net , or maybe a position in M$ ]

Anyway I'm waiting your reply on bishoy [at] dev2dev [dot] org

Thanks and Good Luck.
Bishoy Ghaly
Software Archtect
Egypt

Is it a security issue?

If you have a problem with a released product, call Microsoft Product Support Services. They'll be able to tell you whether it's actually a bug in the product or whether you're misusing the feature.

it is 100000% a bug and i have sample documented code for it and not it is not a security it is a CLR design bug

CodeGuru wrote:

it is 100000% a bug and i have sample documented code for it and not it is not a security it is a CLR design bug

no, i would like to be the first one to report it to Microsoft .

If Microsoft confirms that it's a bug, your support call will be refunded. They ask for the money up front simply because it can be hard to get the customer to pay afterwards.

Developer products include a number of free support incidents in the purchase price. Again, if a bug is confirmed, you will be credited.

Trying to play an end-around game on Channel 9 is not smart. Microsoft's whole sustained engineering process is oriented around Product Support Services. Go with the flow, don't fight it.

im not fighting anything, but for your reference miscosoft support charges like 300$ a call and my monthly salary is way less than that amount im from egypt not USA or Europe and i dont have a license for VS.net and all i asked for is a legal free way to report this bug and post te sample i prepared for it., is that a crime or playing smart ?

If you are absolutely, 100%, definately, no shadow of a doubt, sure that it is a bug - you can ring PSS. It'll go through the system and you won't be charged.

If there is even the slightest hint of doubt, and you can't afford to pay Microsoft to tell you what you are doing wrong, then you're better off posting details here or to a Microsoft newsgroup in the hope that either a) someone will tell you how to fix it, b) you'll have confirmation that it is indeed a bug and know your safe to ring PSS.

I'm presuming you have already applied all the relevant service packs to the version of the Framework you are using.

CodeGuru wrote:

it is 100000% a bug and i have sample documented code for it and not it is not a security it is a CLR design bug

If you post it here, you will still be first one to submit it.
However, if I were you, I'd google the Internet. Chances of you finding "serious design CLR bug", after thousands of people have designed it and millions used it subsequently, is dangerously close to zero.

I am not aware of any Microsoft sponsored gift for those who find bugs in Microsoft products, so you have nothing to gain (nor lose) by posting here.

I found a way to report the BUG , I invite all of you to try it and give me feedback.

http://alerts.msn.com/Alerts/SelectSettings.aspx?rdr=1&ppsignin=1&cpid=42098&cpa=a4ab86a4b893e4a2defdc890c47dc8fd&signup=3&rtn=http%3a%2f%2flab.msdn.microsoft.com%2fProductFeedback


Thank you all for your support and opinions

The Product Feedback Centre is for reporting issues with unreleased products. You may well get the issue fixed in .NET 2.0, but unless you ask PSS, it won't be fixed in 1.1.

Is this a case of cold fusion?

Minh wrote:

Is this a case of cold fusion?

smokin the crack smokin the crack lalalala