Visual Studio 2013
- More than one ServiceInstance were registered to the tool: "{0}". Call the overload of this method that specifies a ServiceInterface ...
- More than one Team Foundation feature that can have IIS sites are on the machine. Use the /siteType option to specify which ...
- More than {2} errors of type '{0}' and sub type '{1}' have occurred; additional errors of this type will not be reported. ...
- Most reference types, including those that override System.Object.Equals, do not override the equality operator (=). Most ...
- Move a Property Sheet : Moves a property sheet one position earlier or later (with respect to its sibling property sheets) ...
- Moves a form by dragging any part of it with the mouse. This feature is particularly useful when the form has no title bar. ...
- Moving a statement which contains a lambda expression will prevent the debug session from continuing while Edit and Continue ...
- Moving a statement which contains a query expression will prevent the debug session from continuing while Edit and Continue ...
- Moving a statement which contains an anonymous method will prevent the debug session from continuing while Edit and Continue ...
- Moving a statement which contains an anonymous type will prevent the debug session from continuing while Edit and Continue ...
- Moving stages is not possible because there's no selected stage or because you're not allowed to place the selected stage ...
- Moving stages is not possible because there's no selected stage or because you're not allowed to place the selected stage ...
- MPI network filter : Specifies the IP addresses from which to accept connections (if chosen above). Ex: 192.168.1.0/255.255.255.0 ...
- MSB1020: The logger was not found. Check the following: 1.) The logger name specified is the same as the name of the logger ...
- MSB1020: The logger {0} was not found. Check the following: 1.) The logger name specified is the same as the name of the ...
- MSB2008: This Visual Studio project system cannot convert "{0}" projects. It can only be used to convert C#, VB, and VJ# ...
- MSB2012: Project-to-project references to web projects are no longer supported and therefore cannot be converted. Please ...
- MSB2013: The project-to-project reference with GUID {0} could not be converted because a valid .SLN file containing all projects ...
- MSB2015: Found an element in the original project file. This cannot be converted to Visual Studio .NET and is being ignored. ...
- MSB3024: Could not copy the file "{0}" to the destination file "{1}", because the destination is a folder instead of a file. ...
- 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 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. ...
- MSB3247: Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning ...
- 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 ...
- MSB3276: Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" ...
- MSB3277: Found conflicts between different versions of the same dependent assembly that could not be resolved. These reference ...
- 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 ...