Hi
I am using Released Silverlight 3 and Q2 Telerik Controls. Just looking at the out of browser feature in Silverlight 3 I find that my application just shows a frame with blank (white) content. Going back to a simple Silverlight application (just a button) it works out of browser no problem. However just adding a RadTreeView to the xaml of my test app results in the blank content. Any ideas?
Thanks
Mike
I am using Released Silverlight 3 and Q2 Telerik Controls. Just looking at the out of browser feature in Silverlight 3 I find that my application just shows a frame with blank (white) content. Going back to a simple Silverlight application (just a button) it works out of browser no problem. However just adding a RadTreeView to the xaml of my test app results in the blank content. Any ideas?
Thanks
Mike
16 Answers, 1 is accepted
0
Hello Mike,
Yes - we are aware of the problem and we are working towards resolving it. The fix should be available within a week.
Sincerely yours,
Valentin.Stoychev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Yes - we are aware of the problem and we are working towards resolving it. The fix should be available within a week.
Sincerely yours,
Valentin.Stoychev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Wolfgang Kamir
Top achievements
Rank 1
Rank 1
answered on 05 Aug 2009, 11:31 AM
Hi Valentin,
please be so kind and notify us in this thread when the fix is available.... I have the same issue, its kind of a pressing matter.... If you can fix it within this week it would really really really help me out.
Kind regards,
Wolfgang
please be so kind and notify us in this thread when the fix is available.... I have the same issue, its kind of a pressing matter.... If you can fix it within this week it would really really really help me out.
Kind regards,
Wolfgang
0
Lawrence
Top achievements
Rank 1
Rank 1
answered on 14 Aug 2009, 03:01 PM
Have you guys developed a fix or have any potential workaround for the out-of-browser issue regarding trying to register handlers with the DOM?
0
Hi Lawrence,
HtmlBridge is not supported from the framework in OOB mode, so we can't do much about it.
Sincerely yours,
Valentin.Stoychev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
HtmlBridge is not supported from the framework in OOB mode, so we can't do much about it.
Sincerely yours,
Valentin.Stoychev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Lawrence
Top achievements
Rank 1
Rank 1
answered on 14 Aug 2009, 03:49 PM
From:
Date: 8/14/2009 10:04:04 AM
Date: 8/14/2009 10:04:04 AM
Hi Lawrence,
HtmlBridge is not supported from the framework in OOB mode, so we can't do much about it.
Sincerely yours,
Valentin.Stoychev
the Telerik team
So, for clarification, does this mean I should not be using Telerik controls if I need to run out-of-browser?
HtmlBridge is not supported from the framework in OOB mode, so we can't do much about it.
Sincerely yours,
Valentin.Stoychev
the Telerik team
So, for clarification, does this mean I should not be using Telerik controls if I need to run out-of-browser?
0
Hi Lawrence,
It seems like some missunderstanding occured. Here is the correct info:
1. With Sp1 release Telerik Silverlight controls are working in OOB mode.
2. What I meant with the previous answer is that The Silverlight3 framework do not allow you to use the HTMLBridge when your application is in OOB mode.
I hope it is all clear now :). Let us know if you hit any issues while using our controls in OOB mode.
Sincerely yours,
Valentin.Stoychev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
It seems like some missunderstanding occured. Here is the correct info:
1. With Sp1 release Telerik Silverlight controls are working in OOB mode.
2. What I meant with the previous answer is that The Silverlight3 framework do not allow you to use the HTMLBridge when your application is in OOB mode.
I hope it is all clear now :). Let us know if you hit any issues while using our controls in OOB mode.
Sincerely yours,
Valentin.Stoychev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Lawrence
Top achievements
Rank 1
Rank 1
answered on 14 Aug 2009, 04:03 PM
I can restate my original question as it was probably confusing.
My company has downloaded and installed your most recent version of SLcontrols to evaluate with one of our applications. As usual the controls perform great when SL is inside the browser. However, when running the application OOB, an exception is thrown regarding:
[System.InvalidOperationException] = {System.InvalidOperationException: The DOM/scripting bridge is disabled.
at System.Windows.Browser.HtmlPage.VerifyThreadAndEnabled()
at System.Windows.Browser.HtmlPage.get_Window()
at Telerik.Windows.Input.Mouse..cctor()}
at System.Windows.Browser.HtmlPage.VerifyThreadAndEnabled()
at System.Windows.Browser.HtmlPage.get_Window()
at Telerik.Windows.Input.Mouse..cctor()
What is the workaround or fix for this exception?
My company has downloaded and installed your most recent version of SLcontrols to evaluate with one of our applications. As usual the controls perform great when SL is inside the browser. However, when running the application OOB, an exception is thrown regarding:
[System.InvalidOperationException] = {System.InvalidOperationException: The DOM/scripting bridge is disabled.
at System.Windows.Browser.HtmlPage.VerifyThreadAndEnabled()
at System.Windows.Browser.HtmlPage.get_Window()
at Telerik.Windows.Input.Mouse..cctor()}
at System.Windows.Browser.HtmlPage.VerifyThreadAndEnabled()
at System.Windows.Browser.HtmlPage.get_Window()
at Telerik.Windows.Input.Mouse..cctor()
What is the workaround or fix for this exception?
0
Wolfgang Kamir
Top achievements
Rank 1
Rank 1
answered on 14 Aug 2009, 04:03 PM
Hi Valentin,
almost clear to me ;-)
Does this post mean, that I now can download and use the version "2009.2.812" (latest in my download-section) for silverlight 3? And with this the OOB-mode will also work? Or is there a special Silverlight3-Edition (last time I had to download the internal build...)?
Kind regards,
Wolfgang
almost clear to me ;-)
Does this post mean, that I now can download and use the version "2009.2.812" (latest in my download-section) for silverlight 3? And with this the OOB-mode will also work? Or is there a special Silverlight3-Edition (last time I had to download the internal build...)?
Kind regards,
Wolfgang
0
Hi all,
Yes - version "2009.2.812" of Radcontrols for Silverlight3 has no known problems with OOB mode.
Lawrence - please download this version and let us know if you still have any issues with it.
Sincerely yours,
Valentin.Stoychev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Yes - version "2009.2.812" of Radcontrols for Silverlight3 has no known problems with OOB mode.
Lawrence - please download this version and let us know if you still have any issues with it.
Sincerely yours,
Valentin.Stoychev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Wolfgang Kamir
Top achievements
Rank 1
Rank 1
answered on 14 Aug 2009, 04:24 PM
Hi again,
unfortunately there seems to be a problem....
Just downloaded and switched the assemblies... from 2009.2.724.1020 to the newest 2009.2.812.1030.
When I try to startup my app, it failes with a AG_E_PARSER_BAD_PROPERTY_VALUE - with the old assemblies it works.
Any clue? Or any clue how i could find out quickly what exactly the problem is?
Kind regards,
Wolfgang
unfortunately there seems to be a problem....
Just downloaded and switched the assemblies... from 2009.2.724.1020 to the newest 2009.2.812.1030.
When I try to startup my app, it failes with a AG_E_PARSER_BAD_PROPERTY_VALUE - with the old assemblies it works.
Any clue? Or any clue how i could find out quickly what exactly the problem is?
Kind regards,
Wolfgang
0
Ben Hayat
Top achievements
Rank 2
Rank 2
answered on 14 Aug 2009, 04:55 PM
Wolfgang, go to your refrences, delete Telerik references out and then add them back in from the new DLLs. See if this resolves it.
0
Wolfgang Kamir
Top achievements
Rank 1
Rank 1
answered on 14 Aug 2009, 05:19 PM
Hi Ben,
thanks for the hint... but that's what I actually ment by "switched the assemblies" ;-)
I removed the references and then referenced the new versinos of the respective DLLs...
Any other ideas?
Kind regards,
Wolfgang
thanks for the hint... but that's what I actually ment by "switched the assemblies" ;-)
I removed the references and then referenced the new versinos of the respective DLLs...
Any other ideas?
Kind regards,
Wolfgang
0
Ben Hayat
Top achievements
Rank 2
Rank 2
answered on 14 Aug 2009, 05:35 PM
I see! Is this running in browser or OOB? And does it happen before you main page shows?
Also, if you look at your xaml pages, do you see any redline under any of the properties (after a build)?
0
Wolfgang Kamir
Top achievements
Rank 1
Rank 1
answered on 14 Aug 2009, 06:55 PM
It's running in the browser... and the error is thrown in the "InitializeComponent()" function of the main App class...
The XAML seems fine.... That was my first thought... that some properties might have changed and therefore the XAML would not be compatible with the new DLLs.... but no warnings or errors....
The XAML seems fine.... That was my first thought... that some properties might have changed and therefore the XAML would not be compatible with the new DLLs.... but no warnings or errors....
0
Lawrence
Top achievements
Rank 1
Rank 1
answered on 14 Aug 2009, 06:59 PM
I was able to get our project running OOB merely by changing the dlls.
Wolfgang--if error is thrown in InitializeComponent it has to be a xaml thing. Maybe a style or template in App.xaml.
Wolfgang--if error is thrown in InitializeComponent it has to be a xaml thing. Maybe a style or template in App.xaml.
0
Wolfgang Kamir
Top achievements
Rank 1
Rank 1
answered on 14 Aug 2009, 07:04 PM
Hi Lawrence,
yes you are right! .. just found out that it has to do somethig with my (custom) ControlTemplate for the TreeView. When I comment out the respective merged resource directory, the app starts up and would not complain.... well, at least until I open up the page with the TreeView.
Ok, I have to rework the template a little.... thanks everyone!
Kind regards,
Wolfgang
yes you are right! .. just found out that it has to do somethig with my (custom) ControlTemplate for the TreeView. When I comment out the respective merged resource directory, the app starts up and would not complain.... well, at least until I open up the page with the TreeView.
Ok, I have to rework the template a little.... thanks everyone!
Kind regards,
Wolfgang