Latest Contributions by JenniferNery

Can you share the code you used for LayerDefintions?  When you say they do not work, what do you mean exactly?  Do you mean the layer shows more than it should?  Can you run Fiddler to see the difference between the calls made with API v2.0 and v2.1 beta? You can either report the bug here in the forums as we check them periodically or you can also go to http://support.esri.com/en/ to submit a bug. ... View more

Can you try another thing?  Start a brand new Silverlight application in Visual Studio 2010 (Silverlight 4, .NET Framework 4.0). Add reference to .NET Assembly System.Windows.Controls.Data.Input. Do not add any namespace in your XAML just yet but go to the Toolbar and drag FeatureDataForm to your Design.  The following should be automatically added to your XAML after the drag is complete.  Go to the properties window and see if you can set FeatureLayer property. xmlns:esri="http://schemas.esri.com/arcgis/client/2009"> ... <esri:FeatureDataForm/> ... View more

Yes, in the code snippet Ali posted "MapView" is the name of his map. However you need to update the foreach loop to the following since you will be iterating to all graphics of the given layer. foreach (Graphic g in lyr.Graphics) {//same code goes here.} Once you have confirmed that none of your graphics have an empty geometry or extent, then that will help us narrow down the issue. FeatureDataGrid zoom to selection handles zoom to point differently than zoom to polyline/polygon, but it should not be a problem if the geometry extent has a value. ... View more

Please visit this help page: http://help.arcgis.com/en/imagemanagement/10.0/help/imageserver_sm/index.html#//008r00000013000000.htm ... View more

We are aware of the COM component error as reported in this thread: http://forums.arcgis.com/threads/15925-Except-Map-and-scalebar-all-controls-fail to resolve this you need to add a reference to System.Windows.Controls.Data.Input before dragging the control to your design. But what I have not seen yet is the "FeatureLayer was not found in type FeatureDataForm" error.  If you did not drag and drop FeatureDataForm to your design, and instead add reference only to the following assemblies: ESRI.ArcGIS.Client.dll and ESRI.ArcGIS.Client.Toolkit.dll, and then add the following code in your XAML, do you get the error? xmlns:esri="http://schemas.esri.com/arcgis/client/2009">     <Grid x:Name="LayoutRoot" > <!-- more code goes here -->         <esri:FeatureDataForm FeatureLayer="{Binding Path=Layers[PointLayer], ElementName=MyMap}" />     </Grid> ... View more

You can use Distinct() from System.Linq and set your ComboBox ItemsSource property, provided that it does not already contain items.  TypeDescComboBox.ItemsSource = (from g in args.FeatureSet.Features             select g.Attributes["TYPEDESC"]).Distinct(); This is just one way, you can also use a dictionary or list to temporarily hold the attribute values and check whether the attribute value already exist before adding to your ComboBox. ... View more

I know that our team is working on providing better KML support for 2.1.  However, can you be more specific on what you think are yet to be supported in the future releases?  Here's a link to our library reference page regarding KML layer: http://helpdev.arcgis.com/en/webapi/silverlight/2.1/apiref/api_start.htm?ESRI.ArcGIS.Client.Toolkit.DataSources~ESRI.ArcGIS.Client.Toolkit.DataSources.KmlLayer.html ... View more

I was only able to replicate the error (The property 'Featurelayer' was not found in type 'FeatureDataForm') when I have incorrectly named the property.  It is case-sensitive.  However, the code you posted has the correct casing and spelling. If it was not able to find FeatureDataForm, the error would be different. If the Binding statement was wrong, the SL app will still compile but have an empty FeatureDataForm. ... View more

I suggest you do the following first before customizing the style. 1. Use ExpressionBlend to get the default style (http://blogs.esri.com/Dev/blogs/silverlightwpf/archive/2010/05/20/Use-control-templates-to-customize-the-look-and-feel-of-ArcGIS-controls.aspx) 2. Use FindName() to get the current scalebar value as suggested in post #5 (http://forums.arcgis.com/threads/15157-Access-ScaleBars-Current-Value) 3. Subscribe to your map's ExtentChanged and retrieve the value as suggested in post #6 in the same thread as above 4. Perform your own calculation of getting the partial values (I'm not exactly sure how you arrived at the formula,  currentvalue * 2 /10 or currentvalue * 6 /10) but check that they are correct. 5. If the default style and the calculation works fine, update the style to include your 2 additional TextBlocks. I think breaking it down into steps/parts, will help you find why the scalebar did not load in the first place. ... View more

The Editor, EditorWidget, TemplatePicker use GeometryService to add/edit polyline and polygon features.  It is used to simplify, auto select, auto complete, cut, reshape, union, etc. Here's some documentation about it: http://sampleserver3.arcgisonline.com/ArcGIS/SDK/REST/geometryserver.html If your feature service only contain points, you can still use the Editor, EditorWidget, TemplatePicker without specifying GeometryService.  You can use just the TemplatePicker to add points and set its ShowAttributesOnAdd to true to enable FeatureDataForm to show after the graphic is added to your map. http://help.arcgis.com/en/webapi/silverlight/samples/start.htm#ToolkitTemplatePicker I suggest that you take advantage of the TemplatePicker and FeatureDataForm because this requires no extra coding on your part, adding TemplatePicker in the XAML should be sufficient. If however, you still prefer to add the point in code, you can still do so. When you create your graphic, you need to set its Geometry and Attributes before adding to your layer.  If you know the FeatureType, you can get the Template corresponding to that type from FeatureLayer.LayerInfo.FeatureTypes[].Templates.http://help.arcgis.com/en/webapi/silverlight/apiref/ESRI.ArcGIS.Client~ESRI.ArcGIS.Client.FeatureService.FeatureTemplate.html . PrototypeAttributes will give you the default attribute key-value pair for the specific type. You also have access to FeatureLayer.LayerInfo.Fields http://help.arcgis.com/en/webapi/silverlight/apiref/ESRI.ArcGIS.Client~ESRI.ArcGIS.Client.Field_members.html. This will determine what acceptable values are for each field.  All these checks are done by TemplatePicker and FeatureDataForm but it certainly is not impossible to navigate your way around doing this in code. ... View more

The Loaded event on ScaleBarValue TextBlock is not necessary.  The thread you are referring to had a specific use case where the current value of ScaleBar is needed to be tracked and converted to a different unit. Ryan's follow-up post #5 proposed an easier way to retrieve the TextBlock using FindName(). If your application does not need to do this extra stuff and you only want to change the look and feel of the controls, just start from the default template. If you have Expression Blend, here's a blog on how it can be accomplished: http://blogs.esri.com/Dev/blogs/silverlightwpf/archive/2010/05/20/Use-control-templates-to-customize-the-look-and-feel-of-ArcGIS-controls.aspx ... View more

The symbol used in EditVertices currently cannot be modified. Exposing EditVertices in the future is something we are thinking about as enhancement in future releases. ... View more

The graphics you are passing probably have Geometry with null SpatialReference. We will try to get more null checks in our API but for the time-being, please check that the Graphics' Geometry SpatialReference is not null. ... View more

I think the NullReference exception comes from resolving the SpatialReference. http://help.arcgis.com/en/webapi/silverlight/apiref/ESRI.ArcGIS.Client~ESRI.ArcGIS.Client.Geometry.SpatialReference~_ctor.html Note that if you want to specify WKID, it's passed as an integer not as string. It is also possible that the Graphics' Geometry have null SpatialReference. Thank you for reporting this - we should add a check in case parameters were incorrect. ... View more

I tried both of your symbols and they look fine to me when I zoom in and out of the map, they are still located at the point where I placed them. The only change I would add is in your PoliceLeft MarkerSymbol, the offsets need to be 40, to account for the Grid that contains the ImageBrush. Below are two graphics located in Redlands and Moreno Valley. I used this as my street map: http://services.arcgisonline.com/ArcGIS/rest/services/ESRI_StreetMap_World_2D/MapServer <esri:Graphic Symbol="{StaticResource PoliceLeftPnt}"> <esri:MapPoint X="-117.171952484027" Y="34.050984501128"/> </esri:Graphic> <esri:Graphic Symbol="{StaticResource PoliceLeft}"> <esri:MapPoint X="-117.22672317423" Y="33.9176215942354"/> </esri:Graphic> ... View more