RadGauge missing after update to interim trial build

5 posts, 1 answers
  1. Gary Gormley
    Gary Gormley avatar
    1 posts
    Member since:
    Feb 2006

    Posted 16 Oct 2009 Link to this post

    I was pleased to see that interim builds could be downloaded.
    I was specifically after the build that fixed the memory leak in RadChart.
    I grabbed the following build
    RadControls_for_Silverlight_2009_2_1009_Trial.zip
    unzipped, and copied over the top of the existing assemblies.

    However, i can't seem to build my Telerik based project anymore.
    I did remove all telreik references and add them back in one by one.
    i get the following error:
    The tag 'RadGauge' does not exist in XML namespace 'clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls.Gauge'

    any ideas ?

    more info.
    C:\Program Files\Telerik\RadControls for Silverlight Q2 2009\Binaries\Silverlight\Telerik.Windows.Controls.Gauge.dll
    has a version of 2009.2.1008.1030
    while the other dll's have a version of 2009.2.1009.1030
    which indicates the build date i believe. Is this a problem ?

    and intellisense in the xaml page suggests that RadGauge is indeed present in the xmlns i nominated.
    but the compiler can't seem to find it.

    So, i'm still stuck !
  2. Answer
    Andrey
    Admin
    Andrey avatar
    1681 posts

    Posted 19 Oct 2009 Link to this post

    Hello Gary,

    We've reproduced the problem with the RadGauge control and the internal build you downloaded.
    The RadControls_for_Silverlight_2009_2_1009_Trial.zip has incorrect version number for Telerik.Windows.Controls.Gauge.dll.
    We will resolve this problem with next internal build. Please, accept our apologies for the inconvenience caused.

    Meanwhile, you can take a look at our second beta we released last week.

    Best regards,
    Andrey Murzov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  3. DevCraft banner
  4. Zero Gravity Chimp
    Zero Gravity Chimp avatar
    40 posts
    Member since:
    Dec 2009

    Posted 16 Dec 2009 Link to this post

    Hello,

    I ran into this problem when I accidentally used a Q3 version in a project that has been upgraded to an internal build version. I understand that it's not up to you what version conflicts the user brings into the application! My question is, is there a better way to display the error?

    RadGauge would work in q3 and my interrim-build version, so the error made it very hard for me to understand that the problem is a minor thing such as version conflict.

    Needless to say, the sequence of implementation that I used would have worked in a new test project where there was no Telerik DLL version conflict.

    Is it possible to show a slightly cleaner error? this might be useful to other users too, just an idea!
  5. Andrey
    Admin
    Andrey avatar
    1681 posts

    Posted 21 Dec 2009 Link to this post

    Hi Gary,

    Thank you for the feedback.
    Unfortunately, it seems there is no better way to display the error with the version conflict. The assemblies processing performs inside the Silverlight and the error is not accessible from  code.

    Best wishes,
    Andrey Murzov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  6. Zero Gravity Chimp
    Zero Gravity Chimp avatar
    40 posts
    Member since:
    Dec 2009

    Posted 21 Dec 2009 Link to this post

    Okay,

    that is not hard to understand. Thank you for the feedback.

    -Paul
Back to Top
DevCraft banner