Unsupported Script Variable

[livarcocc]

From @mbaird628 on August 20, 2018 16:5

Steps to reproduce

dotnet migrate of .xproj to csproj

Expected behavior

Successful conversion

Actual behavior

Failed conversion with following message

"MIGRATE1016::Unsupported Script Variable: compile:CompilerExitCode is currently an unsupported script variable for project migration"
After removing the "postcompile" variable the migration was successful.

{
"version": "1.0.0-*",

"dependencies": {
"Ecolab.IoT.DeviceManagement.Resources": "1.0.0-*",
"Microsoft.AspNetCore.Mvc.DataAnnotations": "1.1.0",
"Microsoft.AspNetCore.Mvc.ViewFeatures": "1.0.1",
"Microsoft.Hadoop.Avro": "1.5.6",
"NETStandard.Library": "1.6.1",
"Newtonsoft.Json": "9.0.1",
"System.ComponentModel.Annotations": "4.0.0"
},
"frameworks": {
"net452": {
"frameworkAssemblies": {
"System.Runtime.Serialization": "4.0.0.0"
},
"buildOptions": {
"define": [ "CODE_ANALYSIS" ]
}
}
},
"scripts": {
"postcompile": "../ExecuteCodeAnalysis.cmd %compile:TargetFramework% %compile:Configuration% %compile:OutputFile% %compile:CompilerExitCode%"
}
}

Environment data

dotnet --info output:

Product Information:
Version: 2.1.104

Commit SHA-1 hash: 48ec687460

Runtime Environment:
OS Name: Windows
OS Version: 10.0.16299
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.104\

Microsoft .NET Core Shared Framework Host

Version : 2.0.6
Build : 74b1c703813c8910df5b96f304b0f2b78cdf194d

Copied from original issue: dotnet/cli#9867