Visual Studio 2013

  1. Visual Studio will automatically keep you signed in, sync your settings between devices, and connect to online developer ...
  2. Visual Studio will automatically make functional changes to the following projects in order to open them. The project behavior ...
  3. Visual Studio will automatically make functional changes to the following projects in order to open them. You will not be ...
  4. Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in ...
  5. Visual Studio will download the required information for the packages to be uploaded to the Store. The packages can also ...
  6. Visual Studio will download the required information for the packages to be uploaded to the Store. The packages can also ...
  7. Visual Studio will download the required information for the packages to be uploaded to the Windows Phone Store. The packages ...
  8. Visual Studio will upgrade workflows from the specified file into a new SharePoint workflow project. The new workflow project ...
  9. Visual Web Developer Express Edition - ENU (English) must be installed before a Visual Web Developer Express Edition language ...
  10. Visual Web Developer Express Edition - ENU must be installed before a Visual Web Developer Express Edition language pack ...
  11. Visual {0} is cached as part of visual {1}. Animating visual {0} will cause the cache to be invalidated. To identify cache ...
  12. Visual {0} is cached using BitmapCache and is also animated by storyboard {1}. This storyboard is CPU-bound and is causing ...
  13. Visuals {0} and {1} are both cached. {0} is updated in the current selection. This causes recomputation of the cache. Visual ...
  14. VS1010: Visual Studio cannot import the selected file. It is not a compatible prototype file. Select a compatible prototype ...
  15. VS1011: Cannot find the prototype file for this toolbox item: {0}. To fix this condition, drag the toolbox item to the diagram, ...
  16. VS1032: The reference string provided does not have the correct format. The correct format is backplane://backplaneId/se ...
  17. VS1035: The ServiceManager is not correctly registered with a backplane. Confirm the ServiceManager is registered with a ...
  18. VS1040: Visual Studio cannot find the ProjectItems collection in the solution. If the problem persists, contact the author ...
  19. VS1041: The integration tool could not initialize the solution scope because of the scope context is not valid. The CreateProject ...
  20. VS1042: The integration tool could not initialize the solution scope because more than one of the three members (CreateProject, ...
  21. VS1043: Visual Studio cannot add an instance of the following .vstemplate file: {0}. Confirm that the file is a valid .vstemplate. ...
  22. VS1044: The integration tool cannot convert the scope object to the specified type: {0}. Provide a scope object of the specified ...
  23. VS1047: The full path of the .vstemplate file is null or empty. An instance of the following service type should provide ...
  24. VS1048: ISequenceService cannot add the following lifeline: {0}. Use the ISequenceService.IsLifelineNameAvailable method ...
  25. VS1051: ISequenceService enables you to call the following method only within the scope of a transaction: {0}. Make sure ...
  26. VS1140:The integration tool encountered an error when it executed the command. For more information, see the inner exception ...
  27. VS1141:The integration tool encountered an error when it executed a transacted command, because there is no available TransactionManager. ...
  28. VS1142: The CommandManager is not correctly registered with a backplane. Confirm the CommandManager is registered with a ...
  29. VS1168: You cannot set the existing CommandManager as the predecessor of the new CommandManager because it will create a ...
  30. VS1170: The CommandManager is already registered with a backplane. Unregister the CommandManager from its backplane and register ...
  31. VS1171: The existing CommandManager cannot be set as the predecessor of the new CommandManager because the new CommandManager ...
  32. VS1213: The activity final node shape cannot have multiple incoming flows. Change the diagram so that there is only a single ...
  33. VS1214: The initial node shape cannot have multiple outgoing flows. Change the diagram so that there is only a single outgoing ...
  34. VS1237: The identifier name is not valid. The identifier name must: - Not be an empty string - Start with an alphabetic character ...
  35. VS1290: The backplane configuration file is either missing, corrupted, or not valid and must be repaired. Otherwise, integrations ...
  36. VS1292: The following namespace is not valid: {0}. Provide a valid namespace that consists of identifiers and uses the following ...
  37. VS1293: The following type is not valid: {0}. The type must: - Start with an alphabetic character or '_' - Consist of alpha-numeric ...
  38. VS1705: The model store has become corrupted because one or multiple elements in the store have more than one definition ...
  39. VS1706: The following profile cannot be loaded because it is either corrupted, not the correct profile, or a duplicate: {0} ...
  40. VS1716: Cannot generate a sequence diagram due to the following possible reasons: A method is not selected. To generate from ...
  41. VS1723: Modeling projects based on this project template must be saved when you create them. Perform either of the following ...
  42. VS1726: Cannot list all the linked work items because you are not connected to the following Team Foundation Servers: {0}. ...
  43. VS1729: There is not enough memory to finish generating the diagram. Try using a smaller call depth or more restrictive filters. ...
  44. VsGraphics /export: /compress: /generatepremultipliedalpha /generatemips /script: /console input_file You must specify a ...
  45. VSLG1001: Logger name '{0}' is not valid. Logger name must contain only letters, number, period(.), dash (-) or underscore ...
  46. VSLG1012: Unable to create event '{0}'. Another logger with the same name might be running, or the object name might be in ...
  47. VSLG4004: TracelogProfiler.dll is not registered; historical data may fail to record. Use 'regsvr32 TracelogProfiler.dll' ...
  48. VSLG4004: TracelogProfiler.dll is not registered; IntelliTrace may fail to record data. Use 'regsvr32 TracelogProfiler.dll' ...
  49. VSLG4005: 32-bit TracelogProfiler.dll is not registered; historical data may fail to record for 32-bit processes. Use 'regsvr32 ...
  50. VSLG4005: 32-bit TracelogProfiler.dll is not registered; IntelliTrace may fail to record data for 32-bit processes. Use 'regsvr32 ...
  51. VSLG4006: 64-bit TracelogProfiler.dll is not registered; historical data may fail to record for 64-bit processes. Use 'regsvr32 ...
  52. VSLG4006: 64-bit TracelogProfiler.dll is not registered; IntelliTrace may fail to record data for 64-bit processes. Use 'regsvr32 ...
  53. VSP 7003: "{0}" Failed to stop monitor. This could happen if VSPerfMon.exe is detached before VSPerfASPNetCmd.exe finished ...
  54. VSP 7006: The specified profiling type "{0}" is not a valid profiling type. Check the /? help text for valid profiling types. ...
  55. VSP 7007: The website path is set to "{0}". "{1}" will be ignored. If this, or "{0}", was intended as a flag, check that ...
  56. VSP1713: Dynamic Hardware Partitioning happened during data collection. File contains inaccurate data: {0} Use /Admin:driver ...
  57. VSP2340: Environment variables were not properly set during profiling run and managed symbols may not resolve. Please use ...
  58. VsStandardCollector.exe is not correctly installed on the remote computer/device '{0}'. Ensure that the current version of ...
  59. VSTestConfig help command command The name of the command you want help on List of commands: NetworkEmulation Configure the ...
  60. Wait a few minutes and then click 'Repair/Install Agents'. Alternatively, use the Environment Viewer to connect to the machine ...
  61. Waiting for Hyper-V Data Exchange Service to start. To start test agent in a lab environment, ensure that Hyper-V Data Exchange ...
  62. Waits until the workflow capability services are ready. This activity can be used only with the virtual environments in Team ...
  63. Want Key Input : Specifies that the owner of the listbox receives WM_VKEYTOITEM messages when a key is pressed while the ...
  64. Warbird: function '%$pD' marked as _forceinline not inlined because it contains inline assembly which cannot be protected ...
  65. Warbird: function '%$pD' marked as _forceinline not inlined because protection level of inlinee is greater than the parent ...
  66. Warehouse TimeZone information has been updated. Please verify that existing warehouse data matches the new TimeZone information. ...
  67. Warning Level : Select how strict you want the compiler to be about checking for potentially suspect constructs. (/W0 - /W4) ...
  68. Warning MSRep0016: Some rules have not been evaluated due to security restrictions. Results for this validation may be incomplete. ...
  69. Warning VSP2368: Settings not supported on this version of Windows were ignored, open the Performance Session Properties ...
  70. Warning VSP2702: Report does not have required information to resolve source lines in functions for process {0}'. This is ...
  71. Warning {0} - Unable to perform the {1} operation because you have a pending {2} on a different item at the destination (to ...
  72. Warning! If you cancel the creation of this copy, you will lose all changes that you previously made to the release template. ...
  73. Warning: A conflict in test references is detected while loading the test metadata file. This may indicate inconsistencies ...
  74. Warning: A conflict in test settings is detected while loading the test metadata file. This may indicate inconsistencies ...
  75. Warning: A lower feature level was used to create device because the originally captured feature level did not work with ...