# Marko Apfel - Afghanistan/Belgium/Germany

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

Home  |   Contact  |   Syndication    |   Login

# November 2009 Entries

For a general applicability i tried to specify the WorkingDirectory attribute in a qotted manner: <WorkingDir>&quot... or <DoubleQuotes>%22<... <WorkingDir>$(DoubleQ... The Exec task self is <Exec WorkingDirectory="$(Working... Command="$(ExtractComCatego...$(InputDirectoryArg) $(FilterArg)$(SeparationArg) ......

After installing VS2005 TE on my machine (which previously runs Visual Studio 2008 TE) all mixed projects (VS2005/VS2008 compatibility with TargetFramework=2.0 and ToolsVersion=2.0 options) thrown an error during compilation: C:\Program Files\MSBuild\Microsoft\Vis... error : In order to perform Code Analysis on managed binaries, MSBuild needs to launch FxCop. MSBuild is unable to locate the FxCop binaries. Make sure Visual Studio Team ......

Open a “visual studio command prompt” and try: tfsbuild stop https://*****:8143 RXXXXX_Sourcecode Gen_2.6_branch_test_20080827.1 ......

By using the argument line array of Main(string[] args) it is important to know such effect. If you specify a quoted folder (e.g. "C:\Projects\PDE\PRJ_EsriDE... the ending backslash makes troubles. My whole argument line (linebreaked for better viewing): -inDir:"C:\Projects\PDE\PRJ... -recursive:false -filter:* -separation:AssemblySeparated -outDir:"C:\Projects\PDE\PR... -outFile:AllInOneReg ......

During a refactoring we searched for full type names in our IoC-config files. The filter was setted to *.xml and Visual Studio does not found all occurrences of the search string in these xml-files.

Setting the filter to *xml without the dot solves this problem – however.

if you see the following warnings in your code: You have two choices: deactivate the rule but this disables this rule for all documentations – also the wanted tune the detail settings In the settings editor you see additional options if you select the “Documentation Rules” root node Normally i want to ignore the warnings for missing private and internal documentations and also for documentation of fields ......

Installing StyleCop for ReSharper under an administrative account does not activate this ReSharper plugin under my developer account. A system analysis show, that this plugin is installed under %userprofile%\Local Settings\Application Data\JetBrains\ReSharper\v4... StyleCop for ReSharper This gives the hint, that the msi must be started for each individual user separately – maybe the is the possibility to move the stuff to all users or that there is also an administrative installation ......

If AgentSmith throws a warning that some term is not spelled correctly for this term the spell checking could be suppressed with: //agentsmith spellcheck disable ... //agentsmith spellcheck enable ......

see also Working with Microsoft FxCop As described in the previous post a custom dictionary could be referenced in a FxCop-call of a target by using the option: /dictionary:&quot;$(Pro... But how is it possible to publish this custom dictionary for the Visual Studio integrated code analysis? This analysis runs an other FxCop.exe than my special FxCop-target. So the custom dictionary which is specified in the FxCop-call of my target is not used. The ...... Run FxCop as a post build event Since FxCop 1.36 it is possible to include FxCop in a post-build event. So FxCop runs after compiling in Visual Studio and allows you directly jumping to the warned line. Description of the command line In the sample above the command line is IF$(ConfigurationName) == Debug $(ProjectDir)..\..\..\..\to... /console /file:"$(TargetPath)" /directory:"$(ProjectDir)..... Interop Assemblies" /directory:"$(ProjectDir)..... ......

Today a colleague ask me to help. On his system all ReSharper menus are grayed out. Also the Visual Studio Add-In Manager does not show this add-in. He tried: a new installation: without success, running with administrative privilegeg: without success, looking in event- and application-logs: no entries. After searching a little bit with old buddy google we found this message: Wild World of Visual Studio -- Mysterious Component We downloaded and installed the latest Microsoft Core XML Services (MSXML) ......

During installation of the SAP .NET Connector the setup throws this error because no Visual Studio 2003 could be found.