Latest Contributions by EagerIp

Editor extensions do not get listed in the Extension Manager dialog since they are managed by the Editor instead. If you implement a regualr extension, the show in extension dialog property will apply. ... View more

1. Debugging .NET 4.0 code in ArcMap.exe You are correct that the .config file locks down Visual Studio on the target debugger type. That means if you want to debug .NET 3.5 code, you will have to update the .config file again. A neat trick I learnt from a Visual Studio blog without changing the .config file manually is to add "ArcMap.exe" to your solution as an .exe project in Visual Studio using File > Open > Project/Solution, Select Exe project files (.exe) from the file extension filter. Then you can switch the ArcMap project's debugging properties (open Properties page, Parameters > Debugger Type) to which ever target .NET runtime version you need. Of course, don't forget to set ArcMap.exe as your startup project before debugging. Unfortunately, Exe project is not supported in VS Express editions so you have to manually edit the config file back and forth in such case. 2. Config file at deployment time... Note that the startup supportedRuntime elements in the ArcMap.exe.config should only affect debugging experience in Visual Studio. At runtime, these xml elements are irrelevant to your custom managed COM ArcObejcts or Add-ins. They will run fine without adding any startup v4.0 element. The only requirement you have to check at deployment is whether the target machine has .NET 4.0 installed. Hope these help. ... View more

The link I posted troubleshoots two slightly different problems. The one I'd like you to try is to attach esriRegasm.exe to debug through your project using Visual Studio. OK. The /e option doesn't give a lot of information. Can you try to debug if the error stems from any of the ComRegisterFunction() inside the failed assembly? You can do so by setting esriRegasm.exe as the debugging external program in Visual Studio. (And it is better if you remove or comment out the BeforeClean/AfterBuild xml from the project file before debugging.) Under Start Action ------------------ Start external program: C:\Program Files\Common Files\ArcGIS\bin\ESRIRegAsm.exe or on a 64 bit OS C:\Program Files (x86)\Common Files\ArcGIS\bin\ESRIRegAsm.exe Under Start Options ------------------- Command line arguments: "NewFindAcctTool.dll" /p:Desktop /e Working directory: {directory of the NewFindAcctTool.dll} Tips on commenting out BeforeBuild/AfterBuild Right-click the project in Solution Explorer and choose Unload Project. After project is unloaded, right-click it again and choose "Edit NewFindAcctTool.xxproj" The project file will be displayed in raw text format. Locate the following xml section near the bottom of the project file and comment it out (i.e. wrap them between <!-- -->). Save changes and reload to start debugging. <Target Name="BeforeClean">   <Exec     WorkingDirectory="$(CommonProgramFiles)\ArcGIS\bin"     Command="esriRegasm.exe &quot;$(TargetPath)&quot; /p:Desktop /u /s"     Condition="Exists('$(TargetPath)')"/> </Target> <Target Name="AfterBuild">   <Exec     WorkingDirectory="$(CommonProgramFiles)\ArcGIS\bin"     Command="esriRegasm.exe &quot;$(TargetPath)&quot; /p:Desktop /s"/> </Target> ... View more

Hi fellj, I see now that your error is different than the original post. See if you can try to debug it with the troubleshooting suggestion posted on 2/2/2010 in the following thread http://forums.arcgis.com/threads/1162-Beta-10-Issue-with-ESRIRegAsm?p=4267#post4267. The goal is to attach esriRegasm.exe to step into your code and see if it throws any useful information during debugging. ... View more

Check to see if you have the right permission to write to \Program Files\Common Files\ArcGIS\Desktop10.0\Configuration\CATID. Use "Program Files (x86)" if it is a 64-bit OS. ... View more

Can you provide more detail information on how to reproduce the crash? Can you reproduce this consistently with a new add-in project?  It will also help if you have screenshots of the error report and the config.esriaddinx file in the project. ... View more

EsriRegAddin only deploys to the current user location at 10.0. Instead of typing the long command in a command prompt, it is more convenient to just double click the .esriAddIn file. It should spin up EsriRegAddin.exe and its wizard. See if this gives you more clue on what's wrong with the deployment. ... View more

When you installed VS2010, did you install C# and VB.NET features? When you installed Engine .NET SDK, did you explicitly select VS2010 from the install feature list (you may need to go to the Custom install option page)? After verifying the above, check to see if you have .vstemplate files installed under \Program Files\Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplates\CSharp\ArcGIS. If so, see if running "devenv /setup" from the VS2010 command prompt fixes the problem. ... View more

Looks like you cannot deploy any add-in at all on this particular machine 😞 The error message generally means during the file copy operation you don't have the correct permission to deploy the add-in to [My Documents]\ArcGIS\AddIns\Desktop10.0 folder. I know you've mentioned you have admin privileges but you may want to double check if you can write to that folder. ... View more

