Visual Studio 2012
- 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 correct Microsoft Windows SDK is not installed. The task is looking ...
- MSB3104: The referenced assembly "{0}" was not found. If this assembly is produced by another one of your projects, please ...
- MSB3105: The item "{0}" was specified more than once in the "{1}" parameter. Duplicate items are not supported by the "{1}" ...
- MSB3106: Assembly strong name "{0}" is either a path which could not be found or it is a full assembly name which is badly ...
- MSB3116: Application is marked to host in browser but is also marked for online and offline use. Please change your application ...
- MSB3121: The file association element in the application manifest is missing one or more of the following required attributes: ...
- MSB3126: The application is using file associations but is not marked for installation. File associations cannot be used ...
- MSB3127: The default icon {0} could not be found in the current file references or is not part of the required download group. ...
- MSB3133: The ExcludePermissions property is deprecated. The permission set requested by the application has been set to the ...
- MSB3134: The permission set requested by the application exceeded the permissions allowed by the Internet or Intranet zones. ...
- MSB3135: The PermissionSet for the target zone has not been defined for the following version of the .NET Framework: {0}. ...
- MSB3144: Not enough data was provided to generate a bootstrapper. Please provide a value for at least one of the parameters: ...
- MSB3152: To enable 'Download prerequisites from the same location as my application' in the Prerequisites dialog box, you ...
- MSB3162: The '{0}' item selected requires '{1}'. Select the missing prerequisite in the Prerequisites Dialog Box or create ...
- MSB3163: Build input parameter 'ComponentsLocation={0}' is not valid. The value must be one of 'HomeSite', 'Relative', or ...
- MSB3164: No 'HomeSite' attribute has been provided for '{0}', so the package will be published to the same location as the ...
- MSB3176: Specified minimum required version is greater than the current publish version. Please specify a version less than ...
- MSB3204: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project ...
- MSB3216: Cannot register assembly "{0}" - access denied. Please make sure you're running the application as administrator. ...
- MSB3245: Could not resolve this reference. {0} If this reference is required by your code, you may get compilation errors. ...
- MSB3250: The file "{0}" will be ignored because it cannot be read. This file was either passed in to InstalledAssemblyTables ...
- MSB3251: Could not resolve assembly {0}. The target framework required by this assembly ({1}) is higher than the project ...
- MSB3252: The currently targeted framework "{1}" does not include the referenced assembly "{0}". To fix this, either (1) change ...
- MSB3253: The currently targeted framework "{2}" does not include "{1}" which the referenced assembly "{0}" depends on. This ...
- MSB3254: The file "{0}" will be ignored because it cannot be read. This file was either passed in to InstalledAssemblySubsetTables ...
- MSB3255: Could not find any Target Framework Subset files in the Target Framework Directories or at the locations specified ...
- MSB3256: No assemblies were read in from the redist lists. A TargetFramework profile exclusion list could not be generated. ...
- MSB3257: The primary reference "{0}" could not be resolved because it has a higher version "{1}" than exists in the current ...
- MSB3258: The primary reference "{0}" could not be resolved because it has an indirect dependency on the .NET Framework assembly ...
- MSB3259: Invalid parameter combination. Can only set either subset or profile parameters. Cannot set one or more subset parameters ...
- MSB3261: The FrameworkDirectory metadata must be set on all items passed to the FullFrameworkAssemblyTables parameter. The ...
- MSB3262: When targeting a profile the ProfileName parameter and one of FullFrameworkFolders or FullFrameworkAssemblyTables ...
- MSB3263: The file "{0}" will be ignored because it cannot be read. This file was either passed in to FullFrameworkAssemblyTables ...
- MSB3267: The primary reference "{0}", which is a framework assembly, could not be resolved in the currently targeted framework. ...
- MSB3268: The primary reference "{0}" could not be resolved because it has an indirect dependency on the framework assembly ...
- MSB3270: There was a mismatch between the processor architecture of the project being built "{0}" and the processor architecture ...
- MSB3271: There was a mismatch between the processor architecture of the project being built "{0}" and the processor architecture, ...
- MSB3273: Unknown processor architecture. The implementation file "{0}" for "{1}" had an ImageFileMachine value of "0x{2}". ...
- MSB3274: The primary reference "{0}" could not be resolved because it was built against the "{1}" framework. This is a higher ...
- MSB3275: The primary reference "{0}" could not be resolved because it has an indirect dependency on the assembly "{1}" which ...
- MSB3283: Cannot find wrapper assembly for type library "{0}". Verify that (1) the COM component is registered correctly and ...
- MSB3288: COM reference "{0}" conflicts with reference "{1}" - the project references different type libraries with the same ...
- MSB3291: Could not resolve dependent .NET assembly "{0}". Please make sure this assembly is included in the references section ...
- MSB3295: Failed to load an assembly. Please make sure you have disabled strong name verification for your public key if you ...
- MSB3325: Cannot import the following key file: {0}. The key file may be password protected. To correct this, try to import ...
- MSB3326: Cannot import the following key file: {0}. The key file may be password protected. To correct this, try to import ...
- MSB3392: Cannot unregister assembly "{0}" - access denied. Please make sure you're running the application as administrator. ...
- MSB3452: StronglyTypedClassName, StronglyTypedNamespace, and/or StronglyTypedFileName parameters were passed in, but no StronglyTypedLanguage. ...
- MSB3453: The language for a strongly typed resource class was specified, but more than one source file was passed in. Please ...
- MSB3454: Tracker.exe is required to correctly incrementally generate resources in some circumstances, such as when building ...
- MSB3455: ResGen.exe may not run because the command line is {0} characters long, which exceeds the maximum length of the ...
- MSB3572: StronglyTypedClassName, StronglyTypedNamespace, and/or StronglyTypedFileName parameters were passed in, but no StronglyTypedLanguage. ...
- MSB3573: The language for a strongly typed resource class was specified, but more than one source file was passed in. Please ...
- MSB3576: Creating the CultureInfo failed for assembly "{2}". Note the set of cultures supported is Operating System-dependent, ...
- MSB3578: This assembly contains neutral resources corresponding to the culture "{0}". These resources will not be considered ...
- MSB3580: The assembly in file "{0}" has an assembly culture, indicating it is a satellite assembly for culture "{1}". But ...
- MSB3644: The reference assemblies for framework "{0}" were not found. To resolve this, install the SDK or Targeting Pack ...
- MSB3645: .NET Framework v3.5 Service Pack 1 was not found. In order to target "{0}", .NET Framework v3.5 Service Pack 1 or ...
- MSB3654: Delay signing requires that at least a public key be specified. Please either supply a public key using the KeyFile ...
- MSB3676: Could not move the file "{0}" to the destination file "{1}", because the destination is a folder instead of a file. ...
- MSB3689: Unable to execute Xaml task. If the CommandLineTemplate task parameter is not specified, then the ToolName attribute ...
- MSB3753: The task could not be instantiated because it does not implement the ITask interface. Make sure the task implements ...
- MSB3757: Multiple Code xml elements have been found, this is not allowed. To fix this issue remove any additional Code xml ...
- MSB3773: The SDK "{0}" cannot be referenced alongside SDK(s) {1}, as they all belong to the same SDK product Family "{2}". ...
- MSB3776: The SDK Reference "{0}" is incorrectly formatted. It must be in the following format " , Version= . For example: ...
- MSB3776: The SDK Reference "{0}" is incorrectly formatted. It must be in the following format " , Version= . For example: ...
- MSB3777: "FrameworkIdentity" attributes were found in the SDK manifest file "{0}", however none of the attributes matched ...
- MSB3778: "APPX" attributes were found in the SDK manifest file "{0}" however none of the attributes matched the targeted ...
- MSB3779: The processor architecture of the project being built "{0}" is not supported by the referenced SDK "{1}". Please ...
- MSB3780: The SDK "{0}" cannot be referenced alongside SDK(s) {1}, because only one version of the SDK can be referenced from ...