I setup a new box with SL3B1 and the new DatePicker March Release and this problem is not fixed -- It looks like it's ignored. I'm hoping that it was the right decision to be made for SL3. Let me explain.
When you're debugging it doesn't crash the browser or thrown an exception anymore but the application still dies and you get the new "White Screen of Death". Because it doesn't give any indication of why the application is stopping we can't be positive it's
the same thing. Strangely enough I found it *easier* to make the error occur in the new Silverlight 3 environment, often on the very first attempt (Click dropdown + Click Calendar). The new environment is slower than my regular development environment so
I'm able to click the dropdown and then very quickly in the region where the calendar *should* be before the calendar is visible.
When you're not debugging no error occurs whatsoever. No browser crash, no application crash, no error message. It's as if the exception is being caught and ignored.
So, given that this is still Beta 1 and the "FIXED" statement in the Silverlight Toolkit's web page it looks like it will be fixed (at least for end users) for SL3. If it continues to crash the application while I'm debugging I suppose I'll just have to
suck it up.
ld1453
Member
291 Points
117 Posts
Re: Re: Re: DatePicker produce weird crash
Apr 06, 2009 05:01 PM | LINK
I setup a new box with SL3B1 and the new DatePicker March Release and this problem is not fixed -- It looks like it's ignored. I'm hoping that it was the right decision to be made for SL3. Let me explain.
When you're debugging it doesn't crash the browser or thrown an exception anymore but the application still dies and you get the new "White Screen of Death". Because it doesn't give any indication of why the application is stopping we can't be positive it's the same thing. Strangely enough I found it *easier* to make the error occur in the new Silverlight 3 environment, often on the very first attempt (Click dropdown + Click Calendar). The new environment is slower than my regular development environment so I'm able to click the dropdown and then very quickly in the region where the calendar *should* be before the calendar is visible.
When you're not debugging no error occurs whatsoever. No browser crash, no application crash, no error message. It's as if the exception is being caught and ignored.
So, given that this is still Beta 1 and the "FIXED" statement in the Silverlight Toolkit's web page it looks like it will be fixed (at least for end users) for SL3. If it continues to crash the application while I'm debugging I suppose I'll just have to suck it up.