The build output doesn't give much clue. Can you try the esriRegAddIn utility in a cmd prompt without the silent flag and see if it gives you more information? For example, cd \Program Files\Common Files\ArcGIS\bin esriRegAddin.exe "C:\VisualStudio\Projects\CustomUIElements\CustomUIElements\bin\Release\CustomUIElements.esriAddIn" There can be error in the config.esriaddinx file or ArcGIS not installed properly. Do you have Desktop installed? ... View more

DockableWindow is a bit tricky here since it is implemented by two classes - 1) the UI part is the designer surface derived from controls and 2) the non-UI part is the class actually inherits from DockableWindow base class. FromID can only handle types derived from base classes declared in ESRI.ArcGIS.Desktop.AddIns.dll. You have to pass in the type that inherits DockableWindow, which is the inner class of the designer window itself if you are using the Add-in Wizard. If you go to the xml declaration of the dockable window, you will see the class attribute is set to �??DockableWindow1+AddinImpl�?�. You have to pass this type to get the dockablewindow implementation class first, then you have to expose a property there get a hold of the UI window. public class DockableWindow1 : UserControl { ... /// <summary> /// Implementation class of the dockable window add-in. It is responsible for /// creating and disposing the user interface class of the dockable window. /// </summary> public class AddinImpl : ESRI.ArcGIS.Desktop.AddIns.DockableWindow {   private DockableWindow1 _windowUI;   ...   internal DockableWindow1 UI   {     get { return _windowUI; }   } } } var winImpl = AddIn.FromID<DockableWindow1.AddinImpl>(ThisAddIn.IDs.DockableWindow1); DockableWindow1 dock = winImpl.UI; ... View more

Hi Tony, Did you create the project from scratch in Visual Studio 2010 or it's an upgrade from 2008? What is the target .NET framework set for the add-in project?  Since an add-in project should not be registered with COM, make sure "Register for COM interop" is unchecked and the ESRI.ArcGIS.Deskop.AddIns assembly reference Copy Local property set to false. If the above doesn't fix the build problem, a full build log from the output window should help to diagnose this. You may want to change the MSBuild verbosity to Normal/Detailed in the Visual Studio Options dialog (Tools > Option, Projects and Solutions > Build and Run) before pasting the log here. ... View more

The ArcGIS 10.0 registration step is performed at the build process so you won't see anything in your source code files. Instead the project file needs to be updated. The following migration help topic should help solving the problem. http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#/Migrating_ArcGIS_9_3_Desktop_and_Engine_custom_components_to_ArcGIS_10/0001000002m2000000/ And check out the "Register ArcGIS Desktop custom components > ESRIRegasm" section ... View more

I was able to successfuly incorporate the dockable window into my custom component. It was working fine. Then, I copied the visual studio solution to a different development computer and now the GetDockableWindow() call returns nothing. The dockable window is part of my custom component, it is not a separate dll or assembly. It seems like the guid for the dockable window got lost somewhere. Any ideas? Do I need to remove the dockable window (user control) from my project and re-add it? Did you run Clean to your solution after moving it or do a Rebuild? If you just copy the project over along with the compiled binary on another machine and just run build, Visual Studio may assume the project is up-to-date so it won't regenerate the dlls and esriRegasm won't be run to register the extra component. ... View more

When I run the "set" command from a DOS window to show the environment variables on a 64 bit machine, this is a subset of what I see: CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files The problem is that ESRIRegAsm is not in CommonProgramFiles but rather CommonProgramFiles(x86). In case it matters, the version of Visual Studio that I am using is 2010.  Perhaps that is the issue because 2010 uses MSBUILD?  Does 2010 on a 64 bit OS work for you?  What does it say when you run set" from the command line? You are correct that esriRegasm.exe lives in the x86 folder but the environment variable set in a regular command prompt is different than MSBuild running inside Visual Studio. Both Visual Studio 2008 and 2010 uses MSBuild to compile C#/VB.NET projects (VC++ projects switch over to MSBuild at 2010). All versions of Visual Studio are 32-bit applications and the $(CommonProgramFiles) environment variable with MSBuild running inside by default points to the x86 folder. You can verify this by putting these lines in the post/pre-build event echo $(CommonProgramFiles) echo $(ProgramFiles) And observe the results in the Output window   C:\Program Files (x86)\Common Files   C:\Program Files (x86) As long as the samples are compiled in Visual Studio, it should know where to find esriRegasm.exe. If you are running a batch script outside the Visual Studio/MSBuild environment, then you have to be careful to look for the x86 folder. Hope this helps. ... View more