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 Register Tag Helpers for use in the current document. Add tag helpers from the specified type name and assembly name. Specify '*' for the type name to include all tag helper types from the specified assembly. TypeName, AssemblyName Value cannot be null or an empty string. Block cannot be built because a Type has not been specified in the BlockBuilder Block directive '{0}' cannot be imported. code This is a literal used when composing ParserError_* messages. Most blocks are named by the keyword that starts them, for example "if". However, for those without keywords, a (localizable) name must be used. This literal is ALWAYS used mid-sentence, thus should not be capitalized. explicit expression This is a literal used when composing ParserError_* messages. Most blocks are named by the keyword that starts them, for example "if". However, for those without keywords, a (localizable) name must be used. This literal is ALWAYS used mid-sentence, thus should not be capitalized. Invalid newline sequence '{0}'. Support newline sequences are '\r\n' and '\n'. <<character literal>> <<comment>> <<identifier>> <<integer literal>> <<keyword>> <<newline sequence>> <<real literal>> <<string literal>> <<white space>> The document type '{0}' does not support the extension '{1}'. Invalid directive keyword '{0}'. Directives must have a non-empty keyword that consists only of letters. A non-optional directive token cannot follow an optional directive token. The '{0}' directive expects an identifier. The '{0}' directive expects a namespace name. The '{0}' directive expects a string surrounded by double quotes. The '{0}' directive expects a type name. The '{0}` directive must appear at the start of the line. The '{0}' directives value(s) must be separated by whitespace. The document of kind '{0}' does not have a '{1}'. The document classifier must set a value for '{2}'. The '{0}' directive may only occur once per document. "EndBlock" was called without a matching call to "StartBlock". line break The '{0}' feature requires a '{1}' provided by the '{2}'. The feature must be initialized by setting the '{0}' property. Specify a C# code block. <<newline sequence>> <<razor comment>> <<text>> <<white space>> Specify the base class for the current document. The base type that the current page inherits. TypeName The '{0}' operation is not valid when the builder is empty. The node '{0}' has a read-only child collection and cannot be modified. The reference is invalid. The node '{0}' could not be found as a child of '{1}'. The reference is invalid. References initialized with the default constructor cannot modify nodes. The '{0}' node type can only be used as a direct child of a '{1}' node. The node '{0}' is not the owner of change '{1}'. Provided value for razor language version is unsupported or invalid: '{0}'. Invalid tag helper directive look up text '{0}'. The correct look up text format is: "name, assemblyName". Invalid tag helper directive '{0}' value. '{1}' is not allowed in prefix '{2}'. The key must not be null. Cannot use built-in RazorComment handler, language characteristics does not define the CommentStart, CommentStar and CommentBody known symbol types or parser does not override TokenizerBackedParser.OutputSpanBeforeRazorComment The specified encoding '{0}' does not match the content's encoding '{1}'. The "@" character must be followed by a ":", "(", or a C# identifier. If you intended to switch to markup, use an HTML start tag, for example: @if(isLoggedIn) {{ <p>Hello, @user!</p> }} "{{" is an escape sequence for string.Format, when outputted to the user it will be displayed as "{" End of file was reached before the end of the block comment. All comments started with "/*" sequence must be terminated with a matching "*/" sequence. Directive '{0}' must have a value. An opening "{0}" is missing the corresponding closing "{1}". The {0} block is missing a closing "{1}" character. Make sure you have a matching "{1}" character for all the "{2}" characters within this block, and that none of the "{1}" characters are being interpreted as markup. The {0} directive is not supported. Optional quote around the directive '{0}' is missing the corresponding opening or closing quote. Inline markup blocks (@<p>Content</p>) cannot be nested. Only one level of inline markup is allowed. Markup in a code block must start with a tag and all start tags must be matched with end tags. Do not use unclosed tags like "<br>". Instead use self-closing tags like "<br/>". The "{0}" element was not closed. All elements must be either self-closing or have a matching end tag. Namespace imports and type aliases cannot be placed within code blocks. They must immediately follow an "@" character in markup. It is recommended that you put them at the top of the page, as in the following example: @using System.Drawing; @{{ // OK here to use types from System.Drawing in the page. }} "{{" is an escape sequence for string.Format, when outputted to the user it will be displayed as "{" Outer tag is missing a name. The first character of a markup block must be an HTML tag with a valid name. End of file was reached before the end of the block comment. All comments that start with the "@*" sequence must be terminated with a matching "*@" sequence. "{0}" is a reserved word and cannot be used in implicit expressions. An explicit expression ("@()") must be used. Section blocks ("{0}") cannot be nested. Only one level of section blocks are allowed. Expected a "{0}" but found a "{1}". Block statements must be enclosed in "{{" and "}}". You cannot use single-statement control-flow statements in CSHTML pages. For example, the following is not allowed: @if(isLoggedIn) <p>Hello, @user</p> Instead, wrap the contents of the block in "{{}}": @if(isLoggedIn) {{ <p>Hello, @user</p> }} {0} is only ever a single character "<text>" and "</text>" tags cannot contain attributes. "{0}" is not valid at the start of a code block. Only identifiers, keywords, comments, "(" and "{{" are valid. "{{" is an escape sequence for string.Format, when outputted to the user it will be displayed as "{" End-of-file was found after the "@" character. "@" must be followed by a valid code block. If you want to output an "@", escape it using the sequence: "@@" Unexpected "{{" after "@" character. Once inside the body of a code block (@if {{}}, @{{}}, etc.) you do not need to use "@{{" to switch to code. "{{" is an escape sequence for string.Format, when outputted to the user it will be displayed as "{" A space or line break was encountered after the "@" character. Only valid identifiers, keywords, comments, "(" and "{{" are valid at the start of a code block and they must occur immediately following "@" with no space in between. "{{" is an escape sequence for string.Format, when outputted to the user it will be displayed as "{" Encountered end tag "{0}" with no matching start tag. Are your start/end tags properly balanced? End of file or an unexpected character was reached before the "{0}" tag could be parsed. Elements inside markup blocks must be complete. They must either be self-closing ("<br />") or have matching end tags ("<p>Hello</p>"). If you intended to display a "<" character, use the "&lt;" HTML entity. Unterminated string literal. Strings that start with a quotation mark (") must be terminated before the end of the line. However, strings that start with @ and a quotation mark (@") can span multiple lines. Parser was started with a null Context property. The Context property must be set BEFORE calling any methods on the parser. Cannot complete the tree, StartBlock must be called at least once. Cannot complete the tree, there are still open blocks. Cannot finish span, there is no current block. Call StartBlock at least once before finishing a span The '{0}' phase requires a '{1}' provided by the '{2}'. The phase must be initialized by setting the '{0}' property. Path must begin with a forward slash '/'. The item '{0}' could not be found. Remove Tag Helpers for use in the current document. Remove tag helpers from the specified type name and assembly name. Specify '*' for the type name to remove all tag helper types from the specified assembly. TypeName, AssemblyName The '{0}' requires a '{1}' delegate to be set. Attribute '{0}' on tag helper element '{1}' requires a value. Tag helper bound attributes of type '{2}' cannot be empty or contain only whitespace. Define a section to be rendered in the configured layout page. The name of the section. SectionName @section Header { ... } In CSHTML, the @section keyword is case-sensitive and lowercase (as with all C# keywords) <<unknown>> Invalid tag helper bound property '{1}' on tag helper '{0}'. Tag helpers cannot bind to HTML attributes with name '{2}' because the name contains a '{3}' character. Invalid tag helper bound property '{1}' on tag helper '{0}'. Tag helpers cannot bind to HTML attributes with name '{2}' because the name starts with '{3}'. Invalid tag helper bound property '{1}' on tag helper '{0}'. Tag helpers cannot bind to HTML attributes with a null or empty name. Invalid tag helper bound property '{1}' on tag helper '{0}'. Tag helpers cannot bind to HTML attributes with prefix '{2}' because the prefix contains a '{3}' character. Invalid tag helper bound property '{1}' on tag helper '{0}'. Tag helpers cannot bind to HTML attributes with prefix '{2}' because the prefix starts with '{3}'. Invalid restricted child '{1}' for tag helper '{0}'. Tag helpers cannot restrict child elements that contain a '{2}' character. Invalid restricted child for tag helper '{0}'. Name cannot be null or whitespace. Tag helpers cannot target attribute name '{0}' because it contains a '{1}' character. Targeted attribute name cannot be null or whitespace. Tag helpers cannot target parent tag name '{0}' because it contains a '{1}' character. Targeted parent tag name cannot be null or whitespace. Tag helpers cannot target tag name '{0}' because it contains a '{1}' character. Targeted tag name cannot be null or whitespace. Tag helper directive assembly name cannot be null or empty. The tag helper attribute '{0}' in element '{1}' is missing a key. The syntax is '<{1} {0}{{ key }}="value">'. TagHelper attributes must be well-formed. The parent <{0}> tag helper does not allow non-tag content. Only child tag helper(s) targeting tag name(s) '{1}' are allowed. Found an end tag (</{0}>) for tag helper '{1}' with tag structure that disallows an end tag ('{2}'). Tag helpers '{0}' and '{1}' targeting element '{2}' must not expect different {3} values. The <{0}> tag is not allowed by parent <{1}> tag helper. Only child tags with name(s) '{2}' are allowed. Specify a prefix that is required in an element name for it to be included in Tag Helper processing. The tag prefix to apply to tag helpers. Prefix Tag Helper '{0}'s attributes must have names. The tag helper '{0}' must not have C# in the element's attribute declaration area. Code blocks (e.g. @{{var variable = 23;}}) must not appear in non-string tag helper attribute values. Already in an expression (code) context. If necessary an explicit expression (e.g. @(@readonly)) may be used. Inline markup blocks (e.g. @<p>content</p>) must not appear in non-string tag helper attribute values. Expected a '{0}' attribute value, not a string. Found a malformed '{0}' tag helper. Tag helpers must have a start and end tag or be self closing. Missing close angle for tag helper '{0}'. Unreachable code. This can happen when a new {0} is introduced. Unexpected literal following the '{0}' directive. Expected '{1}'. Unexpected end of file following the '{0}' directive. Expected '{1}'. The hash algorithm '{0}' is not supported for checksum generation. Supported algorithms are: '{1}'. Set '{2}' to '{3}' to suppress automatic checksum generation. The '{0}.{1}' property must not be null.