Latest Contributions by NeilClemmons

You have 2 errors in your code that need to be resolved.  Try fixing those and see if you still get the error when you run the app. ... View more

The error is complaining about not finding the 9.3 version of the System assembly - "ESRI.ArcGIS.System, Version=9.3.0.1770". Make sure you are referencing the 10.1 version of this file.  The same goes for all of your ESRI references. ... View more

Make sure the VersionSpecific property on all of your ESRI project references is set to False.  You may also need to remove the references and add them back in. ... View more

Add the Using statement. ... View more

If you want to filter a feature layer in your map to show only a subset of the features it contains then you can set a definition query on that layer.  Use IFeatureLayerDefinition.DefinitionExpression to set the query. ... View more

IMaps is in the Carto library.  You don't have a Using statement for Carto. ... View more

At 10.0 and higher you should not be referencing the ADF assembly at all.  You should be using ADF.Local. ... View more

You can only add one item at a time with the AddItem method. ... View more

If the field is a true Date field then need to set its value using a Date.  Convert the textbox value to a Date type and it should work. ... View more

Lines of sight can be calculated by calling ISurface.GetLineOfSight. ... View more

No, a recycling cursor does not release the feature objects.  It uses the same instance of a Feature object over and over.  For this reason, you shouldn't use a recycling cursor if you intend to modify the features it contains. ... View more

This post has been very helpful.  I had the same error but not for the same reason. I found two ways to successfully edit the attributes and would like to know which way is better. This one uses Update:    _SFRMPSelectionSet.Update(null, false, out pCursor);                  if (pCursor == null) { return false; }            pRow = pCursor.NextRow();            while (pRow != null)              {                  foreach (var pair in dictFieldsValues)                  {                    fldIndex = _SFRMPFeatureLayer.FeatureClass.Fields.FindField(pair.Key);                    objectValue = pair.Value;                             pRow.set_Value(fldIndex, objectValue);                  }               pCursor.UpdateRow(pRow);               pRow = pCursor.NextRow(); This one uses Store: _SFRMPSelectionSet.Search(null, false, out pCursor);                 if (pCursor == null) {return false; }            pRow = pCursor.NextRow();            while (pRow != null)              {                  foreach (var pair in dictFieldsValues)                  {                    fldIndex = _SFRMPFeatureLayer.FeatureClass.Fields.FindField(pair.Key);                    objectValue = pair.Value;                      pRow.set_Value(fldIndex, objectValue);                  }               pRow.Store();               pRow = pCursor.NextRow(); Thank you so much. In general, using the Update cursor is faster, especially if you're updating a large number of records.  However, there is a certain amount of overhead that comes with using the Update cursor.  If you're only going to be updating a handful of records (less than a hundred or so), then the Store method is probably going to be quicker.  If you don't know how many records you're going to be updating or if you're writing a general function where the number can vary, then go with the Update cursor. ... View more