Marko Apfel

MSB3105: Duplicate ressource parameter

Marko Apfel — Mon, 25 Jan 2010 11:17:30 GMT

error MSB3105: The item "BALoginForm.resources" was specified more than once in the "Resources" parameter. Duplicate items are not supported by the "Resources" parameter.

Reason

We use two custom cultures to divide between UIs for two customers. At the machine with this error only one custom culture was installed.

Problem

In production environments by the customers only one custom culture is installed. These installed custom culture we use to set the UI culture.

This lets run us in the problem, that during compile time we need booth custom cultures and during runtime only one custom culture are allowed.

So we must change the logic to evaluate the UI-culture during runtime.

Formatting removable media throws “You do not have sufficient rights to perform this operation.”

Marko Apfel — Thu, 03 Dec 2009 07:49:40 GMT

I tried to format my camera SD-card and my windows comes up with the error:

A little bit google helped:

Starting management console as lokal administrator
Start | Run | Open: runas /user:<LokalAdmin> mmc.exe

Browse to security policy

Pimp the privileges for non administrative users
Open policy “Devices: Allowed to format and eject removable media”
Set value to: “Administrators and Interactive Users”
OK

After logging out and newly logging in formatting is possible.

How to install “SQL Server 2008 Management Studio Express”

Marko Apfel — Tue, 01 Dec 2009 17:06:38 GMT

If you google for “SQL Server 2008 Management Studio Express” you will find a MS resource which downloads a 172MB setup.

But this setup does not offer a separate “SQL Server 2008 Management Studio Express” option. Why ever.

So i startet a new search and i found this solution:

Download & install the web platform installer http://www.microsoft.com/web/Downloads/platform.aspx

Start the installer

and use the “customize” link in the Database section to activate “SQL Server 2008 Management Studio Express” option

MSBuild Exec task: using quotes in WorkingDirectory does not work

Marko Apfel — Fri, 27 Nov 2009 16:01:45 GMT

For a general applicability i tried to specify the WorkingDirectory attribute in a qotted manner:


<WorkingDir>&quot;$(SolutionRoot)\EsriDE.Commons\tools\EsriDE\&quot;</WorkingDir>


<DoubleQuotes>%22</DoubleQuotes>
<WorkingDir>$(DoubleQuotes)$(SolutionRoot)\EsriDE.Commons\tools\EsriDE\$(DoubleQuotes)</WorkingDir>

The Exec task self is


<Exec
  WorkingDirectory="$(WorkingDir)"
  Command="$(ExtractComCategories) $(InputDirectoryArg) $(FilterArg) $(SeparationArg) $(OutputDirectoryArg) $(OutputFileArg) $(OutputFormatArg)" />

Every variant throws during building the exception MSB6003 (The directory name is invalid):


"E:\builds\RXXXXX_Sourcecode\APF_Evaluation\BuildType\..\Sources\EsriDE.Commons\tools\EsriDE\EsriDE.Utilities.Build.Com.ComCategoryExtractor.exe"
-inDir:"E:\builds\RXXXXX_Sourcecode\APF_Evaluation\Binaries\Debug" -filter:* -separation:AssemblySeparated
-outDir:"E:\builds\RXXXXX_Sourcecode\APF_Evaluation\Binaries\Debug" -outFile:AllInOneReg -outFormat:RegistryFile
E:\builds\RXXXXX_Sourcecode\APF_Evaluation\BuildType\TFSBuild.proj(70,3):
error MSB6003: The specified task executable could not be run.

The directory name is invalid

I have no idea for a solution. Now the WorkingDirectory is not quoted.

Visual Studio 2005/2008 Code Analysis Error

Marko Apfel — Thu, 26 Nov 2009 18:52:58 GMT

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\VisualStudio\v8.0\CodeAnalysis\Microsoft.CodeAnalysis.targets(46,4):
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 Edition for Software Developers or Visual Studio Team Suite is installed 
and run MSBuild from within the "Visual Studio Command Prompt" 
or specify the path to FxCop by setting the FXCOPDIR environment variable.

