The "IsFileSystemCaseSensitive" parameter is not supported by the "FindConfigFiles" task

[acshef]

TypeScript Version: 2.3.1

Building Solution from Visual Studio is successful. But my TFS Build Agent fails with the following message:

In project.csproj, I'm telling MSBuild to use <TypeScriptToolsVersion>2.3</TypeScriptToolsVersion> (which is the default that was put in there)

tsconfig.json:

{
    "compileOnSave": true,
    "compilerOptions": {
        "noEmitOnError": true,
        "noImplicitAny": true,
        "noImplicitThis": true,
        "noUnusedLocals": true,
        "pretty": true,
        "removeComments": true,
        "forceConsistentCasingInFileNames": true,
        "target": "ES5"
    },
    "files": [
        "./Scripts/site.ts"
    ],
    "typeRoots": [ "./Scripts/typings" ]
}

And my NuGet packages Microsoft.TypeScript.MSBuild and Microsoft.TypeScript.Compiler are both v2.3.1

Expected behavior:

• Build Agent yields successful build that reflects local build

Actual behavior:

• Error related to Microsoft.TypeScript.targets file, see above

[mhegazy]

@yuit any thoughts here

[jaeeunl]

Same issue

[rposener]

@mhegazy @yuit any updates or work-arounds? VSTS Hosted builds are broken for my team as a result of this.

[yuit]

@rposener @sleepydada @acshef could you guys share the project file ? from the error reported, it seems that the tasks and target get mismatched... also could you share what is installed on VSTS (or TFS in @acshef 's case) hosted build

[chrispat]

@yuit we have VS 2017 15.1 with all components installed on the hosted VMs.

[yuit]

@chrisrpatterson thanks! Would it be possible to see the project file ?

[chrispat]

I don't have access to the project file, I work on VSTS. I was just responded to what we currently have installed on the hosted pool.

[yuit]

For the original issue, I will confirm once I get a proj file but at the moment I have a speculation that the target file is from Nuget which is 2.3 pick up tasks from the build agent which if you are using 2017 15.1 will be 2.1

[chrispat]

@yuit I have a proj file from another customer who is hitting this issue. What is your alias so I can email it to you.

[rainersigwald]

@yuit This definitely looks like a mismatch between the UsingTask and the target that invokes it in the MSBuild. Looks like the UsingTask is older.

You could potentially debug by using the MSBuild preprocessor to see the fully expanded project.

[yuit]

from the proj @chrisrpatterson shared with me offline, I think the issues stems from the fact that project imports Microsoft.TypeScript.target files from local and Nuget (and in the case that @chrisrpatterson shares, the local version is 2.1 and Nuget is 2.3). Tasks in 2.1 don't understand "IsFileSystemCaseSensitive" parameter as we introduce that in 2.3

Possible fix
Remove the local import (or Nuget import which ever one you choose). The lines look something like this:

• local

 <Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\TypeScript\Microsoft.TypeScript.targets" Condition="Exists('$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\TypeScript\Microsoft.TypeScript.targets')" />

• Nuget - should be near the end of the proj file

 <Import Project="..\packages\Microsoft.TypeScript.MSBuild.2.3.1\build\Microsoft.TypeScript.MSBuild.targets" Condition="Exists('..\packages\Microsoft.TypeScript.MSBuild.2.3.1\build\Microsoft.TypeScript.MSBuild.targets')" />

@rainersigwald question - when files with same name imported twice, does MSBuild cache the first import and so the second won't get execute?