Visual Studio 2013

  1. Project '|1' requires a reference to version '|2' of assembly '|3', but references version '|4' of assembly '|3'. Reference ...
  2. Project and solution names cannot: - contain any of the following characters: / ? : \ " < > | # % - contain Unicode control ...
  3. Project and solution names cannot: - contain any of the following characters: / ? : \ " < > | # % - contain Unicode control ...
  4. Project cannot be created because the "Excel Visual Studio Design-Time Adaptor Add-in" is not working correctly. Excel might ...
  5. Project cannot be created because the "Word Visual Studio Design-Time Adaptor Add-in" is not working correctly. Word might ...
  6. Project cannot be created or opened because the installed version of Visual Basic For Applications is not compatible with ...
  7. Project collection '{0}' was created successfully, however there were warnings. To view the warnings, examine the most recent ...
  8. Project creation failed: NuGet Package Manager must be installed before creating Apps for Office and SharePoint. To install ...
  9. Project data is unavailable at this time. As a result, all reports on this dashboard have been hidden. After you have created ...
  10. Project does not support paths relative to the root application directory. Remove the leading '/' qualifier from the '{0}' ...
  11. Project file '%s' contains an aggregated project type that cannot be found. The project cannot be opened without the project ...
  12. Project file contains ToolsVersion="{0}". This toolset is unknown or missing. You may be able to resolve this by installing ...
  13. Project file contains ToolsVersion="{0}". This toolset may be unknown or missing, in which case you may be able to resolve ...
  14. Project file could not be backed up to '%s'. Please make sure this file does not already exist and that it is not write-protected. ...
  15. Project item '{0}' was added to the current project but could not be associated with My Namespace extension '{1}'. It will ...
  16. Project item '{0}' was not migrated from the Common project because an item with the same name already exists in the target ...
  17. Project item Login.aspx or Logout.aspx already exists under '{0}' and was not replaced. Forms Authentication for HTML clients ...
  18. Project name '{0}' already exists on the server. The team project name must be unique on all Team Foundation servers used ...
  19. Project names cannot be empty strings nor can they contain only '.' or have any of the following characters: / ? : \ " < ...
  20. Project Property Sheets : Specifies the collection of property sheets, both system and user, inherited by this configuration. ...
  21. Project references from projects that do not support the Common Language Runtime are no longer supported. The project reference ...
  22. Project Server Extensions for Team Foundation Server will be removed from this computer. Do you want to continue uninstalling ...
  23. Project Server Sync: Cannot save the submit request to Project Server. An unknown error occurred. Contact your administrator ...
  24. Project Server Sync: Cannot save the submit request to Project Server. Check that the assignment exists on Project Server ...
  25. Project Server Sync: Cannot save the submit request to Project Server. Check the following likely causes to correct the problem: ...
  26. Project Server Sync: Cannot save the submit request to Project Server. Check the following likely causes to correct the problem: ...
  27. Project Server Sync: Cannot save the submit request to Project Server. One or more mapped work item fields on the submitted ...
  28. Project Server Sync: Cannot save the submit request to Project Server. The Start date must be greater than or equal to the ...
  29. Project Server Sync: Cannot save the submit request to Project Server. The Start date must be less than or equal to Finish ...
  30. Project Server Sync: Cannot save the submit request to Project Server. Verify that the enterprise project exists on Project ...
  31. Project Server Sync: One or more submit requests could not be saved. Work assigned to the failed requests has been allocated ...
  32. Project Server Sync: This item could not be submitted to Project Server because its linked parent item is marked for submission ...
  33. Project-level suppressions either have no target or are given %s a specific target and scoped to a namespace, type, member, ...
  34. Project-level suppressions either have no target or are given {0} a specific target and scoped to a namespace, type, member, ...
  35. Projects that support the Common Language Runtime have been converted to use dynamic linking to the run-time libraries (/MDd, ...
  36. Projects that target Windows 8 cannot be opened because the Tools for Maintaining Store apps for Windows 8 are not installed. ...
  37. Projects that target Windows 8 cannot be opened because the Tools for Maintaining Store Apps for Windows 8 are not installed. ...
  38. Projects that target Windows Phone 8 cannot be opened because the Windows Phone 8 Tools are not installed. Click "Install" ...
  39. Properties cannot be changed while Excel is in edit mode. Move the selection away from the currently selected cell and then ...
  40. Properties in custom build rules always inherit. Property '%s' in custom build rule '%s' has 'Inheritable=False'. Please ...
  41. Properties on this entity have been removed from the data source. The corresponding fields on the associated entity will ...
  42. Properties should be used instead of Get/Set methods in most situations. Methods are preferable to properties in the following ...
  43. Properties that return arrays are prone to code inefficiencies. Consider using a collection or making this a method. See ...
  44. Properties that return collections should be read-only so that users cannot entirely replace the backing store. Users can ...
  45. Properties whose values are of type IVsUICollection cannot currently be set through the presentation layer with a wrapped ...
  46. Property '{0}' of type '{1}' is not supported by Team Foundation Properties. Convert the value to an Int32, DateTime, Double, ...
  47. Property '{0}' of type '{1}' is not supported by the Properties service. Convert the value to an Int32, DateTime, Double, ...
  48. Property '{0}' requires the name '{1}' to be available, but that name is used by another property of the same entity. Please ...
  49. Property '{0}' with value '{1}' is out of range for the Team Foundation Properties service. Double values must be 0, within ...
  50. Property '{0}' with value '{1}' is out of range for the Team Foundation Properties service. The value must be between {2} ...
  51. Property '|1' cannot be initialized in an object initializer expression because all accessible overloads require arguments. ...
  52. Property '|1' doesn't return a value on all code paths. A null reference exception could occur at run time when the result ...
  53. Property definitions may not be declared mutable. To indicate that this property can be set, use 'member val PropertyName ...
  54. Property Sheet File : Specifies the name of the file that contains the property sheet information for the selected property ...
  55. Property statement Declares the name of a property, and the property procedures used to store and retrieve the value of the ...
  56. Property value is invalid. The path contains characters that are not supported by the NTFS file system or by SharePoint sites. ...
  57. Property value is invalid. The value must be a relative path that specifies the folder to deploy the file to. The path must ...
  58. Property value is invalid. The value must be a relative path that specifies the location to map the folder to. The path must ...
  59. Property, indexer, or event '%1!ls!' is not supported by the language; try directly calling accessor methods '%2!ls!' or ...
  60. Protected Friend keyword Specifies that one or more declared members of a class are accessible from anywhere in the same ...
  61. Protected keyword Specifies that one or more declared programming elements are accessible only from within their own class ...
  62. Provide a script to execute on each machine in the environment. Use the format: Logical VM Name (the name set to the VM in ...
  63. Provide accessors for both named and positional arguments. Each positional argument on an attribute should declare a read-only ...
  64. Provide an overridable implementation of Dispose(bool) on {0} or mark the type as sealed. A call to Dispose(false) should ...
  65. Provide the details your stakeholder needs to launch the application to give feedback on. The Feedback Client will display ...
  66. Provide the image resources to run the test provided by the Store Test Kit. These tests help prepare your application for ...
  67. Provide the user account that will be granted enough permissions to use the minimal features of the Administration Console. ...
  68. Provides a base class for all Panel elements. Use Panel elements to position and arrange child objects in Windows Presentation ...
  69. Provides a base class for elements that apply effects onto or around a single child element, such as a Border or Viewbox. ...
  70. Provides a base class for viewers that are intended to display fixed or flow content (represented by a FixedDocument or FlowDocument, ...
  71. Provides ability to enumerate the aggregates on the Phone. This capability gives your app read access to all linked contacts ...
  72. Provides ability to enumerate the aggregates on the Phone. With this capability your app can access all linked contacts and ...
  73. Provides access to a web browser component. This capability must be disclosed because an app could use scripting, which introduces ...
  74. Provides access to interactions with Wallet such as saving, updating, and deleting deals, membership cards and payment instruments. ...
  75. Provides access to network services. This capability must be disclosed because an app could incur charges when a phone is ...