Specifying the FXCOPDIR-variable brings up the next obscure errors.

Replacing the VS2005 CodeAnalysis targets with the VS2008 targets lets run everything fine.

So replace [dont forget to make a backup ;-)]

C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\CodeAnalysis

with

C:\Program Files\MSBuild\Microsoft\VisualStudio\v9.0\CodeAnalysis

But now you get an error in Visual Studio 2005:


MSBUILD : error : Invalid settings passed to CodeAnalysis task. See output window for details.
Code Analysis Complete -- 1 error(s), 0 warning(s)

Setting the build output information to diagnostic you get an good hint what the problem is.

So we edit as the last step the VS2005 target:

the line

<UsingTask TaskName="Microsoft.Build.Tasks.CodeAnalysis" AssemblyFile=".\FxCopTask.dll"/>

we modify to:

<UsingTask TaskName="Microsoft.Build.Tasks.CodeAnalysis" AssemblyFile="..\..\v9.0\CodeAnalysis\FxCopTask.dll"/>

and the following lines

<CodeAnalysisPath Condition="'$(CodeAnalysisPath)'=='' and '$(FxCopDir)'!='' and '$(TeamBuildConstants)'==''">$(FxCopDir)</CodeAnalysisPath>
<CodeAnalysisPath Condition="'$(CodeAnalysisPath)'=='' and '$(VSINSTALLDIR)'!=''">$(VSINSTALLDIR)\Team Tools\Static Analysis Tools\FxCop</CodeAnalysisPath>

are replaced with

<CodeAnalysisPath>C:\Program Files\Microsoft Visual Studio 9.0\Team Tools\Static Analysis Tools\FxCop</CodeAnalysisPath>

not beautiful – but working!

Stopping a build at the TFS

Marko Apfel — Thu, 26 Nov 2009 13:54:43 GMT

Open a “visual studio command prompt” and try:

     tfsbuild stop https://*****:8143 RXXXXX_Sourcecode Gen_2.6_branch_test_20080827.1

Parsing argument line with a folder-parameter ending with backslash

Marko Apfel — Wed, 25 Nov 2009 11:21:11 GMT

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_Common\trunk\code\Commons\bin\Debug\") the ending backslash makes troubles.

My whole argument line (linebreaked for better viewing):

     -inDir:"C:\Projects\PDE\PRJ_EsriDE_Common\trunk\code\Commons\bin\Debug\"

    -recursive:false

    -filter:*

    -separation:AssemblySeparated

    -outDir:"C:\Projects\PDE\PRJ_EsriDE_Common\trunk\code\Commons\bin\Debug\"

    -outFile:AllInOneReg

    -outFormat:RegistryFile

is wrongly splitted to:

The following variant without a ending backslash:

    -inDir:"C:\Projects\PDE\PRJ_EsriDE_Common\trunk\code\Commons\bin\Debug"

    -recursive:false

    -filter:*

    -separation:AssemblySeparated

    -outDir:"C:\Projects\PDE\PRJ_EsriDE_Common\trunk\code\Commons\bin\Debug"

    -outFile:AllInOneReg

    -outFormat:RegistryFile

is no problem:

and also the forward slashes:

    -inDir:"C:/Projects/PDE/PRJ_EsriDE_Common/trunk/code/Commons/bin/Debug/"

    -recursive:false

    -filter:*

    -separation:AssemblySeparated

    -outDir:"C:/Projects/PDE/PRJ_EsriDE_Common/trunk/code/Commons/bin/Debug/"

    -outFile:AllInOneReg

    -outFormat:RegistryFile

works in both variants (with and without an ending one):

Visual Studio: Find in files with *.xml wildcard does not find all occurrences

Marko Apfel — Tue, 17 Nov 2009 10:51:52 GMT

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.

StyleCop throws documentation warning SA1600 for private elements

Marko Apfel — Thu, 12 Nov 2009 12:24:57 GMT

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

Marko Apfel — Thu, 12 Nov 2009 11:58:01 GMT

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.5\vs9.0\Plugins\Microsoft 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 possible.

