RadGauge not found - Changed namespace?

5 posts, 0 answers
  1. Joel
    Joel avatar
    41 posts
    Member since:
    Nov 2010

    Posted 18 Nov 2011 Link to this post

    I updated to 2011.3.116.1040, but Visual Studio says it can't find the RadGauge control in xaml.

    I'm using:
     
    <telerik:RadGauge x:Name="gaugeTemperature" Width="150" Height="300">

    But Visual Studio says type telerik:RadGauge not found.  The project has references to Telerik.Windows.Controls and Telerik.Windows.Controls.Gauge.  Am I missing something else?  Did the gauge namespace move?
  2. Joel
    Joel avatar
    41 posts
    Member since:
    Nov 2010

    Posted 22 Nov 2011 Link to this post

    The new gauges are located in the Telerik.Windows.Controls.DataVisualization dll.

    Here's what telerik said about using the old gauges when I opened a support ticket:

    Hi Joel,

    In the 2011 Q3 release we introduce new gauge control. It is almost new control redesigned from scratch. Some its features are similar to the old control&rsquo;s features but they are implemented in absolutely different way (using different set of properties), some features are completely new.

    Our demo application now references new gauge control and demonstrates its features. We are working on the help topics so they describe features of the new control as well.

    We strongly recommend using of the new gauge control in the new applications. We also would recommend replacing the old control with new one in existing applications if there is a timeframe for this task. To avoid cross-controls problems we&rsquo;ve removed old control from the default Telerik namespace. However it still can be used in your XAML as following:


    <UserControlx:Class="OldGaugeControl.MainPage"
        xmlns:gauge="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls.Gauge"
        xmlns:gauges="clr-namespace:Telerik.Windows.Controls.Gauges;assembly=Telerik.Windows.Controls.Gauge"
        mc:Ignorable="d"
        d:DesignHeight="300"d:DesignWidth="400">
        <Gridx:Name="LayoutRoot"Background="White">
            <gauge:RadGauge>
                <gauges:RadialGauge>
                    <gauges:RadialScaleName="radialScale">
                        <gauges:IndicatorList>
                            <gauges:NeedleValue="75"/>
                        </gauges:IndicatorList>
                    </gauges:RadialScale>
                </gauges:RadialGauge>
            </gauge:RadGauge>
        </Grid>
    </UserControl>

    Luckily, it wasn't too difficult to switch my controls to the new gauges, so I didn't need to muck through the gauge/gauges namespaces.
  3. DevCraft banner
  4. YongKoo Kang
    YongKoo Kang avatar
    101 posts
    Member since:
    Jan 2010

    Posted 22 Nov 2011 Link to this post

    Thank you Joel,

    I also hesitated what's changed with new release note and sample,
    nothing mentioned surprisingly or might be hided in the secret place I can't find out.
    Telerik even didn't upgrade their manual and make me spend more time to fix it.
    Good product but bad document.

    Kang




  5. Andrey
    Admin
    Andrey avatar
    1681 posts

    Posted 23 Nov 2011 Link to this post

    Hello Yong-Gu,

    We are currently updating the documentation of the new RadGauge control. I believe you understand that this is a time-consumming task but we are doing our best to make all the necessary modifications as soon as possible. Stay tuned.

    Regards,
    Evgenia
    the Telerik team

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

  6. Rob Ainscough
    Rob Ainscough avatar
    172 posts
    Member since:
    Jan 2010

    Posted 09 Dec 2011 Link to this post

    I just had this problem too ... had to completely remove RadGauge references and start over from scratch.

    The "upgrade wizard" didn't identify any problems, but when I came to build my solution all hell broke loose with errors everywhere.  So I removed all RadGauge references in XAML and code behind, clean solution, the build solution.  Think I had to exit VS 2010 at one point and go back in.

    Fortunately the gauge wasn't that critical for my application functionality.  But it would have been nice to see some type of warning or something other than crash and burn after upgrading.

    Was there some urgency that we're not aware of that would cause Telerik to release the update without documentation?

    Rob
Back to Top
DevCraft banner