Visual Studio 2012
- The current source control operation cannot be completed. The source control plug-in returned the following error: Item(s) ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: Item(s) ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: Item(s) ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: Shell ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: Source ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: Source ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: Source ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: Specified ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: The specified ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: The specified ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: The user ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: Type is ...
- The current source control operation cannot be completed. The source control plug-in returned the following error: Unsupported ...
- The current system does not meet the minimum hardware requirements for SQL Server 2005 Express Edition (x86). Contact your ...
- The current team project does not contain any test plans. Use Microsoft Test Manager to create a test plan for the team project, ...
- The current Test Runner session has a conflict with another Test Runner session that is already using the same environment. ...
- The current user does not have Administrative rights. Please run this command from an elevated context in order to modify ...
- The current user has insufficient rights to modify the registry of this machine. Modify this user's registry rights and rerun ...
- The current value in the .settings file is '{0}' The new value in the app.config file is '{1}' Do you want to update the ...
- The current value of {0} refers to types that cannot be resolved. The document cannot be edited in the Design view until ...
- The CurrentRunConfig property of the LoadTest specifies a run configuration named '{0}', but there is no run configuration ...
- The custom operation '{0}' refers to a method which is overloaded. The implementations of custom operations may not be overloaded. ...
- The custom-designed version of 'System.Runtime.CompilerServices.ExtensionAttribute' found by the compiler is not valid. Its ...
- The data adapter "{0}" is not completely configured. To resolve this problem, configure the adapter by using the Data Adapter ...
- The data adapter is not completely configured. To resolve this problem, configure the adapter by using the Data Adapter Configuration ...
- The data could not be saved because the server could not be contacted. Please check your network connection and try saving ...
- The data in row {0} was not committed. Error Source: {1}. Error Message: {2} Correct the errors and retry or press ESC to ...
- The data in this report is currently showing only Just My Code. To disable this feature change the setting in Tools->Options->Performance ...
- The data provider is either not based on the ADO .NET technology or is missing the InvariantName property that identifies ...
- The data provider required to connect to the local data file could not be found. The file will be added to the project but ...
- The data source name '{0}' contains invalid characters. The name cannot: - contain any of the following characters: / ? : ...
- The Data Source value in the connection sting specifies an instance of SQL Server that is not installed. To resolve this ...
- The data source was not disposed before the application was terminated. Consider calling IVsUISimpleDataSource.Close() when ...
- The Data Sources window encountered an error while trying to display the data source. Verify the data source is correct, ...
- The data warehouse has detected data conflicts for the following work item fields. The conflicts occur because there are ...
- The database compatibility level of the build script %i does not match the compatibility level of the target database %i. ...
- The database connection information could not be found. Please verify that the TFS database is running and accessible and ...
- The database file that you are attempting to connect to is not compatible with the current instance of SQL Server. To continue, ...
- The database for the following team project collection is not reachable: {0}. The server that hosts the database is: {1}. ...
- The database name in the build script %s does not match the name of the target database %s. Verify whether your database ...
- The database schema provider with type {0} is not valid. You must make sure the database schema provider is loaded, or you ...
- The database settings for DB_CHAINING or TRUSTWORTHY could not be modified. You must be a SysAdmin to apply these settings. ...
- The database that you specified cannot be used. The database exists, but it is not a warehouse database for Team Foundation ...
- The database that you specified does not exist. A new database will be created and populated for use with Team Foundation ...
- The database you entered is already in use by another Team Project Collection. You must enter a database that is not in use. ...
- The database you have selected is part of a SQL AlwaysOn group or database mirror, which require upgrade to be performed ...
- The database you selected is new or does not contain any objects. Click Finish to create an empty dataset. Once database ...
- The database you specified cannot be used. The database exists, but its schema is not valid for use with Team Foundation ...
- The DatabaseSchemaProviderFamily extension {0} could not be loaded because there is already another DatabaseSchemaProviderFamily ...
- The DataGrid's selected items collection no longer supports INotifyCollectionChanged. This means we don't get events on multi-select. ...
- The DataProviderServices extension {0} could not be loaded because there is already another DataProviderServices extension ...
- The Dataset Designer in this version of Visual Studio is not compatible with the version of SQL Server Compact for this connection. ...
- The DataSet Project property in {0} must be set to a project that targets the same version of the .NET Framework as the current ...
- The DataSet Project property must be set to a project that targets the same version of the .NET Framework as the current ...
- The DataSetFile attribute is missing or empty in {0}. Datasets that contain non-Null DataSetProject values require a valid ...
- The DATA_COMPRESSION option was specified more than once for the target, or for at least one of its partitions if the target ...
- The DB Command "{0}" is not completely configured. To resolve this problem, set the CommandText and Connection properties ...
- The debug driver for the selected Debugging Accelerator Type is not installed on the target machine. For more information, ...
- The debug mode is Program, but there is no program specified. Please specify a program using the project's Debug property ...
- The debug source files settings for the active solution indicate that the debugger will not ask the user to find the file: ...
- The debugger attempted to call a function within the debugged process but this function did not complete in time. The debugger ...
- The debugger attempted to call a function within the debugged process but this function did not complete in time. The state ...
- The debugger does not support debugging managed and native code at the same time on the platform of the target computer/device. ...
- The debugger is not properly installed. Cannot debug the requested type of code. Run setup to install or repair the debugger. ...
- The debugger is still attaching to the process or the process is not currently executing the type of code selected for debugging. ...
- The debugger was unable to automatically select an appropriate type of code. Please manually specify the type(s) of code ...
- The debugger was unable to communicate with its worker process (msvsmon.exe) due to a protocol compatibility error. Ensure ...
- The debugger was unable to find the registration for the target application. If the problem persists, try uninstalling and ...
- The debugger was unable to install Windows Web Services API because an installer for the current operating system version ...
- The debugger was unable to install Windows Web Services API. Downloading the update installer failed. Please ensure that ...
- The debugger was unable to terminate one or more processes: %1 The debugger may be unstable now. It is recommended that you ...
- The declaration form 'let . and .' for non-recursive bindings is not used in F# code. Consider using a sequence of 'let' ...
- The declarations in this file will be placed in an implicit module '{0}' based on the file name '{1}'. However this is not ...
- The declared type parameters for this type extension do not match the declared type parameters on the original type '{0}' ...
- The default code index database exists but is not in a usable state. An attempt to automatically recover the database failed. ...