Latest Contributions by RyanCoodey

Sorry for the late reply guys, just saw all the posts thanks to Patrick. So what I did is attach the measure action on the maps PreviewMouseDown (that is if the tool is selected).  This way when it is finished, it is not tied right back into the map.  Also, with the release of the 2.2 API, we can now stop a measure action by calling MeasureAction.Detach(). Here are some of my methods:         protected void AttachMeasureAction(Map map)         {             if (!MeasureActionSelected && map != null)             {                 MeasureActionSelected = true;                 //ToolLock = true;                 map.Layers.CollectionChanged += Layers_CollectionChanged;                 MeasureAction.Attach(map);                 MeasureAction.Execute();             }         }         protected void StartMeasureAction()         {             DisableMeasureAction();             foreach (Map map in InternalMaps)             {                 map.PreviewMouseDown += Map_PreviewMouseDown;                 map.Cursor = Cursors.Hand; //Need to reset cursor because measure action changes it upon finish             }         }         protected void DisableMeasureAction()         {             MeasureAction.Detach();             foreach (Map map in InternalMaps)                 map.PreviewMouseDown -= Map_PreviewMouseDown;             MeasureActionSelected = false;             //ToolLock = false;         } //Events         protected void Map_PreviewMouseDown(Object sender, System.Windows.Input.MouseButtonEventArgs e)         {             DisableMeasureAction();             AttachMeasureAction((Map)sender);         }         protected void Layers_CollectionChanged(Object sender, System.Collections.Specialized.NotifyCollectionChangedEventArgs e)         {             //Restart measure action when finished             if(MeasureActionSelected)             {                 if (e.OldItems != null)                 {                     for (Int32 i = 0; i < e.OldItems.Count; i++)                     {                         if (e.OldItems is GraphicsLayer && ((GraphicsLayer)e.OldItems).ID == null)                         {                             StartMeasureAction();                              break;                         }                     }                 }             }         } Hope this helps! ... View more

Well, I ended up contacting support about this and got this response: I investigated further and found that a product defect had already been logged for this issue. #NIM065082- Add-in ComboBox dropdown is not under the ComboBox, it appears under the caption. The current status of the Bug is 'Rejected'- Reason for Rejection is "as designed" Unfortunately, this is by design and part of the add-in framework. The workaround would be to keep the showCaption="false". This makes absolutely no sense though.  I don't think I have ever seen a ComboBox that was "designed" this way... even ESRI's own ComboBox's don't behave this way (ex. Spatial Analyst Toolbar).  I sent an enhancement request back asking for an option to adjust this alignment then, but kind of doubt this will happen.  Sorry, don't mean to rag on ESRI, they do exceptional development work... just don't understand their position on this one. ... View more

ESRI support helped me out... When creating a new attribute index, the �??unique�?� option is disabled (grayed out) for versioned feature classes.  The only way around this is to make a copy of the feature class (which will not be versioned), delete the original and rename this new one�?� then you must create ALL unique indexes before registering as versioned. ... View more

Marcus, From what I can tell, 2.2 Beta has this issue, but the 2.2 Final will have it fixed (not released yet).  Check out the post I made here: http://forums.arcgis.com/threads/27909-MeasureAction-in-Web-Mercator-Issues...?highlight=web+mercator ... View more

Yep, just signing the assembly with a strong name key fixes the problem... don't even have to change the version number on the assembly. Thanks for all your help Richard! ... View more

Hmmm, you have to use a strong name to use versioning... I wonder if all I need to do is sign the assembly and provide a strong name key... I'll try that out and report back. ... View more

There are many options.  You might try changing the version of the shared code and then have the assembly which references the shared code set the properties on the reference to indicate that it is version specific. Unfortunatly you can not set the Specific Version flag when the reference is to another project.  Suppose I could compile the assembly and reference that, not ideal though.  Not sure if this will work either... There are many options.  Create a different assembly for each project, i.e. share the actual underlying C# files but have a different Visual Studio project which builds a different assembly. Again, not ideal, but should work... There are many options.  Literally install the shared assembly in the GAC (I understand why XCopy is easier). Kinda defeats the appeal of add-ins in my opinion if we go this approach. I'll see what I can come up with... thanks! ... View more

Sounds like your problem might be your approach to shared code.  For example, I think that if the sharedcode assembly is already loaded from a previous add-in then it will not reload.  Perhaps the references should be Version Specific? I agree, this is exactly the problem... and this is what I am trying to work out.  I have tried incrementing the referenced assemblies build number, and the add-in project is referencing this new version number... but it still seems to use the older assembly from one of the other add-ins... Am I missing something?  I don't need to give the assembly a unique filename, say with the build number in it, do I (that would be a bit annoying to manage)? Thanks a lot for all the help so far Richard! ... View more

Thanks for the reply Richard! The add-ins are being delivered by placing the .esriAddIn file on a network share.  The users have this share location set in their registry's "AddInFolders" key. The assemblies are deployed inside each of the .esriAddIn files, so if the assembly is used in several different add-ins (shared), then it is zipped into both add-in packages.  They are not registered and not in the GAC.  We just want to do an xcopy like deploy... I have never used "fusion log viewer", I will check it out. Thanks a lot! ... View more

Any ideas anyone?  Thanks! ... View more

Any chance you could post the MapSplitter control? Hi Yeltad, I can't share too much code since it technically belongs to the company I work for... but I have attached this control with a few little things stripped out.  I wrote this code back when I was learning WPF, so it may not be the best either :P.  Hope it helps some though. Sorry for the late reply, I was out on vacation... ... View more