Hi Steve,
I also received this message earlier today. I think Visual Studio got very confused in the end as I was constantly adding/removing and generally messing around with all sorts of controls trying to see the functionality. I have since closed everything down, restarted Visual Studio, created a new project exactly as described above and all works fine. I can no longer replicate this problem.
What was interesting to note was that the error occured on exactly the same line as you have stated, thus seems to be a problem with the component rather than ones code. I didn't test the problem with Firefox and as you have probably noted yourself, the page itself functioned properly without error up until closure.
Very odd, I will test some more in the next day or two to find out exactly what causes this to occur although I have a strange feeling someone on here might just beat me to it and explain what the real problem is.
Regards
I have the exactly same problem. I'am using the beta1 and the latest control toolkit.
I think this is an annoying new bug in the control toolkit.
My data editing pages are "popup" pages, so every time I close a "popup" (with dragpanel), I get this message.
But maybe you are not right about one thing
I get thesame error in firefox also, just try ctrl+shift+j for the error consol in firefox, and test.
Just checking and found:
This is a known bug in the control toolkit.
Issue id: 4701
Check ithere.
I've found that
- The bug is still in ajax beta 2 + controltoolkit for beta2. (the javascript error messages are different, but we get some when navigating out or closing the window)
- However with the new 61121 toolkit release I cannot reproduce the bug, so it was finally solved (the 4701 issue is not closed yet...
Thanks for the update - I've just closed work item 4701 with: "As noted in the previous comment andhttp://forums.asp.net/thread/1440767.aspx, this should be fixed in the 61121 release as part of the fix for work item 5704.".
No comments:
Post a Comment