In ArcGIS Pro SDK CoreHost, managing data access and concurrency differs significantly from ArcObjects. Unlike ArcObjects, where you could explicitly query schema locks using ISchemaLock.GetCurrentSchemaLocks, CoreHost abstracts lock management. The SDK assumes you have appropriate permissions and handles concurrency internally. If conflicts arise, operations like editing or schema modifications will throw exceptions, signaling lock or access issues.
Instead of directly working with schema locks or load-only modes, CoreHost provides tools like the EditOperation class to manage data edits in a transactional and efficient way. Below is an example of how you can manage edits, such as deleting features or rows, using the EditOperation class
await QueuedTask.Run(() =>
{
// Create an EditOperation to delete features
var deleteFeatures = new EditOperation() { Name = "Delete Features" };
// Access the first standalone table in the active map
var table = MapView.Active.Map.StandaloneTables.FirstOrDefault();
if (table == null)
{
throw new InvalidOperationException("No standalone tables found in the active map.");
}
// Specify the ObjectID of the row to delete
long oid = 1; // Replace with the actual ObjectID you want to delete
deleteFeatures.Delete(table, oid);
// Delete all selected features in the active view
// Create a polygon geometry for selection (example; replace with your geometry)
var polygon = GeometryEngine.Instance.Buffer(MapPointBuilder.CreateMapPoint(0, 0, SpatialReferences.WGS84), 10);
// Select features in the active view using the polygon
var selection = MapView.Active.SelectFeatures(polygon);
deleteFeatures.Delete(selection);
// Execute the EditOperation
if (!deleteFeatures.IsEmpty)
{
bool result = deleteFeatures.Execute(); // Returns true if the operation succeeds
if (!result)
{
throw new Exception("Delete operation failed.");
}
}
// Alternatively, use the async variant
// await deleteFeatures.ExecuteAsync();
});
