Our setup (installshield) copies those file to this location. Those file then have to be installed in the following folder: %Program files%\Common Files\ArcGIS\Desktop10.0\Configuration\CATID They now generate those *.ecfg (xml in a zip file) with the EsriRegAsm.exe tool. dll.ĮSRI is no longer using the registry for the component category registration. The option, that may not work as ESRI does not use Registry to listen for Component Categories Items anymore, was to deploy using for example, an MSI such as Advanced Installer and use RegSvr32 for example, to register the. It was my understanding, from the Developer Summit, you must have a Licensed Product on the deploying machine. Without those files, the developed tools won't work. Those *.ecfg files contain the category registration for ArcMap or what else. The suspicous "esriregasm.exe" tool does not work standalone, it seems, that ArcGIS has to be installed. So, does anyone have an idea, on how to create the registration files (*.ecfg), which will be deployed on the users machine. Note: on a build server there is NO ArcGIS installed! And we do not deploy with VisualStudio!
I don't know if I'm the only tracking down this problem.Īssume that you have a build server (like hudson) and you like to build all your assemblies and dlls on this build server.
0 kommentar(er)
