Application Unable to Start after Update

6 posts, 0 answers
  1. Vinod
    Vinod avatar
    23 posts
    Member since:
    Nov 2011

    Posted 25 Oct 2013 Link to this post

    I updated to 2013.3.1016.45.

    After update the application is unable to start with the following error

    InvalidCastException:

       at Telerik.Windows.Controls.RadToggleButton.OnCornerRadiusChanged(DependencyObject d, DependencyPropertyChangedEventArgs e) in c:\TB\105\WPF_Scrum\Release_WPF\Sources\Development\Core\Controls\Buttons\RadToggleButton.cs:line 408
       at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
       at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
       at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
       at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
       at System.Windows.StyleHelper.ApplyStyleOrTemplateValue(FrameworkObject fo, DependencyProperty dp)
       at System.Windows.StyleHelper.InvalidateContainerDependents(DependencyObject container, FrugalStructList`1& exclusionContainerDependents, FrugalStructList`1& oldContainerDependents, FrugalStructList`1& newContainerDependents)
       at System.Windows.StyleHelper.DoStyleInvalidations(FrameworkElement fe, FrameworkContentElement fce, Style oldStyle, Style newStyle)
       at System.Windows.StyleHelper.UpdateStyleCache(FrameworkElement fe, FrameworkContentElement fce, Style oldStyle, Style newStyle, Style& styleCache)
       at System.Windows.FrameworkElement.OnStyleChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
       at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
       at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
       at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
       at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
       at System.Windows.StyleHelper.ApplyTemplatedParentValue(DependencyObject container, FrameworkObject child, Int32 childIndex, FrugalStructList`1& childRecordFromChildIndex, DependencyProperty dp, FrameworkElementFactory templateRoot)
       at System.Windows.StyleHelper.InvalidatePropertiesOnTemplateNode(DependencyObject container, FrameworkObject child, Int32 childIndex, FrugalStructList`1& childRecordFromChildIndex, Boolean isDetach, FrameworkElementFactory templateRoot)
       at System.Windows.FrameworkTemplate.InvalidatePropertiesOnTemplate(DependencyObject container, Object currentObject)
       at System.Windows.FrameworkTemplate.<>c__DisplayClass6.<LoadOptimizedTemplateContent>b__3(Object sender, XamlObjectEventArgs args)
       at System.Xaml.XamlObjectWriter.Logic_CreateAndAssignToParentStart(ObjectWriterContext ctx)
       at System.Xaml.XamlObjectWriter.WriteStartMember(XamlMember property)
       at System.Windows.FrameworkTemplate.LoadTemplateXaml(XamlReader templateReader, XamlObjectWriter currentWriter)
  2. Kiril Vandov
    Admin
    Kiril Vandov avatar
    324 posts

    Posted 30 Oct 2013 Link to this post

    Hello Vinod,

    We were not able to reproduce this issue on our side. That is why I would like to ask you for more information about your scenario:
    - which is the theme that is used in your application(OfficeBlack,Windows8 e.t.).
    - do you have applied custom styles to your RadToggleButtons. If so could you provide us with the custom style.
    - from which version of our binaries you are migrating to 2013.3.1016.45.

    We're looking forward to hearing from you.

    Kind regards,
    Kiril Vandov
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  3. UI for WPF is Visual Studio 2017 Ready
  4. Vinod
    Vinod avatar
    23 posts
    Member since:
    Nov 2011

    Posted 05 Dec 2013 Link to this post

    Hello,

    As Q3 SP1 was released this week, I tried the upgrade once more and the problem still persists.

    1. The theme used is the Windows8Touch theme.
    2. No custom styles are applied to RadToggleButton. In fact, my code doesn't even use RadToggleButton anywhere. Or even the WPF ToggleButton.
    3. I migrated from 2013.2.724.45 -> 2013.3.1204.45

    With some luck and guess work I traced the problem to RadDiagramNavigationPane. I guessed that was the only control using a RadToggleButton in my app. Removing RadDiagramNavigationPane fixes the crash for me.
  5. Kiril Vandov
    Admin
    Kiril Vandov avatar
    324 posts

    Posted 06 Dec 2013 Link to this post

    Hello Vinod,

    Thank you for your cooperation. Your help helped us to finally reproduce this issue on our side. We will include the fix for this issue as soon as possible in one of our next internal build. I have also update your Telerik points as a thanks for your cooperation.

    Please excuse us for the inconvenience caused.

    Kind regards,
    Kiril Vandov
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  6. Jaco De Villiers
    Jaco De Villiers avatar
    15 posts
    Member since:
    Nov 2009

    Posted 06 Jan 2014 Link to this post

    I have the same issue.  Any fix available yet?
  7. Tina Stancheva
    Admin
    Tina Stancheva avatar
    3298 posts

    Posted 08 Jan 2014 Link to this post

    Hello Jaco,

    We fixed the issue in the middle of December which means that you can test it using the latest internal build, which you can download from your account. Please let us know if you still experience issues with the internal build so that we can address them.

    Regards,
    Tina Stancheva
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
Back to Top
UI for WPF is Visual Studio 2017 Ready