We are trying to automate reconcilation and post activity . But during reconcilation version having conflicts could not be reconciled.
So we are trying to make "mark as visited" all the conflicts using Arcobject .
Kindly suggest us Arcobjects for "mark as visited" option.
There is no help that translates the interactive interface terms to the ArcObjects environment for handling version conflicts. Most likely that is because to use ArcObjects you actually have to code every step that the interactive interfaces actually set in motion when the user selects the option to Mark as Visited. (Generally for every step in the user interface there are at least 10 to 100 steps in ArcObjects underlying it). This means you have to act directly on the versions through the Version interfaces and probably cursors. Unfortunately nothing describes the code underlying those interactive interfaces in the help docs. The best I found was to read the Versioning help topic set and its subtopics and look up and experiment with the direct APIs of the interfaces and tools listed for ArcObjects that it leads you to.
Those topics give code that does much of what the interactive interfaces are in reality doing through ArcObjects, such as detecting conflicts and removing conflicts from the conflict set. But it does not specifically walk through what the Mark as Visited option is in reality doing through ArcObject anywhere. The closest help topic to what you need to do seems to be How to merge conflicting geometries during a reconcile. At a guess, I would say that removing conflicts from the conflict set for a version in favor of the Reconcile rule (Mark as Visited) involves much the same process as this code gives, except that it would have to resolve every field to match the desired version, not just the shape field. In theory, the Mark As Visited option could be as easy as simply removing the conflict from the conflict set, since the Reconciled version is the version you want accepted, and you may not even have to read or alter any field information at all.
Surround all of your code modifications in Try blocks, because there is no telling what errors you may trigger with this kind of code and be sure to operate on experimental data only while developing the code to avoid data corruption or loss. If you come up with anything using this information, share in on the ArcObjectsSDK forum. I'm sure others would benefit and perhaps be able to assist you if you get stuck.
