When Visual Studio compiles your ESRI components, it registers them in the ESRI component categories. In order to do this, it must have write access to the system registry. You have a couple of options - run Visual Studio as an administrator every time you start it up or turn off UAC on your machine. If you're registering your component via Add from File on the Customize dialog in ArcMap (not the optimal way of doing it if you're actively developing) then ArcMap must be running as an administrator (or turn off UAC). This will not impact your users. When your application is deployed, the Windows installer will kick off the registration. Of course, it must be running with elevated privileges but that is standard. Installing software is a task that should only be performed by an administrator. The only way around all of this is to rewrite your application as an addin. Addins do not require admin privileges to deploy. hello Neil and Agray1 It wasn't the running of Visual Studio as an administrator, or installing the extension as an administrator which was a problem. As the UAC policy is controlled centrally here I don't have any ability to control that. What the problem was, and my apologies for not being clear, is that a tool in the extension which brought up a window and allowed a number of things to be done. One of those things calls another tool (the second tool is not visible in the tool bar). This second tool was not working. I tried adding it to the extensions toolbar - and it worked. I tried running ArcGIS with administrator rights (when the second tool was not in the extensions toolbar - and it worked). Neither of these were acceptable. This morning I looked back at the setup project and then started comparing it to what it should look like - Neil, your comment in another thread make me think about this option http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#/How_to_deploy_a_custom_component_using_a_setup_project/00010000016r000000/ For some reason I had stopped before the Registering the CustomComponent .dll file using ESRIRegAsm.exe step of the process. So I did this step of the process. And now it works. cheers shawn
... View more
If your Command/Tool does not have any registration code and you are manually "Add From File" via the Customize dialog, then try to add the type library (.tbl) file instead of the .dll file. http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#//00010000040v000000 thanks James, that worked perfectly ... will worry about proper deployment of the whole thing once I've reached that stage ...
... View more