HubTile exception in Blend 2012 with "cannot convert to GridlayoutPosition"

8 posts, 0 answers
  1. Carlos
    Carlos avatar
    14 posts
    Member since:
    Feb 2012

    Posted 10 Apr 2013 Link to this post


    I installed the latest 2013.1. Now every time I add a RadHubTitle,  Blend exceptions (see attached image). 

    C:\Program Files (x86)\Telerik\RadControls for Windows Phone 8 Q1 2013\Binaries\WindowsPhone\Telerik.*

    I works fine in VS 2012 and runs fine in the the emulator and windows phone.  

    Please help.

    thanks 
  2. Victor
    Admin
    Victor avatar
    1351 posts

    Posted 13 Apr 2013 Link to this post

    Hello Carlos,

    I am afraid that I can not reproduce this exception. Also, given the fact that it only occurs in blend is indicative that it might be its fault. Also, the exception states that it cannot convert a type to a type with the same name which may be due to an assembly mismatch. Why Blend loads two different versions of the same assembly is anyone's guess.

    You can try uninstalling any previous versions of the controls and install just the latest release in a clean environment.

    Greetings,
    Victor
    the Telerik team
    Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
  3. DevCraft banner
  4. Carlos
    Carlos avatar
    14 posts
    Member since:
    Feb 2012

    Posted 15 Apr 2013 Link to this post

    Victor,

    I uninstalled/re-installed Telerik and blend. Still similar problem.  This issue started after I upgraded to Q1 2013 controls.  See attached excel and file for some more info.  
  5. Victor
    Admin
    Victor avatar
    1351 posts

    Posted 18 Apr 2013 Link to this post

    Hello Carlos,

    Thanks for the info. We will notify you if we figure out what is causing these exceptions. Microsoft makes this extremely difficult however. There is no way we can debug what our code does inside Expression Blend and the exceptions being thrown provide zero information.

    Regards,
    Victor
    the Telerik team
    Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
  6. Tomas
    Tomas avatar
    3 posts
    Member since:
    Apr 2012

    Posted 03 Aug 2013 Link to this post

    After upgading to the latest version, I see the same problem. Sometimes instead of the exception, I get weird errors in VS xaml editor, e.g.

    <telerikData:RadListPicker Header="Currency" ItemsSource="{Binding Currencies}" SelectedItem="{Binding SelectedCurrency, Mode=TwoWay}" />

    It says "The local property Header can only be aplied to types that are derived from HeaderedItemsControl" and "The local property SelectedItem can only be aplied to types that are derived from RadSelector"

    Wtf?
  7. Ivo
    Admin
    Ivo avatar
    90 posts

    Posted 06 Aug 2013 Link to this post

    Hello Tomas,
    We've found a way to debug the issue, so we are currently working on it.

    Regards,
    Ivailo Dinkov
    Telerik
    Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
  8. Till
    Till avatar
    2 posts
    Member since:
    Oct 2012

    Posted 03 Feb 2014 in reply to Ivo Link to this post

    Could you make any progress on that issue? I guess I have the same problem with RadListPicker using the following code:
    <telerikInput:RadListPicker ItemsSource="{Binding AvailableApps}" SelectedItem="{Binding SelectedApp, Mode=TwoWay}">..

    Works fine, but fails to load in blend with the following exception:
    The local property "SelectedItem" can only be applied to types that are derived from "RadSelector"

    This is super annoying and I can´t use the control as I rely on the designer in my project.
  9. Victor
    Admin
    Victor avatar
    1351 posts

    Posted 06 Feb 2014 Link to this post

    Hi Till,

    I am afraid that we were not able to diagnose this issue. We have very little design-time code and it executes normally. After that it crashes somewhere in the Visual Studio assemblies. It messes up the run-time type information somehow and can't match the different properties to their respective types.

    Regards,
    Victor
    Telerik
    If you want to get updates on new releases, tips and tricks and sneak peek previews directly from the developers working on the UI for Windows Phone, subscribe to the blog feed now.
Back to Top
DevCraft banner