Marko Apfel - Afghanistan/Belgium/Germany

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

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


Twitter | LinkedIn | Xing


Post Categories

Image Galleries



Enterprise Library


SQL Server


September 2010 Entries

Today i have tried to use a Castle Windsor in an project based at .NET Framwork 3.5 Client Profil. This is not possible because somewhere in the Castle Windsor assembly a reference to System.Web is made.

Only for .NET Framwork 4 Castle Windsor offers assemblies for both profiles.

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 ......

My short summary This comparison is mainly originated with attention to XML-based configuration possibilities and grouping implementations of the same contract which are choosable over a key. StructureMap A really nice container with simple XML configuration. But we had problems if the container must instantiate WPF-controls. LightCore Also a really nice container with simple XML configuration. But it seems that there is no way to specify distinct implementations which are choosable by a key. Autofac ......

Problem context We use a backgroundworker to load MXD documents from several places of the system and extract meta data and thumbnails which a GUI component shows in an asynchron way. The unit tests for this logic throws an exception during the access the thumbnail: 'mapDocument.Thumbnail' threw an exception of type 'System.Runtime.InteropServ... exception = {"Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))"TargetSite = {stdole.IPicture get_Thumbnail()} Solution ......

Starting a new Visual Studio solution through the IDE is offen too complex and time wasting. Other programs allows per default to create a blank document with the explorer context menu. Why not offer this functionality for Visual Studio? This is no problem – with a blank solution file in the %SystemRoot%\ShellNew folder and addional informations in the registry you have this: The whole bundle is downloadable under: ExplorerContextmenuForCreat... ......