Latest Contributions by JeffMatson

Are you attempting to pass in Direct-Connect parameters in your property set?  If so you likely need to add several parameters, and also make sure your Instance parameter is correct.  (We have an Oracle database and the Instance parameter to be passed in via PropertySet is different than what ArcCatalog reports - not sure if that is the same for your SQL Server database or not...) ... View more

Hi Harald, Event variables can go out of scope at "unexpected" times.  You'll need to wire/unwire event handlers and hydrate variables at all event boundaries. For example if someone opens a particular mxd, the OpenDocument event fires, followed by BeforeCloseDocument and CloseDocument, then another OpenDocument.  Any variables hydrated at the first OpenDocument will have gone out of scope and the RCW error will occur the next time they are referenced. Instead you would want to use modular level variables which are hydrated at OpenDocument and released at BeforeCloseDocument, then hydrated again during the next OpenDocument so you have a "fresh" instance. This event lifecycle is similar for Map events, Edit events, etc.  Below is an outline that should help for a simple MXD with one map in it.  It gets more complicated when switching between multiple data frames, edit sessions and workspaces, etc. Startup event fires    (+DocumentEvents - set up listeners for OpenDocument, NewDocument and BeforeCloseDocument)       OpenDocument/NewDocument event fires (initial ArcMap opening event)          (+MapEvents)          (+EditEvents)       BeforeCloseDocument event fires (this fires before the actual MXD that was chosen opens)         (-EditEvents)         (-MapEvents)       OpenDocument/NewDocument event fires   (now we are in the MXD selected for opening and ready for action)          (+MapEvents)          (+EditEvents)    ----------------------------------------------------------------    The bulk of operations occurring in your session    ----------------------------------------------------------------        BeforeCloseDocument event fires  (session is done, user is either opening another MXD or closing ArcMap)       (-EditEvents)       (-MapEvents) Shutdown event fires   (user is definitely closing ArcMap at this point)    (-DocumentEvents) ... View more

I think you'll want to set up your event using a variable: ArcObjects 10 .NET SDK Help  I've also utilized a counter to help avoid RCW errors when deprecating event listeners: private void SetupCoreFrameworkMapEvents() { if (m_application.Document.Parent is IMxApplication && m_sbRefs_MapEvents == 0) { m_VersionChanged = new CoreFramework.FrameworkVersionChangedEventHandler (WaterEditorExtension_ExtensionVersionChanged); m_coreFramework.FrameworkVersionChanged += m_VersionChanged; m_sbRefs_MapEvents += 1; } } private void RemoveCoreFrameworkMapEvents() { while (m_sbRefs_MapEvents > 0) { if (m_VersionChanged != null) { m_coreFramework.FrameworkVersionChanged -= m_VersionChanged; } m_sbRefs_MapEvents -= 1; } } ... View more

I feel like we've had this conversation before  Any idea *when* this will be available?  Also how about Undo/Redo events? Thanks, Jeff ... View more

Assuming you set up your representation's geometry editing behavior to use Override geometry, you can set IRepresentation.Shape to the modified geometry, then call IRepresentation.UpdateFeature() and finally call IFeature.Store(). ... View more

Sorry, I haven't messed with the Datastore object yet.   This works for an SDE layer that isn't in the map: Geodatabase geodatabase = new Geodatabase(new DatabaseConnectionFile(new Uri(" [full path to connection file] "))); var fc = geodatabase.OpenDataset<FeatureClass>(" [featureClass name] ") as FeatureClass;‍‍ ... View more

I'm assuming your SDE feature class is listed as "editable" in the List by Editing tab?  Are you hydrating the fc variable from a map layer or from a geodatabase object? ... View more