We're having a look at the RC for SL 5.0.
The previous 5.0 beta worked fine with the Telerik controls however we're getting some very basic issues with the RC.
For instance creating a new SL 5.0 project from scratch and adding a RadTabControl with a RadTabItem with content causes an exception.
This will throw the following error:
Message=Set property 'System.Windows.Controls.ContentControl.Content' threw an exception. [Line: 15 Position: 33]
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
Message=Value cannot be null.
Parameter name: element
at MS.Internal.XcpImports.ItemsControl_GetItemsOwner(DependencyObject element)
at System.Windows.Controls.ItemsControl.ItemsControlFromItemContainer(DependencyObject container)
at Telerik.Windows.Controls.ItemsControl.ItemsControlFromItemContainer(DependencyObject container)
at Telerik.Windows.Controls.RadTabItem.OnContentChanged(Object oldContent, Object newContent)
at System.Windows.Controls.ContentControl.OnContentChanged(IntPtr nativeTarget, CValue& oldContentValue, CValue& newContentValue)
This also occurs if we specifically set the content:
Additionally attempting to run the demo site with version 5.0.60818.0 of the SL plugin also throws this error with some controls.
The ones we've tested so far that fall over are:
RibbonView (If there arebackstage items)
The RadBreadCrumb works.
33 Answers, 1 is accepted
This is the response from the support ticket I raised. Just a matter of time then...
We are currently testing our controls against the Silverlight 5 RC. There are some issues that we found and some of them are major like the one in the thread you send. We will definitely work on resolving them, but in the moment I can't give you a specific time frame when there will be stable version compatible with Silverlight RC. But I can assure you that we are tightly following Microsoft releases and will try to provide compatible controls as soon as possible.
Don't hesitate to contact us if you have further questions.
the Telerik team
Our RadOutlookBar seems to be broken since upgrading from beta to SL 5 RC.
The problems with our controls with SL 5 RC are reported to Microsoft and they will try to address them for the official Release of Silverlight 5. Please let us know if you need more info.Greetings,
the Telerik team
'You will not be able to test any application using Telerik Silverlight controls prior to the actual release by Microsoft'.
That is completely unacceptable and has dented my faith in Telerik's ability to be at the bleeding edge for Silverlight.
I can confirm we have some issues with most of our controls working properly with the official SL5 RC drop. However, I can assure you that we are actively working on fixing all the issues and we will not stop until this goal is achieved.
the Telerik team
Are there any dates at all on when you expect this to occur? Would be nice to be able to give an answer to management!
At this time, we cannot commit to an exact date when we will launch native controls built against SL5 RTM. We will be targeting a short timeframe after the offiicial announcement of SL5 RTM to release controls built on top of that RTM version. I want to again stress on the fact that all our Silverlight 4 controls will be fully compatible with the forthcoming SL5 official release. We are closely working with Microsoft to ensure that.
All the best,
the Telerik team
I am in the same situation as Glen (and assumingly many others).
Good to know, that you are "targeting a short timeframe after the offiicial announcement of SL5 RTM to release controls built on top of that RTM version".
But at the moment the Telerik Silverlight controls have serious issues with the current RC version.
That means, we are (more or less) blocked in our development cycle until
- either Microsoft releases the RTM
- or Telerik provides a fix for the current RC version.
Not a big deal, if it is just a question of days.
But currently we have no information about any dates and can't continue our development!!!
RTM could still be months away... our development is also seriously interupted by this. A week has passed away en still no news about Supporting the RC or even a hint on when "or if" the RC will be supported!!!
Telerik may boast that "our investments are safe"... but we are becoming seriously discouraged by the lack of transparency regarding Silverlight5 RC.
May I ask Telerik to give us a definate answer about when or if the RC will be supprted?
Same situation over here. All progress blocked due to the RC incompatibility.
Please provide an update for SL5 RC version.
Same situation here, a timeframe would be awesome, even if it's a month away just let us know so that we can work around it accordingly. Give us some transparency here.
I dont think it is quite fair that Telerik is getting landed with so much blame as it looks like SL5 RC is an enormous steaming pile of code that steps across boundarys that no one expected. (if installing SL5RC can affect my SL4 apps someone in MS land is doing it wrong)
What i would like is a hotfix resolution result where i can hack my registry or something to make this problem go away...
look forward to resolution, thanks for your time telerik team.
For me it turned out that Telerik controls produce errors both with SL 5 RC and without SL 5 at all. So I uninstalled SL 5 RC and installed SL 5 beta. Thereafter my SL 4 projects with Telerik controls works without weird exceptions.
Yes, I also find so so wrong, but at least it's helped.
I completely understand the situation you are in. We are absolutely serious when claiming that we will address all the currently existing issues. The fact is that we are working really closely with MS on this. As a close partner we have an access to the latest internal drops and we can confirm that all the issues have been successfully resolved when running tests against these latest internal builds.
Our timeframe remains to launch a SL5 offering together with or shortly after Silverlight 5 RTM.
the Telerik team
You have now put all your customers at a competitive disadvantage to other SL shops who don't rely on Telerik controls.
We can't test or even use any of the features of SL5 RC until it is released has now made me seriously question whether I will recommend Telerik as a provider ever again. When I sold the Management on Telerik here it was based on your fast turn around on issues with bug fixes \ support.
Now I have to go to them and state that we can't test our application against SL 5 RC because our 3rd party control provider doesn't work.
This gives our competitors months of advantage over us which might as well be years in our space.
I have to now go and look at your competitors offerings and put a plan together to convert.
Thank you very much.
Hopwever this is one of the risks we understood when we started developing against Preview/Beta/RC code bases. You have to take the good with the bad. If your manager is giving you a hard time because the RC doesn't work the same as the beta, I'd point out that the business decision to start to produce code on a developing platform has caused the delay.
Until the actual release ships, no one knows what the code will look like. It's worth remembering that the actual release may cause additional problems to both your code and your 3rd parties.
While it's great that telerik now has access to internal microsoft builds, it's a shame that they didn't before hand so we could run and test against the RC now. At least we can be confident that a telerik release alongside the Silverlight 5 release will be fully compatable.
I've managed to uninstall all the RC stuff and reinstall the beta. I'm running fine as I was before, and I'll avoid using the RC and as a company we will be moving directly to the release as and when telerik ships working code.
I'm also expecting that when the release arrives I'll have to rework some of our code to work with it.
In case it helps anyone, I've removed everything in Add/Remove Programs with Silverlight 5 in the name, Ria Services and blend 5 preview. I've then reinstalled Microsoft Expression Blend SDK Preview for Silverlight 5, Microsoft Expression Blend Preview for Silverlight 5, Microsoft Silverlight PRODUCT VERSION: 5.0.60401.0, Microsoft Silverlight 5 Beta SDK and WCF RIA Services v1.0 SP2 Preview (April 2011).
This (in my view) terrible decision by MS to abandon the devloper community has ripple effects on all third party control vendors and they are scrambling to steer their individual businesses in a manner that both keeps them competitive and their work product(s) marketable while doing their best to keep the customer base happy. Telerik is squarely in this unfortunately dynamic.
I can say that I have had great response from Telerik on the majority of concerns specific to their Silverlight controls on balance. Sometimes not at the speed I may have wished or at times too quick to believe there is no problem on their end when there indeed was, but overall they deliver a steady product with (again in my opinion) a support system / team that far exceeds the popular competitors.
My last "2 cents" ... for all those active LOB app-dev folks who are considering the evolution from SL4 to 5, you might otherwise want to consider other options of application maturation because of the Microsoft shift to HTML5. It really is a shame because after the years of evolving SL into a business ready codebase its days are numbered.
The world ends on December 21 2012 anyway so im guna go out developing Silverlight =P
Hey I'm with ya, I'll bring the beer. I'd much rather put $$ to that than a black hole with no reward.
Deal ill bring the steaks for the BBQ and we can watch it all go down in comfort.
As a side note if MS wants us to use HTML5 hadnt they better make a browser that can actually parse HTML and render something useful on screen, IE is always the browser i find myself tweaking HTML for where FireFox, Chrome, Opera all have consistent outputs between them. Anyone else with me on that one?
As I said in my previous post - we ARE working on a native RadControls for Silverlight 5 offering as we always did with each new version of Silverlight.
We did not launch a specific build against the RC version as there were certain problems outside our product. It would have been easier for us to release a build of RadControls for Silverlight 5 RC, but that would result in a customer-frustration and a lot of posts and emails due to the number of issues we discovered earlier.
Given the fact that RadControls for Silverlight is the industry leading toolkit for Silverlight development we did not want to lower the high quality-standards of the product and eventually disappoint you.
We want to ship a stable product, to which you will be able to easily upgrade without having to implement any significant changes. To support the fact that Telerik’s plans about Silverlight have not changed at all you can refer to Vassil Terziev’s blog posts on that matter:
To be able to ship a stable product that will run as expected against Silverlight 5 we will have to deliver it together with or shortly after the Silverlight 5 official (RTM) release.
the Telerik team
ComponentOne - PASS
Infragistics - PASS
Devexpress - PASS
XCeed - PASS
FarPoint - PASS
Divelements - PASS
Intersoft - PASS
Visifire - PASS
Telerik - FAIL
Now I'm curious about what Telerik is doing differently than everyone else?
We can point you to the specific problems that we reported to Microsoft like:
- Regression with LambdaExpression.Compile() method
- FlowDirection of TextBock property behaving differently
- Exception with setting listBox.SelectedItems = null when there are more than one item selected in a ListBox
- Popup rendering issue when flow direction is changed
All the best,
the Telerik team
Back then you seemed like a dynamic company which wasn't mired in release schedules like Infragistcs \ DevExpress were etc.
It meant we could be on the bleeding edge of technology and always ready to use new features as and when MS released them.
We can no longer count on that though which is sad state of affairs.
I notice that your WP7 controlset was updated throughout the beta. I imagine SL took back seat to that focusing on Xaml based controls for Metro.
I understand that there are issues with MS's release candidate. What I don't understand was the lack of transparency from Telerik over what was happening and why your controls won't work with the RC. From a public relations viewpoint it was handled badly and the downside is management where I work have lost faith in Telerik.
I'm currently having to evaluate replacement controls because of this. Had I been able to say from the outset that there were issues and there wouldn't be a fix prior to RTM then I'm sure I wouldn't have been tasked with doing this.
The RC was bad. No one in their right mind would code for regression bugs of a prerelease build, especially an RC that will soon be replaced. How about next time you do your job and advise your management the risks inherent in building against prerelease software. Then you won't get a black eye and we won't have to put up with your bellyaching. Wait for the RTM.
We experience the same problems with the RadOutlookBar and RadTabControl in the RC.
I've however found that these controls only fail if you specify the items in xaml - if you bind the controls to an ItemsSource (dynamically populating the items), they don't fail (at least not for me).
/ Øivind Solberg
Not to diminish your 20 years of experience, but you and the rest of the world may have a different definition of the word "soon". We are November now and we still have no support for RC nor do we have any "hard" date for the release of the RTM (although according to Scott Gu it should be this month).
it's nice of you to mock people (NOT!), but what if you are in a situation where SL5 has features (such as P/Invoke) that you really need.
We are in this position and our development has virtually halted for over a month now because of Telerik refusal to actually handle the RC problem.
I'm pretty sure that Q3 will not support the RC any more then Q2 does, but before we go through the "pain" of upgrading to Q3... Will Q3 support Silverlight5 RTM when it comes out later this month (if it comes out later this month) or will there be an SP of Q3 that will support Silverlight5?
The most most frustrating part is that their demo site and projects don't even run with SL5 and it's been out as a beta for almost a year (and don't get me going about that).
I suggest you to try our demos with the official Silverlight 5 release.Best wishes,
the Telerik team