Confirm Getting error: Reference is not a valid visual DependencyObject

[danparker276]

When I close or ok my Confirm window I get this error.  If I step through it, it doesn't do it, probably because of timing.
I only noticed this on the latest internal build.

EDIT:
I can confirm, that I went back to the old internal build, and I didn't get this error.  Version 2013.1.220.1050 is ok.  
Versoin 2013.1.403.1050 is broken.  
Of note, I'm opening up this confirm message on a RadWindow.

This is very hard to debug because Visual Studio wasn't able to catch this error in try/catch.

[Alek]

Hello Dan,

We did not manage to reproduce the issue. Please, take a look at the attached video in case we are missing something important.

Kind regards,
Alek
the Telerik team

[danparker276]

Seems like the problem only happens when I call .Focus() (on any control) after my confirm message is closed. Now I've also noticed that it happens only if I have when I'm using the radbusyindicator. 
If I stop the radbusyindicator before calling .Focus(), I get the error.
If I stop it after, I don't get the error. (So this is my solution).
Also, this only happens when I'm running with the debugger in VS.  When I deploy it, I don't get the error.
Also, it only happens when I use that version.  I just upgraded and got the error again.  That was the only thing I changed.


I tried to isolate this and created my own test app but I can't.  I tried to re-create many of the controls in the radwindow, but it didn't give me the error.  I think this is an error in Visual Studio and only happens when I have a lot of controls in the radwindow.  I'm not sure there is much you can do, especially since I can't reproduce it in my test program.  I guess this might have something to do with the busy indicator.  Of note I'm not putting anything inside my busy indicator.  I'm Setting the rowspan of the busy indicator and calling this to enable:
            busyIndicatorTED.IsBusy = false;
            this.IsEnabled = true;

[Alek]

Hello Dan,

We are glad that you've found a solution for the case. 

We'll keep the situation in mind for future references, although at the moment we can not take any actions since we did not manage to reproduce the issue.  

If you have more details for the scenario do not hesitate to contact us again.

Regards, Alek
the Telerik team

[Yonggu Kang]

Hi Dan and telerik team,

I'm on the same boat.
Mostly I'm using floating dock to open edit view,which is based on usercontrol and widely using RadBusyIndicator as well.
The floating dock shows without problem on opening,however,whenever I tried to extend or shrink the view by dragging with mouse
 or click the button on the view to close, error burst out and the worse is it can't be trapped as Dan said, visual studio should be closed.
It also happens when I make docked view floating and click any button or resize, and regardless of 'FOCUS', always shows error
and vs should be re-started in my case.

There were no problem at all in the past version but current version does.
What's changed ? Should I go back to old vsersion ?
My project composed of more than 30 xaps and Whenever I upgraded newer version, I often met unexpected error.<sigh>.
It's too terrible for me to upgrade new version.
Though error happend only in developing stage, it's so hard to add new view.
If there is no way to fix, it wud be better for me to go back old vsersion as far as I'm using RadDock.

TIA.

Kang

[Alek]

Hello Kang,

We are not aware of such behavior.

Following the explanations in your forum post we've created a sample example trying to reproduce the issue, but we did not manage. You may find it as an attached file. You can make modifications in it in order to recreate the crash and send it back to us or you can send us your own sample where the issue can be observed. 

This will be very helpful to us in order to investigate the case.

Regards, Alek
Telerik

[Daniel]

The crash can be reproduced using the example solution by enabling OOB with GPU and trust.

<OutOfBrowserSettings ShortName="RadDocking_SL Application" EnableGPUAcceleration="True" ShowInstallMenuItem="True">
  <OutOfBrowserSettings.Blurb>RadDocking_SL Application on your desktop; at home, at work or on the go.</OutOfBrowserSettings.Blurb>
  <OutOfBrowserSettings.WindowSettings>
    <WindowSettings Title="RadDocking_SL Application" />
  </OutOfBrowserSettings.WindowSettings>
  <OutOfBrowserSettings.SecuritySettings>
    <SecuritySettings ElevatedPermissions="Required" />
  </OutOfBrowserSettings.SecuritySettings>
  <OutOfBrowserSettings.Icons />
</OutOfBrowserSettings>

Using  2013.2.715.1050 DLLs

[danparker276]

Just FYI, mine occurred with OOB and full trust.  I don't have GPU on though.

[Alek]

Hello,

We've managed to reproduce the behavior which is mentioned in the last two forum posts. is seems that we've introduced an issue in the RadDocking concerning Silvelight OOB application after the last official release (version 2013.2.611). 

But we would like to note that this is a different issue from the one that this discussion has been created about. We still do not manage to reproduce it. We tried under versions 2013.2.611, 2013.1 403 and 2013.1.220. Without reproducing the problem at our side, there is not much we can do to help.

Regards, Alek
Telerik