Developing Custom Metadata Editor for ArcCatalog using C#.NET
-
Hi, I am trying to develop a custom metadata editor for ArcCatalog(ArcGIS), using VB.NET. I am using a COM component into my application. i am using esriObjecLibrary 1.0 into my reference, and its a .dll project, using VisualStudio.NET 2003. this metadata editor will be a pluging into ArcCatalog. after writing the code, when i compile the project it says "Unable to emit assembly: Referenced assembly 'Interop.StdType' does not have a strong name".. I went to the DOS prompt and gave a strong name to the assembly and added the assembly file into my AssemblyInfo.vb file, but still its not working. if any of you have worked on this and know much about it, i will appreciate ur help...if u have worked on similar problem using C#.NET that will be of much help... Thanks software Used: Visual Studio.NET 2003 ArcGIS 8.2 VB.NET Platform: win2k abhishek
-
Hi, I am trying to develop a custom metadata editor for ArcCatalog(ArcGIS), using VB.NET. I am using a COM component into my application. i am using esriObjecLibrary 1.0 into my reference, and its a .dll project, using VisualStudio.NET 2003. this metadata editor will be a pluging into ArcCatalog. after writing the code, when i compile the project it says "Unable to emit assembly: Referenced assembly 'Interop.StdType' does not have a strong name".. I went to the DOS prompt and gave a strong name to the assembly and added the assembly file into my AssemblyInfo.vb file, but still its not working. if any of you have worked on this and know much about it, i will appreciate ur help...if u have worked on similar problem using C#.NET that will be of much help... Thanks software Used: Visual Studio.NET 2003 ArcGIS 8.2 VB.NET Platform: win2k abhishek
Create a key pair using sn.exe -k KeyFile.snk. When you generate an interop assembly, use the /keyfile:<filepath> switch to both tlbimp.exe and aximp.exe (if importing an ActiveX control to derive from
AxHostas well). If you're doing this from within VS.NET, go to the project configuration and in there is a place you can either entire a file path (relative to the project root) or a key container name. I typically install my key into my machine store using sn.exe -i KeyFile.snk MyContainerName (obvious use a container name you want). I would delete the interop assemblies you've already created and regenerate them as I've mentioned here. Also be sure you use a key pair (possibly the same one - it helps identify your assemblies, though it's not verifiable like X.509 certificates). A strong name requires that the assembly be signed, which you seem to already know. A strongly named assembly can only use strongly named assemblies.Microsoft MVP, Visual C# My Articles