Visual Studio 2013
- Failed to parse the file contents. This is likely caused by the file encoding type set on this file in TFS not matching the ...
- Failed to parse xml in the UITest file attachment or TCM.Steps field. Make sure this data is valid and retry the operation. ...
- Failed to process configuration file. Try to restart this application. If failures continue, try to repair your installation. ...
- Failed to query the source control global permissions for {0}. You have insufficient permission. You must have the "Edit ...
- Failed to queue test run {0}. Test run contains one or more test assemblies targeted for .Net Framework3.5. Refer to website ...
- Failed to read manifest file "{0}". It may need to be regenerated. Try running the Rebuild Solution command to fix the error. ...
- Failed to read manifest file "{0}". It may need to be regenerated. Try running the Rebuild Solution command to fix the error. ...
- Failed to register following shortcut keys - {0}This could be because another application is already using these shortcut ...
- Failed to register listener on registry key {0} with error code {1}. Please ensure that test agent has required permission ...
- Failed to register output. Please try enabling Per-user Redirection or register the component from a command prompt with ...
- Failed to register this test agent with the test controller. Connection to the test controller {0} failed because either ...
- Failed to register this test agent with the test controller. Possible reasons could be you do not have permissions to connect ...
- Failed to register this test agent with the test controller. Possible reasons could be you do not have the right permissions ...
- Failed to remove test environment '{0}' as there is a mismatch between the server's version '{1}' and your version '{2}' ...
- Failed to save a screenshot to a file. Please check that the save location exists, that you have write permission to the ...
- Failed to save some module load event(s) before the in-memory buffer pool was exhausted. You may experience some symbol resolution ...
- Failed to save some process, thread, and/or fiber start event(s) before the in-memory buffer pool was exhausted. Some processes, ...
- Failed to save the changes to "{0}". Please make sure the file is not read-only and that there is adequate disk space for ...
- Failed to save the changes to "{0}". The file name cannot contain any of these characters: / ? : " < > | # %. The path cannot ...
- Failed to set permissions for account {0} on path {1}. Builds using agent {2} may not work correctly until this issue is ...
- Failed to set the source control global permissions for {0}. You have insufficient permission. You must have the "Edit server-level ...
- Failed to start SharePoint Sandboxed Code service on the SharePoint server. Please try manually starting this service via ...
- Failed to start the test executor. This might indicate missing or corrupted executor files. Consider re-installing Visual ...
- Failed to unregister '%1', this process will be launched using DEBUG_PROCESS flag. The behavior of application might be different. ...
- Failed to update service account of Windows service {0} because Service Control Manager could not be opened. (Error Code: ...
- Failed to update TFS Team Project Collection {0} as the test controller service account could not be granted required permission. ...
- Failed to update TFS Team Project Collection {0} as the test controller service account could not be granted required permission. ...
- Failed to update the Client Secret and Package SID (HRESULT: 0x{0:X}). Please update these values manually on the Windows ...
- Failed to update the Client Secret and Package SID because of an unexpected result from the store. Please update these values ...
- Failed to update the Client Secret and Package SID. Please update these values manually on the Windows Azure Mobile Services ...
- Failed to update the owner of workspaces from service account {0} to {1}. You will have to determine tfs account corresponding ...
- Failed to upgrade '%s'. Please make sure you have the corresponding platform installed under '%vctargetspath%\platforms\%s' ...
- Failed to upgrade ProjectReference '%s'. Please make sure the file is not missing from disk, and the solution/project has ...
- Failed to upgrade property sheet file '%s'. Please make sure the file exists, is not corrupted and containing folder is not ...
- Failed to upload test run results to the drop location '{1}'. Ask your server administrator to make the drop location available. ...
- Failure during generic comparison: the type '{0}' does not implement the System.IComparable interface. This error may be ...
- Failure to reload may indicate that the header file is not in sync with the rc file. If the project is under source control, ...
- Fallback Location : This value is used as a secondary location to store the browsing database or IntelliSense files. If empty, ...
- Favor Fast Code. Maximizes the speed of EXEs and DLLs by instructing the compiler to favor speed over size. (This is the ...
- Favor Size or Speed : Choose whether to favor code size or code speed; 'Global Optimization' must be turned on. (/Ot, /Os) ...
- Feature '%1!ls!' is not part of the standardized ISO C# language specification, and may not be accepted by other compilers ...
- Field cannot be deleted because an index is associated with the field. Please contact your Team Foundation Server administrator. ...
- Field {0} is a member of type {1}, which is serializable, but is of type {2}, which is not serializable. Add the NonSerializedAttribute ...
- Field {0} is declared as 'static readonly' but is initialized with a constant value '{1}'. Mark this field as 'const' instead. ...
- Field {0} is declared as 'static readonly' but is initialized with an empty string ("). Mark this field as 'const' instead. ...
- Fields of static readonly field '%1!ls!' cannot be assigned to (except in a static constructor or a variable initializer) ...
- File '%s' cannot be added to the project. The most likely reason is that the project file is under source code control and ...
- File '%s' cannot be removed. The most likely reason is that the file is under source code control and cannot be removed at ...
- File '%s' cannot be renamed. The most likely reason is that the file is under source code control and cannot be renamed at ...
- File '%s' not found in current source file's directory or in build system paths. Current source file path: '%s' Build system ...
- file already exists in the following directory: '{1}'. You either need to delete or move this file, choose another backup ...
- File could not be renamed. You must press Enter to commit changes to the file name before activating the designer window. ...
- File Extensions : Specifies the file extensions to associate with this rule. Files that match the given extensions will automatically ...
- File type handlers cannot be built as managed assemblies. Set the Common Language Runtime options to no CLR support in project ...
- File {0} contains a script loader file reference (url = {1}) that will be ignored because the explicit content type ({2}) ...
- File {0} contains a script loader file reference (url = {1}, type = {2}) that could not be loaded because the path could ...
- File {0} contains a script loader file reference (url = {1}, type = {2}) that could not be loaded because the resolved path ...
- File {0} contains a script loader file reference (url = {1}, type = {2}) that could not be loaded because the resolved path ...
- File {0} contains a script loader file reference (url = {1}, type = {2}) that will be ignored because the upper limit ({3}) ...
- File {0} is included into {1} and {2} item groups. This is not allowed for project items, which can belong to only one item ...
- File {0} is not found in your installation. The task cannot proceed. Please make sure Visual Studio is properly installed. ...
- Files and folders cannot be: - Empty strings - System reserved names, including 'CON', 'AUX', PRN', 'COM1' or 'LPT2' - contain ...
- Files and folders cannot be: - Empty strings - System reserved names, including 'CON', 'AUX', PRN', 'COM1' or 'LPT2' - contain ...
- Files and folders cannot: -be empty strings - contain any of the following characters: / ? : \ " < > | # % - contain Unicode ...
- Files in libraries or multiple-file applications must begin with a namespace or module declaration, e.g. 'namespace SomeNamespace.SubNamespace' ...
- Files should begin with either a namespace or module declaration, e.g. 'namespace SomeNamespace.SubNamespace' or 'module ...
- FileTracker : error FTK1013: could not find unicode byte order marker in the file tracking log file: %ls. The tracking data ...
- Filter properties are not supported by the following technology: {0}. To search for a control, you must remove the filter ...
- FilterDescriptor '{0}' with type '{1}' is associated with {2} TypeDescriptors. It has to be associated with exactly one TypeDescriptor. ...
- FilterDescriptor with Name '{0}' defined on the TypeDescriptor '{1}' could not be located in the containing method '{2}'. ...
- FilterDescriptor with Name '{1}' is associated with {2} TypeDescriptors belonging to Parameter(s) with direction 'Out', 'InOut' ...
- FilterDescriptor with Name '{1}' is not associated with any TypeDescriptors belonging to Parameter(s) with direction 'In'. ...
- Filters are not supported for one or more instances of the following breakpoint and will be ignored for those instances. ...
- Finalizers should be avoided where possible, to avoid the additional performance overhead involved in tracking object lifetime. ...
- Finally clauses that restore security-related state should be wrapped in an outer try block. This will prevent an exception ...