Visual Studio 2013

  1. Instrumented application '%2' (Process Id %1) is not logging profile data because a profile monitor is not running, or is ...
  2. Instrumenting this image requires it to run as a 32-bit process. The CLR header flags have been updated to reflect this. ...
  3. Insufficient permissions to write to the specified trace output directory. Use the {0} option to provide an alternate directory ...
  4. Insufficient Permissions. Ensure that you have the following access permissions on the target process: (PROCESS_QUERY_INFORMATION, ...
  5. int, xint (unsigned hex int), uint (unsigned int) int64, xint64, uint64 byte, xbyte, ubyte 2byte, x2byte, u2byte 4byte, x4byte, ...
  6. IntelliSense and browsing information will not be available for C++ projects because the C++ browsing database file %s could ...
  7. IntelliSense might be incorrect as a result. To try the generation again, remove and re-add the reference, or rebuild the ...
  8. IntelliTrace debugging is available only for x86 applications. To enable IntelliTrace debugging, change the platform to x86. ...
  9. IntelliTrace events are collected when you run your application. You can enable or disable collection of IntelliTrace events ...
  10. IntelliTrace is configured to collect data from IIS, but no Web request was intercepted during the test. Verify that the ...
  11. IntelliTrace is not available because another application is profiling on the Web server. Do you want to continue without ...
  12. IntelliTrace is not available because another application is recording IntelliTrace information for the Web server. Do you ...
  13. IntelliTrace is not collecting data for process '{0}' The project type may not be supported or the process you are debugging ...
  14. IntelliTrace is not collecting data for this debugging session. IntelliTrace is not supported when attaching to a process ...
  15. IntelliTrace is not collecting data for this debugging session. The project type may not be supported or the process you ...
  16. IntelliTrace is unable to function properly since the file is locked, try exiting the processes below and launching IntelliTrace. ...
  17. IntelliTrace logs can be opened only with Visual Studio Ultimate. Download Visual Studio Ultimate at the following link: ...
  18. IntelliTrace start application.iTrace /n:mylogger IntelliTrace stop /n:mylogger IntelliTrace launch /f:application.iTrace ...
  19. Interface implementations in augmentations are now deprecated. Interface implementations should be given on the initial declaration ...
  20. InterfaceId' and 'EventsId' parameters for 'Microsoft.VisualBasic.ComClassAttribute' on '|1' cannot have the same value. ...
  21. Interfaces are meant to contain members that specify a set of behaviors. To mark or label a class, use an attribute instead ...
  22. Interfaces cannot contain definitions of concrete members. You may need to define a constructor on your type to indicate ...
  23. Interfaces that are visible to COM should not define overloads, as they will be renamed and cannot be implemented by Visual ...
  24. Intermediate Directory : Specifies a relative path to the intermediate file directory; can include environment variables. ...
  25. INTERNAL ASSEMBLER ERROR (file %s, line %d) Please choose the Technical Support command on the Visual C++ Help menu, or open ...
  26. INTERNAL ASSEMBLER ERROR in '%s' Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical ...
  27. Internal Compiler Error ( 1!8.8x! at address %3!p!): likely culprit is '%2!ls!'. An internal error has occurred in the compiler. ...
  28. INTERNAL COMPILER ERROR (file %s, line %d) Please choose the Technical Support command on the Visual C++ Help menu, or open ...
  29. INTERNAL COMPILER ERROR in '%s' Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical ...
  30. Internal Error - no application limit has been set. Please use the Developer Phone Registration tool to unregister and then ...
  31. Internal Error! {0}.Dispose() for {1} Lock: Out of Order Lock Disposal! (Pre-release = {6}) Reader: Initial: {2}, Now: {3} ...
  32. Internal error. The result provided by unit test extension cannot be opened. Failed to get an instance of the TestClassExtensionAttribute ...
  33. Internet Explorer {0} or higher is required to run load tests using Team Foundation Service. Update your Internet Explorer, ...
  34. Internet Explorer {0} or higher is required to run load tests using Visual Studio Online. Update your Internet Explorer, ...
  35. Interop layer should not be public. The DllImport attribute should not be applied to publicly accessible members (public ...
  36. Interwork ARM and ARM Thumb Calls : Enables generation of thunking code to interwork 16 and 32 bit ARM code. (/QRinterwork-return) ...
  37. Invalid 'TestEnvironment' xml element at index '{0}'. Attribute '{1}' of xml element '{2}' must be present and cannot be ...
  38. Invalid annotation: '%1$ls' property (with byte count) may only be used on values of pointer type: Function '%2$ls' %3$ls. ...
  39. Invalid annotation: '%1$ls' property (with element count) may only be used on values of pointer, array, or reference type: ...
  40. Invalid annotation: 'Null' property may only be used on values of pointer, pointer-to-member, array, or reference type: Function ...
  41. Invalid annotation: 'NullTerminated' property may only be used on buffers whose elements are of integral or pointer type: ...
  42. Invalid anonymous type member declarator. Anonymous type members must be declared with a member assignment, simple name or ...
  43. Invalid ASP.NET Web site '{0}' specified for code coverage instrumentation: {1} The project will be removed from instrumentation ...
  44. Invalid binary file '{0}' specified for code coverage instrumentation: {1} The file will be removed from instrumentation ...
  45. Invalid character in hexadecimal character entity. Hexadecimal character entities must contain digits between '0' and '9', ...
  46. Invalid character(s) in the plugin name. Plugin name can contain only letters, digits, space and the following characters: ...
  47. Invalid class name '{0}'. Types must be in a namespace to be referenced in XAML; they cannot be declared in the global namespace ...
  48. Invalid class name '{0}'. Types must be in a namespace to be referenced in XAML; they cannot be declared in the global namespace. ...
  49. Invalid code coverage item: the specified binary file '{0}' or pdb file '{1}' or key file '{2}' or output directory '{3}' ...
  50. Invalid commit id. Please enter the full 40 character commit id/hash, or 1 or more characters from the beginning of a commit ...
  51. Invalid commit id. Please enter the full 40 character commit id/hash. Valid characters are numbers from 0-9 and letters a-f. ...
  52. Invalid compression info. FileSize="{0}", compressedDataOffset="{1}", compressedSize="{2}", uncompressedSize="{3}", compression="{4}". ...
  53. Invalid compression information: FileSize={0}, compressedDataOffset={1}, compressedSize={2}, uncompressedSize={3}, compression={4} ...
  54. Invalid constraint: the type used for the constraint is sealed, which means the constraint could only be satisfied by at ...
  55. Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like . ...
  56. invalid delegate initializer - expected either '( , Platform::CallbackContext])' or '( , , Platform::CallbackContext , bool])' ...
  57. Invalid file extension value. The file extension cannot exceed 255 characters or contain the characters \ / ? : " > < |. ...
  58. Invalid Ignorable attribute value. Ignorable must contain a space delimited list of prefixes defined by xmlns declarations ...
  59. Invalid key specified for location of instrumentation utility. Exception was thrown: {0}. Reinstalling the application may ...
  60. Invalid layout configuration. The height of '{1}' is set to StretchToContainer with its parent height set to FitToContent ...
  61. Invalid layout configuration. The width of '{1}' is set to StretchToContainer with its parent width set to FitToContent without ...
  62. Invalid member '{0}' on provided type '{1}'. Provided type members must be public, and not be generic, virtual, or abstract. ...
  63. Invalid message queue URL {0} specified for service host {1}. The build machine will not work until this issue has been corrected. ...
  64. Invalid mutation of a constant expression. Consider copying the expression to a mutable local, e.g. 'let mutable x = .'. ...
  65. Invalid object expression. Objects without overrides or interfaces should use the expression form 'new Type(args)' without ...
  66. Invalid Or empty ProgID: %s. ProgIDs must consist of an alpha character (i.e. a-z, A-Z) followed by zero or more of the following ...
  67. Invalid parameter: passing MEM_RELEASE and a non-zero dwSize parameter to '%1$ls' is not allowed. This causes the call to ...
  68. Invalid parameter: passing MEM_RELEASE and MEM_DECOMMIT in conjunction to '%1$ls' is not allowed. This causes the call to ...
  69. Invalid parameters found. Usage: LEViewer.exe /openFile: /TFSUri LEViewer.exe /TFSUri: /environmentUri: /systemUri: LEViewer.exe ...
  70. Invalid ProcessContent attribute value. ProcessContent must contain a space delimited list of prefix qualified names or a ...
  71. Invalid provider '{0}' in connection string entry '{1}' in config file '{2}'. SqlDataConnection can only be used with provider ...
  72. Invalid service or driver admininstration action: %1 (specify one of 'START', 'STOP', 'INSTALL', 'UNINSTALL', or 'AUTOSTART') ...
  73. Invalid target type "%1" for /target: must specify 'exe', 'winexe', 'appcontainerexe', 'library', 'module' or 'winmdobj'. ...
  74. Invalid UITest action filter. Custom Filter category is not of type custom. Custom action filter:{0}, group : {1}, category ...
  75. Invalid UITest action filter. Custom Filter is of reserved group name. Custom action filter :{0}, group : {1}, category : ...