Visual Studio 2012

  1. Shims requires tests to be executed in a process with UnitTestIsolation enabled. Please ensure that your VisualStudio installation ...
  2. Show "Build Rule" Dialog : If set to false, the "Matching Custom Build Rule" dialog will not be shown when a file is added ...
  3. Show Environment In Log : Specifies whether or not to echo all environment variables into the build log during builds of ...
  4. Show Only Rule Properties : Specifies whether to show only the properties defined in the tool file when the rule is displayed ...
  5. Show or hide miscellaneous files in Solution Explorer;Save documents as Unicode;Auto-load files changed outside the environment;Allow ...
  6. Shows field information. By default, this lists all fields on the Team Foundation Server. Optional parameters can be used ...
  7. Shows how the TopMost property controls whether a form is a top-most form. A top-most form will float above other, non top-most ...
  8. Shut down a logger with a given session name. Usage: shutdown options Options: /session: required The name of the session ...
  9. Shutdown: Raised after all application forms are closed. This event is not raised if the application terminates abnormally. ...
  10. Similar to the Response URL validation rule but allows you to turn it off for specific requests and specify custom terminators. ...
  11. Since '%1!ls!' is an async method that returns 'Task', a return keyword must not be followed by an object expression. Did ...
  12. Since no additional actions have been recorded an action recording region has been inserted out of sequence. It is advisable ...
  13. Since the build definition was opened, Daylight Savings Time has started or ended. This means that the values you have selected ...
  14. Since the reference property {0}' is not backed by a foreign key, it is not valid to get its OriginalValue unless the reference ...
  15. Since the solution was not closed the get operation has been cancelled. You must initiate a get operation at a later time ...
  16. Since you are not restoring all the databases, your Team Foundation Server may not be in a synchronized state after the restore ...
  17. Since you have not configured lab service account, make sure a) test agent can communicate with the test controller, b) test ...
  18. Single server configuration with the application tier, data tier, Sharepoint, Reporting Services, and Analysis Services on ...
  19. Single-threaded COM objects are not properly supported on Windows CE platform, such as the Windows Mobile platforms that ...
  20. Skipped firewall configuration as no firewall is installed on this machine. If you add a firewall later, you need to run ...
  21. Skipped installation of Network Emulation driver. Network Emulation driver is not supported for current operating system. ...
  22. Skipped registering this test agent with the test controller as it is already registered as part of the virtual environment. ...
  23. Skipping because sharepoint is remote. You must manually added this service account to the Sharepoint farm administrators ...
  24. Skipping because the "$(AspNetConfiguration)" configuration is not supported for this web project. You can use the AspNetConfiguration ...
  25. Skipping team '{0}' due to missing process configuration settings. The common project settings and the agile project settings ...
  26. Skipping the host would make it unusable for lab management. If you skip the host, it will be re-checked when you attempt ...
  27. Skipping update of SOAP subscriptions due to failure to find an existing value for appSetting {0} in the current application ...
  28. Slide {0}: Missing value for shape: '{1}'. Subshapes in the metadata are not found on the slide. To view subshape names on ...
  29. Slide {0}: Multiple shape groups are defined on the slide. Some layout properties defined on subshape '{1}' may not be applied. ...
  30. Slide {0}: No shapes or multiple shapes defined on the slide. Exactly one shape has to be defined. If using multiple shapes, ...
  31. Slide {0}: The subshape '{1}' defined for the Edit Shape property cannot be edited. Define another subshape for default editing. ...
  32. SlipBehavior.Slip is supported only on root ParallelTimelines that do not reverse, accelerate, decelerate, or have a RepeatBehavior ...
  33. sln file exists, then the IDE looks for a single .sln file that references the project. If no such single .sln file exists, ...
  34. sln file exists, then the IDE looks for a single .sln file that references the project. If no such single .sln file exists, ...
  35. Smaller Type Check : Enable checking for conversion to smaller types, incompatible with any optimization type other than ...
  36. SnappedBackButtonStyle is used to style a Button for use in the title area of a snapped page. Margins appropriate for the ...
  37. Snapshot allows you to save the current state of the environment as it is, later you can access the same by using the restore ...
  38. Solution '%s' and its projects must be migrated to the formats used by this version of this application. If you choose to ...
  39. Solution and project files cannot be shared into existing solutions or projects. Consequently, %0 could not share all the ...
  40. Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read ...
  41. Solution Explorer Mode : The default mode for Visual C++ projects in Solution Explorer. When set to "Show only files in project", ...
  42. Solution file '%s' cannot be migrated because it cannot be modified. To migrate the solution, change the permissions on the ...
  43. Solution file '%s' cannot be migrated because it is read-only on disk. To migrate the solution, change the permissions on ...
  44. Solution file '%s' cannot be migrated because the solution cannot be checked out from source code control. To migrate the ...
  45. Solution file '%s' is from a previous version of this application and must be migrated in order to build in this version ...
  46. Solution Folder names cannot: - contain any of the following characters: / ? : \ " < > | # % - contain Unicode control characters ...
  47. Solution folders are not supported in this version of the application. Solution folder '%s' will be displayed as unavailable. ...
  48. Some applications that work outside the browser (including Team Explorer Everywhere command line client and the git-tf utility) ...
  49. Some attached data sources are configured to allow invalid certificates. Update the connection string to remove the option ...
  50. Some bindings are no longer valid as a result of this operation. Do you want to clear these bindings? Click 'Yes' to proceed ...
  51. Some build resources are enabled. If any builds are running during the servicing operation, they will be stopped by the system. ...
  52. Some bytes have been replaced with the Unicode substitution character while loading file {0} with {1} encoding. Saving the ...
  53. Some command line switches were read from the auto-response file "{0}". To disable this file, use the "/noautoresponse" switch. ...
  54. Some fakes could not be generated. For complete details, set Diagnostic attribute of the Fakes element in this file to 'true' ...
  55. Some features have been installed but need to be configured. Click on Configure Installed Features to begin configuring the ...
  56. Some files have been deleted or renamed on the server. You can continue with a get silently and the local files will be deleted ...
  57. Some files have been deleted or renamed on the server. You can continue with the Checkin or perform instead a Get operation ...
  58. Some files have been deleted or renamed on the server. You will need to perform a Get operation in order to see those changes ...
  59. Some items at the new binding have different contents on your local disk than in the newly bound database. You should consult ...
  60. Some messages did not display because they were not associated with any ProjectStarted events. Use diagnostic verbosity to ...
  61. Some of the files you are adding to your project are located outside of the project's binding root. These files cannot be ...
  62. Some of the files you are attempting to add to the solution cannot be added because they are used for source control tracking. ...
  63. Some of the files you are renaming or moving will be located outside of the project's binding root. The item(s) %1 will not ...
  64. Some of the items in the pending check-in list are not located in the solution that you have open. Double-click this message ...
  65. Some of the items that were modified while disconnected cannot be automatically checked out, possibly because these items ...
  66. Some of the items that you are adding to source control are stored in a file encoding (UTF-8) that your source control system ...
  67. Some of the items you are trying to checkout are both changed in memory and their on-disk version is different from the server's ...
  68. Some of the items you attempted to add to source control do not exist on disk and could not be added. If these items are ...
  69. Some of the items you have selected for this operation already have deferred source control operations pending. Do you want ...
  70. Some of the items you have selected for this operation have deferred source control operations pending. Because these items ...
  71. Some of the links you requested were created. However, you cannot create a link between a work item and itself. In those ...
  72. Some of the machines in the environment do not have the latest version of the test agent installed on them. Chose 'Upgrade ...
  73. Some of the project locations are not valid. %0 will continue the open from source control process, skipping projects with ...
  74. Some of the reviewers don't have permission to some of the files to review. Do you want to submit the code review anyway? ...
  75. Some of the selected database objects will not be deleted because they are open in designers. Are you sure that you want ...