|
POST
|
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
04-25-2013
08:55 AM
|
0
|
0
|
2322
|
|
POST
|
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
04-25-2013
07:33 AM
|
0
|
0
|
2322
|
|
POST
|
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
04-25-2013
06:50 AM
|
0
|
0
|
2322
|
|
POST
|
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
04-25-2013
06:18 AM
|
0
|
0
|
565
|
|
POST
|
IMaps is in the Carto library. You don't have a Using statement for Carto.
... View more
04-25-2013
06:14 AM
|
0
|
0
|
1585
|
|
POST
|
I believe the ComReleaser class is in the ADF.Connection.Local assembly.
... View more
04-19-2013
10:38 AM
|
0
|
0
|
2036
|
|
POST
|
At 10.0 and higher you should not be referencing the ADF assembly at all. You should be using ADF.Local.
... View more
04-19-2013
05:02 AM
|
0
|
0
|
2036
|
|
POST
|
You are declaring the variable outside of the loop. While it is true that you are assigning it a value inside the loop, it is possible that the loop could be skipped and never iterate (if pStyleItem were Nothing from the start) which would leave the variable unassigned when you use it to assign a value to prenderer.Symbol. You can always avoid this problem by explicitly assigning the variable a value when you declare it: Dim pMarker As IMarkerSymbol = Nothing The line above doesn't actually change anything as pMarker is initialized to Nothing by default and will not be given an actual value in the case where the loop doesn't iterate, but it will make the warning go away. You could also go into Settings and turn the warning off but I think that's a bad idea because getting the warning makes you review your code, which in turn could help you find and fix a logic error that you may have otherwise missed.
... View more
04-09-2013
06:59 AM
|
0
|
0
|
489
|
|
POST
|
You can only add one item at a time with the AddItem method.
... View more
04-04-2013
06:29 AM
|
0
|
0
|
557
|
|
POST
|
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
04-01-2013
09:26 AM
|
0
|
0
|
295
|
|
POST
|
Set the Z value for the point (IPoint.Z) to the elevation value you want to use. Make sure the point is z-aware first (IZAware.ZAware = true).
... View more
03-27-2013
10:05 AM
|
0
|
0
|
933
|
|
POST
|
Lines of sight can be calculated by calling ISurface.GetLineOfSight.
... View more
03-27-2013
06:09 AM
|
0
|
0
|
2113
|
|
POST
|
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
03-26-2013
06:57 AM
|
0
|
0
|
568
|
|
POST
|
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
03-26-2013
05:32 AM
|
0
|
0
|
568
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-20-2014 05:29 AM | |
| 1 | 02-01-2011 04:18 AM | |
| 1 | 02-04-2011 04:15 AM | |
| 1 | 01-17-2014 03:57 AM | |
| 1 | 10-07-2010 07:37 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:23 AM
|