Marko Apfel - Afghanistan/Belgium/Germany

Management, Architecture, Programming, QA, Coach, GIS, EAI

  Home  |   Contact  |   Syndication    |   Login
  187 Posts | 2 Stories | 201 Comments | 4 Trackbacks

News



Twitter | LinkedIn | Xing

Archives

Post Categories

Image Galleries

C#

Enterprise Library

SAP

SQL Server

Technologie

Namespaces of components in an Add-In

It seems that there is only one namespace for all components in an Add-In allowed. The namespace is defined over an attribute of the tag <AddIn>. And this tag is allowed only once per config.esriaddinx file.

That worried me stomach pain! If i group the content of my UI-component in distinct folders (separate buttons, extensions, ..) it is common sense that these folders are part of the namespace. So distinct components have distinct namespaces – and this could not be packed in an Add-In.

Additional content for an Add-In

Particularly in IoC-based development you have several assemblies which build together your application. Offen and normally the different projects are not referenced among each other. So the Add-In compile process ad hoc could not resolve all assemblies which are needed for the package – we need to specify additonal content. In my opinion this is a little bit ugly.

  1. Create a folder install in your Add-In project
  2. Add addional content to this folder as a link – be carefully that you really choose “Add as link”!
  3. Specify for all additional files under properties (F4) the Build Action to “AddInContent”

Today is fully unclear for me how the mechanism works for resolving the content. Additional and automatic resolved content is strangely mixed – especially if you want to include pdb-files.

Extending the table context menu over an Add-In

Items of the table context menu could only be of the following types

  • CommandBar
  • Button
  • Makro

If you want to extend this menu over an Add-In, so you must create a button. This button could then inserted in the menu.

But unfortunately this button then appears also in the customize dialog. Till yet i have no nice solution to suppress this behaviour.

posted on Wednesday, September 8, 2010 12:08 PM