Visual Studio 2012

  1. ls': Annotation operands must be integer/enum/pointer types. Void operands and C++ overloaded operators are not supported. ...
  2. Macro '%s' contains characters that are not supported by msbuild and the conversion can't create the new msbuild elements ...
  3. Macros such as RFX_Text() and RFX_Int() are dependent on the type of the member variable, not the type of the field in the ...
  4. Main query of the target table ({0}) uses a different database object than the dropped object and cannot be changed automatically. ...
  5. Make requests on your behalf to access all private resources (project, version control items, builds, etc.) within the ({0}) ...
  6. Make sure that the configuration editor for the following diagnostic data adapter is installed in the correct location: {0}. ...
  7. Make sure the lab service account has read permissions on the build drop location, in order to run tests and deployment workflows ...
  8. Make sure the password matches and is strong. The password must be at least eight characters long, contain at least one uppercase ...
  9. Make sure the server is operating correctly. Verify there are no syntax errors in web.config by doing a Debug.Start Without ...
  10. Make sure you are not trying to unload an application domain that is the default domain, has a running thread, or is already ...
  11. Make {0} non-private, mark it as final, or seal its declaring type. This method was originally defined in base class {1}. ...
  12. Make {0} sealed (a breaking change if this class has previously shipped), implement the method non-explicitly, or implement ...
  13. Makes the local file writable and changes its pending Change status to "edit" in the workspace. Edit is an alias for the ...
  14. Making the selected element into a UserControl might result in broken references in the new UserControl and/or broken references ...
  15. Managed code profiling component was not registered - fixing. This session may not have correct results for managed/mixed ...
  16. Managed threads are consuming {0:0.00%} of the CPU. Go the Performance Warnings menu in the navigation toolbar and select ...
  17. Manifest File : Specifies the name of the manifest file to generate. Only used if Generate Manifest is true. (/MANIFESTFILE:[file]) ...
  18. Many cached textures are composed together in frames during this time range and average fill rate is {0}. Go to the Performance ...
  19. Many-to-many associations are read-only, therefore the EntityCollections on both ends of the association are not editable. ...
  20. Maps a team project collection to a PWA instance. The PWA instance must be registered before mapping the collection to it. ...
  21. Mark interface {0} as InterfaceType(ComInterfaceType.InterfaceIsIDispatch) because it is specified in the ComSourceInterfaces ...
  22. Mark package scope as assembly scope in metadata. Package-scoped items are public by default. (/securescoping[+|- or /ss[+|-]) ...
  23. Marking all methods '_declspec(noinline)' prevents the warning. Changing the static constructor to an explicitly called static ...
  24. Marks an executable as having been tested to be compatible with Windows Data Execution Prevention feature. (/NXCOMPAT[:NO]) ...
  25. Marshaling Session or Host object to secondary AppDomain failed. Check that Host and all types in Session dictionary are ...
  26. Mask : The mask string specifies what type of characters can be written and where. Possible mask symbols: 'a', 'A', 'c', ...
  27. Matching symbols could not be found. Choose the Symbol Settings ' link to add the symbol file location and then reload the ...
  28. Max Cached Translation Units : The maximum number of translation units that will be kept active at a time for IntelliSense ...
  29. Maximum concurrent C++ compilations : The maximum number of CPU cores to use for parallel C++ compilation. A value of 0 causes ...
  30. Maximum height used for composing this visual across the selection. If the texture count is 1 for selection, the same texture ...
  31. Maximum number of profiled processes exceeded. Some data may have been lost. Check the MaxProcesses setting in the registry. ...
  32. Maximum packet length exceeded. If the problem continues, reduce the number of network host names or network addresses that ...
  33. Maximum width used for composing this visual across the selection. If the texture count is 1 for selection, the same texture ...
  34. MC1001: The LocalizationDirectivesToLocFile property value is not valid and must be changed to None, CommentsOnly, or All ...
  35. MC3001: TypeConverter syntax error encountered while processing initialization string '{0}'. Property elements are not allowed ...
  36. MC3010: '{0}' Name property value is not valid. Name must start with a letter or an underscore and can contain only letters, ...
  37. MC3014: The object being added to an array property is not a valid type. The array is of type '{0}' but the object being ...
  38. MC3016: Two new namespaces cannot be compatible with the same old namespace using an XmlnsCompatibility attribute. '{0}' ...
  39. MC3020: The dictionary key '{0}' is already used. Key attributes are used as keys when inserting objects into a dictionary ...
  40. MC3041: Markup extensions require a single '=' between name and value, and a single ',' between constructor parameters and ...
  41. MC3042: Name/value pairs in MarkupExtensions must have the format 'Name = Value' and each pair is separated by a comma. '{0}' ...
  42. MC3046: Unknown attribute '{0}' in the '{1}' namespace. Note that only the Key attribute is currently supported in this namespace. ...
  43. MC3048: '{0}' value is not a valid MarkupExtension expression. Cannot resolve '{1}' in namespace '{2}'. '{1}' must be a subclass ...
  44. MC3054: The type '{0}' cannot have a Name attribute. Value types and types without a default constructor can be used as items ...
  45. MC3077: The class '{0}' does not implement IXmlLineInfo. This is required to get position information for the XAML being ...
  46. MC3081: '{0}' is a read-only property of type IList or IDictionary and cannot be set because it does not have a public or ...
  47. MC3082: '{0}' cannot be set as the value of a Trigger's Property attribute because it does not have a public or internal ...
  48. MC3083: Cannot access the delegate type '{0}' for the '{1}' event. '{0}' has incorrect access level or its assembly does ...
  49. MC3086: Parent element or property '{0}' requires an XML data island. To distinguish an XML island from surrounding XAML, ...
  50. MC3087: Cannot set content property '{0}' on element '{1}'. '{0}' has incorrect access level or its assembly does not allow ...
  51. MC3090: TypeConverter syntax error encountered while processing initialization string '{0}'. Element attributes are not allowed ...
  52. MC3091: '{0}' is not valid. Markup extensions require only spaces between the markup extension name and the first parameter. ...
  53. MC3093: Cannot set Name attribute value '{0}' on element '{1}'. '{1}' is under the scope of element '{2}', which already ...
  54. MC4003: Cannot resolve the Style {0} '{1}'. Verify that the owning type is the Style's TargetType, or use Class.Property ...
  55. MC4104: The property '{0}' cannot be set as a property element on template. Only Triggers and Storyboards are allowed as ...
  56. MC4106: Cannot resolve the Template Property '{0}'. Verify that the owning type is the Style's TargetType, or use Class.Property ...
  57. MC4108: The root of a Template content section cannot contain an element of type '{0}'. Only FrameworkElement and FrameworkContentElement ...
  58. MC4111: Cannot find the Trigger target '{0}'. (The target must appear before any Setters, Triggers, or Conditions that use ...
  59. MC4610: '{0}' element is not a valid child of AlternateContent. Only Choice and Fallback elements are valid children of an ...
  60. MC4640: Namespace '{0}' is marked as compatible with itself using XmlnsCompatibilityAttribute. A namespace cannot directly ...
  61. MC6002: Unrecognized tag '{0}:{1}' in namespace 'http://schemas.microsoft.com/winfx/2006/xaml'. Note that tag names are case ...
  62. MC6005: {0}="{1}" is not valid. '{1}' is not a valid event handler method name. Only instance methods on the generated or ...
  63. MC6006: {0}.{1}="{2}" is not valid. '{1}' must be a RoutedEvent registered with a name that ends with the keyword "Event". ...
  64. MC6009: {0}:ClassModifier attribute cannot be specified on the root tag because a {0}:Class attribute is also required. Either ...
  65. MC6011: '{0}' event has a generic event handler delegate type '{1}'. The type parameters of '{1}' cannot be bound with an ...
  66. MC6012: '{0}' event has a generic event handler delegate type '{1}'. The type parameter '{2}' on '{1}' does not match any ...
  67. MC6020: {0}:TypeArguments='{1}' is not valid on the tag '{2}'. Either '{2}' is not a generic type or the number of Type arguments ...
  68. MC6021: {0}:FieldModifier cannot be specified on this tag because it has either no {0}:Name or Name attribute set, or the ...
  69. MC6023: Because '{0}' is implemented in the same assembly, you must set the {1}:Name attribute rather than the Name attribute. ...
  70. MC6024: '{0}' root element requires a {1}:Class attribute to support event handlers in the XAML file. Either remove the event ...
  71. MC6025: '{0}' root element is a generic type and requires a {1}:Class attribute to support the {1}:TypeArguments attribute ...
  72. MC6026: '{0}' root element requires a {1}:Class attribute because '{2}' contains a {1}:Code tag. Either remove {1}:Code and ...
  73. MC6028: {0}:TypeArguments="{1}" is not valid. '{2}' is not a valid type name reference for the generic argument at position ...
  74. MC6031: {0}:FieldModifier attribute cannot be specified because a {0}:Class attribute is also required to generate a Name ...
  75. Me keyword Provides a way to refer to the current instance of a class or structure, that is, the instance in which the code ...