text/microsoft-resx
2.0
System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Element is not valid.
You must select at least one member.
Interface name conflicts with an existing type name.
Interface name is not a valid {0} identifier.
Illegal characters in path.
File name must have the "{0}" extension.
Debugger
Determining breakpoint location...
Determining autos...
Resolving breakpoint location...
Validating breakpoint location...
Getting DataTip text...
Preview unavailable
Overrides
Overridden By
Inherits
Inherited By
Implements
Implemented By
Maximum number of documents are open.
Failed to create document in miscellaneous files project.
Invalid access.
The following references were not found. {0}Please locate and add them manually.
End position must be >= start position
Not a valid value
given workspace doesn't support undo
Add a reference to '{0}'
Event type is invalid
Can't find where to insert member
Can't rename 'other' elements
Unknown rename type
IDs are not supported for this symbol type.
Can't create a node id for this symbol kind: '{0}'
Project References
Base Types
Miscellaneous Files
Could not find project '{0}'
Could not find location of folder on disk
Error while reading file '{0}': {1}
Assembly
Exceptions:
Member of {0}
Parameters:
Project
Remarks:
Returns:
Summary:
Type Parameters:
File already exists
File path cannot use reserved keywords
DocumentPath is illegal
Project Path is illegal
Path cannot have empty filename
The given DocumentId did not come from the Visual Studio workspace.
Project: {0} ({1})
Use the dropdown to view and switch to other projects this file may belong to.
{0}
Use the dropdown to view and navigate to other items in this file.
Project: {0}
Use the dropdown to view and switch to other projects this file may belong to.
ErrorReadingRuleset
Error reading ruleset file {0} - {1}
AnalyzerChangedOnDisk
The analyzer assembly '{0}' has changed. Diagnostics may be incorrect until Visual Studio is restarted.
C#/VB Diagnostics Table Data Source
C#/VB Todo List Table Data Source
Cancel
_Deselect All
Extract Interface
Generated name:
New _file name:
New _interface name:
OK
_Select All
Select public _members to form interface
_Access:
Add to _existing file
Add to _current file
Change Signature
_Create new file
Default
File Name:
Generate Type
_Kind:
Location:
Select destination
Modifier
Name:
Parameter
Parameters:
Preview method signature:
Preview reference changes
_Project:
Type
Type Details:
Re_move
_Restore
More about {0}
Navigation must be performed on the foreground thread.
[+]
[-]
Reference to '{0}' in project '{1}'
<Unknown>
Analyzer reference to '{0}' in project '{1}'
Project reference to '{0}' in project '{1}'
AnalyzerDependencyConflict
Analyzer assemblies '{0}' and '{1}' both have identity '{2}' but different contents. Only one will be loaded and analyzers using these assemblies may not run correctly.
{0} references
1 reference
'{0}' encountered an error and has been disabled.
Enable
Enable and ignore future errors
No Changes
Current block
Determining current block.
IntelliSense
C#/VB Build Table Data Source
MissingAnalyzerReference
Analyzer assembly '{0}' depends on '{1}' but it was not found. Analyzers may not run correctly unless the missing assembly is added as an analyzer reference as well.
Suppression State
Active
Suppressed
N/A
Suppression state is supported only for intellisense diagnostics, which are for the current solution snapshot. Switch to 'Intellisense' diagnostics for suppression.
Suppress diagnostics
Computing suppressions fix...
Applying suppressions fix...
Remove suppressions
Computing remove suppressions fix...
Applying remove suppressions fix...
This workspace only supports opening documents on the UI thread.
This workspace does not support updating Visual Basic compilation options.
This workspace does not support updating Visual Basic parse options.
Synchronize {0}
Synchronizing with {0}...
Visual Studio has suspended some advanced features to improve performance.
Installing '{0}'
Installing '{0}' completed
Package install failed: {0}
<Unknown>
No
Yes
Choose a Symbol Specification and a Naming Style.
Enter a title for this Naming Rule.
Enter a title for this Naming Style.
Enter a title for this Symbol Specification.
Accessibilities (can match any)
Capitalization:
all lower
ALL UPPER
camel Case Name
First word upper
Pascal Case Name
Severity:
Modifiers (must match all)
Name:
Naming Rule
Naming Style
Naming Style:
Naming Rules allow you to define how particular sets of symbols should be named and how incorrectly-named symbols should be handled.
The first matching top-level Naming Rule is used by default when naming a symbol, while any special cases are handled by a matching child rule.
Naming Style Title:
Parent Rule:
Required Prefix:
Required Suffix:
Sample Identifier:
Symbol Kinds (can match any)
Symbol Specification
Symbol Specification:
Symbol Specification Title:
Word Separator:
example
IdentifierWord_Example and IdentifierWord_Identifier are combined (with prefixes, suffixes, and word separators) into an example identifier name in the NamingStyle UI.
identifier
IdentifierWord_Example and IdentifierWord_Identifier are combined (with prefixes, suffixes, and word separators) into an example identifier name in the NamingStyle UI.
Install '{0}'
Uninstalling '{0}'
Uninstalling '{0}' completed
Uninstall '{0}'
Package uninstall failed: {0}
Error encountered while loading the project. Some project features, such as full solution analysis for the failed project and projects that depend on it, have been disabled.
Project loading failed.
To see what caused the issue, please try below.
1. Close Visual Studio
2. Open a Visual Studio Developer Command Prompt
3. Set environment variable “TraceDesignTime” to true (set TraceDesignTime=true)
4. Delete .vs directory/.suo file
5. Restart VS from the command prompt you set the environment variable (devenv)
6. Open the solution
7. Check '{0}' and look for the failed tasks (FAILED)
Additional information:
Installing '{0}' failed.
Additional information: {1}
Uninstalling '{0}' failed.
Additional information: {1}
Move {0} below {1}
{0} and {1} are parameter descriptions
Move {0} above {1}
{0} and {1} are parameter descriptions
Remove {0}
{0} is a parameter description
Restore {0}
{0} is a parameter description
Re-enable
Learn more
Prefer framework type
Prefer predefined type
Copy to Clipboard
Close
<Unknown Parameters>
--- End of inner exception stack trace ---
For locals, parameters and members
For member access expressions
Prefer object initializer
Expression preferences:
Block Structure Guides
Outlining
Show guides for code level constructs
Show guides for comments and preprocessor regions
Show guides for declaration level constructs
Show outlining for code level constructs
Show outlining for comments and preprocessor regions
Show outlining for declaration level constructs
Variable preferences:
Prefer inlined variable declaration
Use expression body for methods
Code block preferences:
Use expression body for accessors
Use expression body for constructors
Use expression body for indexers
Use expression body for operators
Use expression body for properties
Some naming rules are incomplete. Please complete or remove them.
Manage specifications
Manage naming styles
Reorder
Severity
Specification
Required Style
This item cannot be deleted because it is used by an existing Naming Rule.
Prefer collection initializer
Prefer coalesce expression
Collapse #regions when collapsing to definitions
Prefer null propagation
Prefer explicit tuple name
Description
Preference
Implement Interface or Abstract Class
For a given symbol, only the topmost rule with a matching 'Specification' will be applied. Violation of that rule's 'Required Style' will be reported at the chosen 'Severity' level.
at the end
When inserting properties, events and methods, place them:
with other members of the same kind
Prefer braces
Over:
Prefer:
or
built-in types
everywhere else
type is apparent from assignment expression
Get help for '{0}'
Get help for '{0}' from Bing
Move down
Move up
Remove
Pick members
Unfortunately, a process used by Visual Studio has encountered an unrecoverable error. We recommend saving your work, and then closing and restarting Visual Studio.
Prefer auto properties
Add a symbol specification
Remove symbol specification
Add item
Edit item
Remove item
Add a naming rule
Remove naming rule
VisualStudioWorkspace.TryApplyChanges cannot be called from a background thread.
prefer auto properties
prefer throwing properties
When generating properties:
Options
Try the preview version of our live code analysis extension, which provides more fixes for common API design, naming, performance, and reliability issues
Never show this again
Prefer simple 'default' expression
Prefer inferred tuple element names
Prefer inferred anonymous type member names
Preview pane
Analysis
Enable full solution _analysis
Perform editor _feature analysis in external process (experimental)
Fade out unreachable code
Fading
Changes are not allowed if the assembly has not been loaded.
Changes are not allowed if the project wasn't built when debugging started.
Changes are not allowed if the project wasn't loaded and built when debugging started.
'Lightweight solution load' is enabled for the current solution. Disable it to ensure that all projects are loaded when debugging starts.
Changes are not allowed while code is running.
Prefer local function over anonymous function
Keep all parentheses in:
In other operators
Never if unnecessary
Always for clarity
Parentheses preferences:
Module has been unloaded.
Can't apply changes -- module '{0}' has been unloaded.
Can't apply changes -- unexpected error: '{0}'
Prefer deconstructed variable declaration
External reference found
No references found to '{0}'
Search found no results
Sync Class View
Reset Visual Studio default keymapping
Enable navigation to decompiled sources (experimental)
IMPORTANT: Visual Studio includes decompiling functionality (“Decompiler”) that enables reproducing source code from binary code. By accessing and using the Decompiler, you agree to the Visual Studio license terms and the terms for the Decompiler below. If you do not agree with these combined terms, do not access or use the Decompiler.
You acknowledge that binary code and source code might be protected by copyright and trademark laws. Before using the Decompiler on any binary code, you need to first:
(i) confirm that the license terms governing your use of the binary code do not contain a provision which prohibits you from decompiling the software; or
(ii) obtain permission to decompile the binary code from the owner of the software.
Your use of the Decompiler is optional. Microsoft is not responsible and disclaims all liability for your use of the Decompiler that violates any laws or any software license terms which prohibit decompiling of the software.
I agree to all of the foregoing:
Decompiler Legal Notice
Colorize regular expressions
Highlight related components under cursor
Regular Expressions
Report invalid regular expressions
The settings configured here only apply to your machine. To configure these settings to travel with your solution, use .editorconfig files.
Modifier preferences:
Prefer readonly fields
Analyzing '{0}'
Live code analysis
Prefer conditional expression over 'if' with assignments
Prefer conditional expression over 'if' with returns
Apply '{0}' keymapping scheme
We notice you suspended '{0}'. Reset keymappings to continue to navigate and refactor.
Use expression body for lambdas
Prefer compound assignments
Generate .editorconfig file from settings
Save .editorconfig file
Kind
Prefer index operator
Prefer range operator
All methods
Avoid expression statements that implicitly ignore value
Avoid unused parameters
Avoid unused value assignments
Parameter preferences:
Non-public methods
Unused value is explicitly assigned to an unused local
Unused value is explicitly assigned to discard
Value assigned here is never used
Value returned by invocation is implicitly ignored
Back
Finish
Interface cannot have field.
Make abstract
Members
Namespace: '{0}'
Pull Members Up
Additional changes are needed to complete the refactoring. Review changes below.
_Select Dependents
Select destination and members to pull up.
Select members:
_Select Public
'{0}' will be changed to abstract.
'{0}' will be changed to non-static.
'{0}' will be changed to public.
Calculating dependents...
Select destination:
Use expression body for local functions
Allow:
Make '{0}' abstract
Review Changes
Select member
Prefer static local functions