AgentSmith: suppressing spell checking warnings

Marko Apfel — Thu, 12 Nov 2009 09:42:32 GMT

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

Using a custom dictionary in code analysis

Marko Apfel — Wed, 11 Nov 2009 15:22:08 GMT

Working with Microsoft FxCop

Marko Apfel — Wed, 11 Nov 2009 15:06:56 GMT

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)..\..\..\..\tools\FxCop\FxCopCmd.exe

/console

/file:"$(TargetPath)"

/directory:"$(ProjectDir)..\..\..\..\lib\Primary Interop Assemblies"

/directory:"$(ProjectDir)..\..\..\..\lib\ArcGIS\9.2.0.1324"

/dictionary:"$(ProjectDir)..\..\..\CustomDictionary.xml"

Parameter	Description
/console	Outputs messages to console, including file and line number information.
/file	Assembly file to analyze. $(TargetPath) is a makro-variable of Visual Studio which points to the compilation. Wrap it in quotations to avoid problems with spaces in path names.
/directory	Location to search for assembly dependencies. This parametes could occurs multiple times. $(ProjectDir) is a makro-variable of Visual Studio which points to the *.csproj-file of the project.
/dictionary	Custom dictionary to allows own abbreviations and own words for syntax checking.

Integration as a build target

Integration as an own target

Instead running FxCop as a post build event the using of build targets is a good and since using of Hudson the recommended way.

In the csproj file therefore a new target must included. You could name it De.Esri.FxCop.targets for instance.

Place the call of this target beneath the normal build target.

<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
<Import Project="..\De.Esri.FxCop.targets" />

And now we need this target. Important is the FxCopCmd-call. Therefore we use the Exec tag.

The whole call must made in one line. Only for documentation purposes every option has a own line.

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <PropertyGroup>
        <BuildDependsOn>$(BuildDependsOn);FxCop</BuildDependsOn>
        <RebuildDependsOn>$(RebuildDependsOn);FxCop</RebuildDependsOn>
    </PropertyGroup>
 
    <ItemGroup>
        <CodeAnalysisDictionary Include="&quot;$(ProjectDir)..\FxCop.CustomDictionary.xml&quot;" />
    </ItemGroup>
    
    <Target Name="FxCop">
        <Exec Command="..\..\tools\FxCop\FxCopCmd.exe 
              /file:&quot;$(TargetPath)&quot; 
              /dictionary:&quot;$(ProjectDir)..\FxCop.CustomDictionary.xml&quot; 
              /out:&quot;$(OutDir)..\$(ProjectName).FxCopReport.xml&quot; 
              /console /forceoutput"
           WorkingDirectory="..\..\tools\FxCop\" ></Exec>
        <Message Text="FxCop finished." />
    </Target>
</Project>

Because the filesystem ressource parameters could contain spaces (e.g. )Program Files) these parameters must be quoted. Thats why we need the cryptical " there.

Integration as a MSBuild-Community target

John Rayner's Blog

Complex build script run FxCop:

Integrating FxCop into CruiseControl.NET

ReSharper is not available

Marko Apfel — Mon, 09 Nov 2009 13:23:27 GMT

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) 6.0 Service Pack 1 and ReSharper works fine. :-)

The colleague remembered that he uninstalled SQL Server 2005 – and for this MSXML6 is a installation feature – so a full deinstallation removes MSXML6 also. :-(

SQL Server 2005 Zugriffsproblem bei Remotezugriff

Marko Apfel — Thu, 23 Feb 2006 21:15:00 GMT

Wenn ein Remote-Zugriff auf einen SQL Server 2005 mit der Fehlermeldung

"A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections."

scheitert, dann hilft folgendes

Öffnen der SQL Server Surface Area Configuration
Anwählen von "Surface Area Configuration for Services and Connections"
Unter "MSSQLSERVER > Database Engine > Remote" den Zugriff auf "Local and remote connections" mit Unterpunkt "Using both TCP/IP and named pipes" setzen
SQL Server neu starten