Select to view content in your preferred language

Map Progress Bar

3674
5
06-01-2010 01:37 PM
CraigPerreault
Deactivated User
How can I add the MapProgressBar using 2.0 beta, like in the esriToolKit used in version 1.2
0 Kudos
5 Replies
DominiqueBroux
Esri Frequent Contributor
MapProgressBar is still there with 2.0 beta and is working the same way than in 1.2.

In your xaml file, add something like:
<esri:MapProgressBar x:Name="MyProgressBar" 
    Background="{StaticResource CommonBackgroundBrush}"
 Map="{Binding ElementName=Map}"
 HorizontalAlignment="Center" VerticalAlignment="Bottom"
 Width="150" Height="12" 
 Margin="5"  />
0 Kudos
CraigPerreault
Deactivated User
I get the error description:
The type or namespace name 'MapProgressBar' could not be found (are you missing a using directive or an assembly reference?)


I am using the same code that worked in 1.2 without:
  xmlns:esriToolkit="clr-namespace:ESRI.ArcGIS.Client.Toolkit;assembly=ESRI.ArcGIS.Client.Toolkit"

xmlns:esri="http://schemas.esri.com/arcgis/client/2009"  

        <esri:MapProgressBar x:Name="MyProgressBar"
 Map="{Binding ElementName=myMap}"
                Grid.Row="1"
 HorizontalAlignment="Center" VerticalAlignment="Center"
 Width="150" Height="12"
 Margin="5"  />
0 Kudos
DominiqueBroux
Esri Frequent Contributor
Might be that ESRI.ArcGIS.Client.Toolkit is not referenced in your project.
0 Kudos
CraigPerreault
Deactivated User
Thanks Dominique - my bad, from the What's New in Silverlight 4 page "In XAML, support for XML namespace references to a schema. You can remove multiple assembly/namespace references at the top of your XAML page with one for ESRI.ArcGIS.Client, ESRI.ArcGIS.Client.Behaviors, and ESRI.ArcGIS.Client.Toolkit:" but I did still need to add the toolkit as a reference in the project.
0 Kudos
dotMorten_esri
Esri Notable Contributor
xmlns:esri="http://schemas.esri.com/arcgis/client/2009" should be enough for both core and toolkit assemblies, including the MapProgressBar.

I've seen VS2010 be a little "weird" with these namespaces, and sometimes "forget" what assemblies they map to. Usually just removing the namespace declaration, save, and put it back in fixes it for me when it does this.
0 Kudos