MSB3084: Task attempted to find "{0}" in two locations. 1) Under the "{1}" processor specific directory which is generated based on SdkToolsPath 2) The x86 specific directory under "{2}" which is specified by the SDKToolsPath property. You may be able to solve the problem by doing one of the following: 1) Set the "SDKToolsPath" property to the location of the Microsoft Windows SDK.
MSB3042: A namespace or class definition was found within a conditional compilation directive in the file "{0}". This may ...
MSB3071: All drive letters from A: through Z: are currently in use. Since the working directory "{0}" is a UNC path, the ...
MSB3082: Task failed because "{0}" was not found, or the .NET Framework {1} is not installed. Please install the .NET Framework ...
MSB3083: The item "{0}" was specified more than once in the "{1}" parameter and both items had the same value "{2}" for the ...
MSB3084: Task attempted to find "{0}" in two locations. 1) Under the "{1}" processor specific directory which is generated ...
MSB3086: Task could not find "{0}" using the SdkToolsPath "{1}" or the registry key "{2}". Make sure the SdkToolsPath is ...
MSB3087: An incompatible host object was passed into the "{0}" task. The host object for this task must implement the "{1}" ...
MSB3091: Task failed because "{0}" was not found, or the .NET Framework SDK {1} is not installed. The task is looking for ...
MSB3091: Task failed because "{0}" was not found, or the correct Microsoft Windows SDK is not installed. The task is looking ...