13

This is what I see:

1>------ Build started: Project: xxx (xxx\xxx), Configuration: Debug Win32 ------
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018: The "VCMessage" task failed unexpectedly.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018: System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018:    at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args)
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018:    at System.String.Format(IFormatProvider provider, String format, Object[] args)
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018:    at Microsoft.Build.Shared.ResourceUtilities.FormatString(String unformatted, Object[] args)
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018:    at Microsoft.Build.Utilities.TaskLoggingHelper.FormatString(String unformatted, Object[] args)
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018:    at Microsoft.Build.Utilities.TaskLoggingHelper.FormatResourceString(String resourceName, Object[] args)
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018:    at Microsoft.Build.Utilities.TaskLoggingHelper.LogErrorWithCodeFromResources(String messageResourceName, Object[] messageArgs)
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018:    at Microsoft.Build.CPPTasks.VCMessage.Execute()
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

and the solutions listed in the google and SO searches don't deliver (removing trailing slashes, reverting to default $(OutDir) or $(TargetDir) paths, etc.)

Context

This regards several projects which have been migrated from MSVC2012. Other projects with the same project/solution layout migrated from the same MSVC2012 environment didn't blink an eye, while some exhibit this error, which prevents any sort of successful compile/build result.

Ger Hobbelt
  • 1,126
  • 1
  • 11
  • 16

3 Answers3

22

The Fix

The error was due to the project configuration field Platform Toolset being empty. (The .vcproj project file should list a value such as v120 here)

Before:

<PlatformToolset>
</PlatformToolset>

After:

<PlatformToolset>v120</PlatformToolset>

This value can be set in DevStudio via project Properties panel > Configuration Properties > General > Platform Toolset :: pick one of the values from the dropdown there.

The way this was uncovered:

  • create an empty new project in MSVC2013 of the same type

  • use Beyond Compare (or another visual diff tool which can easily edit the files being compared by copying chunks across) to copy the files set across and test (by reloading into DevStudio and running the build process in there).

  • next copy across bits of the project settings (and duplicate the blocks if your original project has multiple build targets like mine had (Win32/x64/Itanium)), test again.

  • rinse and repeat the above until your 'new' project exhibits the same issue as the old one. Narrow down to a minimal XML subset in the .vcproj file.

Related SO questions and blogs which were tried before all this:

The conclusion: if you run into this issue, check all your project configuration entries. And when push comes to shove, dig the bugger out by the above compare-and-test divide-and-conquer process.

Community
  • 1
  • 1
Ger Hobbelt
  • 1,126
  • 1
  • 11
  • 16
  • The v120 should be added for each configuration at this location: ... ... v120 ... ... – Or b Mar 08 '21 at 08:15
1

I had the same issue. My problem was I was using values to output file. what I Used was $(TaskName)$(TaskExt) instead of $(TargetName)$(TargetExt)

Correct value could be

In Properties -> Configuration -> Linker

output file = $(SolutionDir)\$(Platform)\$(Configuration)\$(TargetName)$(TargetExt)

Saman
  • 71
  • 1
  • 3
0

In Visual Studio 2013, you get this error when trying to compile a program created in a project with incorrect settings. For me, this happened when I clean up my installation. If you are trying to clear your temporal files and go to C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\layout and execute the program InstallCleanup.exe it seems to delete temporal files but also your settings. In particular the type of project you are creating.

How to reproduce the error:

If you do "New Project" it will display some options 1) Atl 2) CLR 3) General 4) Win 32. You must select Win 32 and then pick Win32 console or Win32 project. By default, it selects something else, then after creating the project you will realize that Properties -> Linker -> System -> Subsystem is empty when it should be /SUBSYSTEM:CONSOLE (or /SUBSYSTEM:WIN32).

After fix this and try to compile it will generate the MSB4018 error.

In summary, the solution is to create again the project and verify that the settings are correctly set as explained.

Gustavo Rodríguez
  • 863
  • 8
  • 11