Visual Studio 2010

  1. The exception-handling model that catches C++ exceptions only and tells the compiler to assume that extern C functions never ...
  2. The ExcludePermissions property is deprecated. The permission set requested by the application has been set to the permissions ...
  3. The ExecuteEventArgs Data property does not contain an object of type '{0}'. This command cannot be invoked unless the correct ...
  4. The existing published deployment does not appear to be a valid deployment manifest. Are you sure you want to overwrite this ...
  5. The expected URL of the file(s) being deployed conflicts with file(s) on the server. The file(s) on the server will be deleted ...
  6. The expression cannot be evaluated as it comes from an untrusted assembly. Only expressions consisting of field or property ...
  7. The expression compiler was unable to evaluate the indexer expression '{0}' because it references the model parameter '{1}' ...
  8. The expression form { expr with . } may only be used with record types. To build object types use { new Type(.) with . } ...
  9. The expression used for the calculated field '{1}' includes a variable reference. Variable values cannot be used in calculated ...
  10. The expression used for the calculated field '{1}' includes an aggregate function. Aggregate functions cannot be used in ...
  11. The expression used for the language of '{1}' includes a variable reference. Variable values cannot be used in report language ...
  12. The expression used for the language of '{1}' includes an aggregate function. Aggregate functions cannot be used in report ...
  13. The expression used for the language of '{1}' refers to a data source. Data sources cannot be used in report language expressions. ...
  14. The expression used for the language of '{1}' refers to a dataset. Datasets cannot be used in report language expressions. ...
  15. The expression used for the language of '{1}' refers to a report item. Report items cannot be used in report language expressions. ...
  16. The expression used for the language of '{1}' uses the aggregate function Previous. Previous cannot be used in report language ...
  17. The expression used for the language of '{1}' uses the aggregate function RunningValue. RunningValue cannot be used in report ...
  18. The expression used for the language of '{1}' uses the function RowNumber. RowNumber cannot be used in report language expressions. ...
  19. The expression used for the parameter '{1}' in the dataset '{3}' includes a variable reference. Variable values cannot be ...
  20. The expression used for the parameter '{1}' in the dataset '{3}' includes an aggregate function. Aggregate functions cannot ...
  21. The expression used for the parameter {1}' in the dataset {3}' includes the function RowNumber. RowNumber cannot be used ...
  22. The expression used for the parameter {1}' in the dataset {3}' refers to a data source. Data sources cannot be used in query ...
  23. The expression used for the parameter {1}' in the dataset {3}' refers to a dataset. Datasets cannot be used in query parameter ...
  24. The expression used for the parameter {1}' in the dataset {3}' refers to a field. Fields cannot be used in query parameter ...
  25. The expression used for the parameter {1}' in the dataset {3}' refers to a report item. Report items cannot be used in query ...
  26. The expression used for the parameter {1}' in the dataset {3}' uses the aggregate function Previous. Previous cannot be used ...
  27. The expression used for the parameter {1}' in the dataset {3}' uses the aggregate function RunningValue. RunningValue cannot ...
  28. The Expression Web Include component only works on files in the current Web site. Please select a page to include from the ...
  29. The Extended information for file %s was corrupt and has been moved. Some of the name information may be lost, if this has ...
  30. The Extended information for item %s did not match the information in the parent. It will be changed to match the parent. ...
  31. The Extended Name information for the item %s has been corrupted and could not be recreated. The name will be shortened. ...
  32. The Extensibility wizard cannot run. You must have at least one of the following products installed: Microsoft Visual Basic ...
  33. The extension '{0}' returned an invalid value from RedirectParent. If you do not want to support redirection, return the ...
  34. The extension has been successfully uninstalled. Please close and restart all open instances of the below applications for ...
  35. The extension package is invalid because it contains both a regular extension manifest '{0}' and a Language Pack manifest ...
  36. The ExtensionHandle object is not valid. You must call ExtensionManager.GetExtensionHandle(ExtensionHandle h) to get the ...
  37. The extraction rule ExtractHiddenFields can only be applied to a response that is either an HTML document or a partial rendering ...
  38. The extraction rule was created, and the text is extracted to a context parameter named '{0}'. '{1}' matches were found for ...
  39. The extraction rule was created, and the text is extracted to a context parameter named '{0}'. You will need to add bindings ...
  40. The F# Interactive path has been set in \"Tools > Options.\" under \"F# Tools, F# Interactive\". However, the given file ...
  41. The Feature "{0}" cannot be deployed as part of the sandboxed solution "{1}". Move the feature to a package where the Sandboxed ...
  42. The field labels and expected type of this record expression or pattern do not uniquely determine a corresponding record ...
  43. The field name {0} suggests that it is instance data but it is declared as static (Shared in Visual Basic). Review this member ...
  44. The field name {0} suggests that it is static (Shared in Visual Basic) data but it is declared as an instance member. Review ...
  45. The field with the name {1}' in the dataset {3}' has both or neither of the following properties: DataField and Value. Fields ...
  46. The file "{0}" could not be deleted. Make sure that the file is not in use and you have required permissions to access the ...
  47. The file %1 cannot be saved because it is write-protected. You can either save the file in a different location or %0 can ...
  48. The file %1 does not support refactoring and will need to be manually changed. Do you wish to continue with the refactoring? ...
  49. The file %s cannot be saved because it is write-protected. You can either save the file in a different location or %s can ...
  50. The file %s could not be loaded. An attempt to repair this condition failed because the file could not be found. Please reinstall ...
  51. The file %s has been changed by another application. Global undo and redo operations involving this file can no longer be ...
  52. The file %s is not a valid Team Foundation physical database file. It must be renamed to a file with an extension or moved ...
  53. The file %s, which you attempted to edit, is read-only on disk. Would you like to make the file writeable or edit it anyway? ...
  54. The file '%0' cannot be checked out for editing because this would cause it to be reloaded, and reloads are not currently ...
  55. The file '%0' needs to be checked out before it can be edited. The file was not checked out automatically because you have ...
  56. The file '%1' does not support refactoring and will need to be manually changed. Do you wish to continue with the refactoring? ...
  57. The file '%1' is open in an editor with unsaved changes. Do you want to save your changes before adding this file to the ...
  58. The file '%1' is open in an editor with unsaved changes. Do you want to save your changes before invoking Open With on this ...
  59. The file '%1' no longer exists in the Web project. Do you want to remove the copy from the offline cache and lose any changes ...
  60. The file '%1' no longer exists in the Web. Do you want to remove the copy from the local cache and lose any changes you have ...
  61. The file '%1' no longer exists in this Web site. You have this file open with unsaved changes. Do you want to save these ...
  62. The file '%1' was not signed. The deployment project contains deprecated signing properties. See Help for more information. ...
  63. The file '%s' (%s) lists '%s' as a branch, but that file is missing or corrupted or doesn't have any parents or branches ...
  64. The file '{0}' cannot be opened because it is already opened in another editor. Close other document windows that are using ...
  65. The file '{0}' does not have any class definitions in it. Add a class definition. If you have verified that there is at least ...
  66. The file '{0}' does not support code parsing or generation because it is not contained within a project that supports code. ...
  67. The file '{0}' in the project '{1}' is missing from the file system. You must restore this file or remove it from your project. ...
  68. The file '{0}' is not in the current solution. Load the project containing '{1}' into the current solution to open this file. ...
  69. The file '{0}' was created in an earlier version of Visual Studio. This file will be converted, in memory only, to the current ...
  70. The file '{0}' was created with an unsupported version of this application and cannot be added to the settings file list. ...
  71. The file '|' could not be accessed. Try one of the following: Make sure the specified folder exists. Make sure the folder ...
  72. The file can not be opened because it is being used by another process. Please close all applications that might access this ...
  73. The file containing the definition might be missing or in a different version than the rest of the project. Make sure that ...
  74. The file contains a character that cannot be represented in the current code page (%d). Save the file in Unicode format to ...
  75. The file could not be downloaded because it is not located on a trusted site. The XML expansion pack may not work as expected. ...