Marko Apfel - Afghanistan/Belgium/Germany

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

  Home  |   Contact  |   Syndication    |   Login
  178 Posts | 2 Stories | 149 Comments | 4 Trackbacks


Twitter | LinkedIn | Xing

Article Categories


Image Galleries



Enterprise Library


SQL Server


November 2011 Entries

Problem this code does not work Type t = typeof(ESRI.ArcGIS.Framewor... System.Object obj = Activator.CreateInstance(t); but yet this code Type t = Type.GetTypeFromCLSID(typeo... System.Object obj = Activator.CreateInstance(t); Reason In the first variant the runtime tries to cast to AppRefClass . This is not possible. And in the second one, the runtime does not knows anything about AppRefClass. So it leave it as IUnknown. (originally communicated ......

Why such constructs are included in the csproj-Files? <CodeAnalysisRuleSetDire... Files (x86)\Microsoft Visual Studio 10.0\Team Tools\Static Analysis Tools\\Rule Sets</CodeAnalysisRuleSe... <CodeAnalysisRuleDirecto... Files (x86)\Microsoft Visual Studio 10.0\Team Tools\Static Analysis Tools\FxCop\\Rules</Code... So it every projects needs some manual steps to clean the project file so the solution could be build on ......

Problem Normally I try to have my continuous integration as most a possible toolset free to ensure that no local stuff could have an impact to my build. My Silverlight app references a special compile target in a folder outside my developer tree: <Import Project="$(MSBuildExtension... /> So I copied the stuff from this folder to a local one and changed the call to this target in my csproj: <Import Project="..\..\..\tools\Web... ......

Problem Normally PostSharp runs fine on unattended build servers. So on our global Jenkins continuous integration server PostSharp does the job. But on my local TeamCity continuous integration server I got the following error: POSTSHARP error PS0127: The aspect 'EsriDE.Commons.Logging.Aop... uses non-licensed features (Basic Features). Please visit to acquire a license of PostSharp. POSTSHARP error PS0154: Information regarding the previous ......

Problem Our global Jenkins continuous integration server throws this error during compile step. My local TeamCity continuous integration server runs fine. What is the difference. Background I integrate some static code analysis steps via MSBuild-targets in the csproj files. To allow a fast developing without a code analysis for ever compiling I bound these targets only to RELEASE-configuration. With the MSBuild element <ImportGroup> only one condition must be specified. So my construct was: ......

Problem A continuous integration server should only have a minimal toolset installed. This ensures that no unwanted libraries could affect the build and other steps. Clearly that with this slogan also StyleCop should not be installed to the CI server. But we wanna have this analysis as an part of the whole build. Solution Prerequisites First at all we need the necessary files from StyleCop (the core assemblies and the target). The easiest way is to download the MSI of StyleCop, install the software ......


When using xUnit and constructs like Debug.WriteLine the DbgView-tool does not show the written output anymore.


Add a new Listener – for example:

Debug.Listeners.Add(new DefaultTraceListener());

Problem I must go back to an older package version (from to but the Package Manager Console does not allow this. With the command Update-Package EsriDE.Commons.System.Utils -Version I got the error: Update-Package : Already referencing a newer version of 'EsriDE.Commons.System.Utils'. Solution Don’t worry. You could uninstall the package Uninstall-Package EsriDE.Commons.System.Utils -Version and install the older one instead. Install-Package EsriDE.Commons.System.Utils ......

As an GWB-influencer I had the chance to review SmartAssembly.

Because obfuscation is an important part in protecting intellectual property this review chance was a good start for this. The first few clicks show that not only obfuscation could be made with SmartAssembly but also some other very interesting things.

The complete review could be read here: GWB-Review SmartAssembly