search

fsprojects / ProjectScaffold

A prototypical .NET solution (file system layout and tooling), recommended for F# projects
http://fsprojects.github.io/ProjectScaffold
The Unlicense
515 stars 153 forks source link

ArgumentException when running build.cmd #110

Closed Slesa closed 7 years ago

Slesa commented 9 years ago

Running for the first time in this directory, build.cmd reports 'build process successful, 0 errors, 0 warnings' Starting target RunTests. ... D:\dev\github\Poseidon.new\packages\NUnit.Runners\tools\nunit-console.exe "-nologo" "-noshadow" "-labels" "D:\dev\github\Poseidon.new\tests\Poseidon.Tests\bin\Release\Poseidon.Tests.dll" "-xml:TestResults.xml" ProcessModel: Default DomainUsage: Single Execution Runtime: net-3.5 Unhandled Exception: System.ArgumentException: Das Element wurde bereits hinzugefügt. Schlüssel im Wörterbuch: "tmp". Hinzuzufügender Schlüssel: "tmp".

(key 'tmp' already added to dictionary)

Maybe to mention: I started build.cmd under a cygwin bash shell.

pblasucci commented 9 years ago

Out of curiosity, what happens if you use build.sh from Cygwin? Alternatively, what if you run build.cmd from CommandPrompt.exe?

Slesa commented 9 years ago

Oh, that's interesting indeed - yesterday I started a cmd from the bash itself, and everything was exactly as mentioned above. So I thought - ok, that's the message. Starting the cmd.exe without the bash in the background, everything is ok.

Starting build.sh in cygwin produces the same error.

dsyme commented 7 years ago

Very old issue, please reopen if it is still a problem