Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Apr 02, 2006 07:44 AM|LINK
In case you want to have impact on thre matter, as I posted earlier in this thread, there's a related report on MSDN product feedback center
I asked a few days ago about the status, they are still investigating this case.
UPDATE 4/6/2006: Microsoft is working on a QFE (quick fix) and they should have an update very soon.
If it is exactly same scenario you face, you can vote for it (also comment on bottom of the page).
And if you have steps which can be used to reproduce the error, even if it would occur in slightly different scenario, make sure you post the steps here, exactly and accurately (this thread is referenced on the report above) so that ASP.NET Team is aware
of them. It always helps them to better "map" the issue (how wide the issue is, what needs to be changed in order to fix it, costs, should it be postponed or not and so on)