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 Value cannot be null or an empty string. Value must be between {0} and {1}. Value must be a value from the "{0}" enumeration. Value must be greater than {0}. Value must be greater than or equal to {0}. Value must be less than {0}. Value must be less than or equal to {0}. Value cannot be an empty string. It must either be null or a non-empty string. 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. Block cannot be built because a Type has not been specified in the BlockBuilder <<character literal>> <<comment>> <<identifier>> <<integer literal>> <<keyword>> <<newline sequence>> <<real literal>> <<string literal>> <<white space>> 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. "EndBlock" was called without a matching call to "StartBlock". "{0}" character end of file line break space or line break <<newline sequence>> <<razor comment>> <<text>> <<white space>> 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 "@" 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. Expected "{0}". The {0} directive is not supported. Optional quote around the directive '{0}' is missing the corresponding opening or closing quote. The 'inherits' keyword must be followed by a type name on the same line. 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. Sections cannot be empty. The "@section" keyword must be followed by a block of markup surrounded by "{}". For example: @section Sidebar { <!-- Markup and text goes here --> } 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. Encountered end tag "{0}" with no matching start tag. Are your start/end tags properly balanced? Unexpected {0} after section keyword. Section names must start with an "_" or alphabetic character, and the remaining characters must be either "_" or alphanumeric. "{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: "@@" 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 "{" 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. 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 Cannot complete action, the parser has finished. Only CompleteParse can be called to extract the final parser results after the parser has finished Parser was started with a null Context property. The Context property must be set BEFORE calling any methods on the parser. Attribute '{0}' on tag helper element '{1}' requires a value. Tag helper bound attributes of type '{2}' cannot be empty or contain only whitespace. @section Header { ... } In CSHTML, the @section keyword is case-sensitive and lowercase (as with all C# keywords) Cannot perform '{1}' operations on '{0}' instances with different file paths. <<unknown>> 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. 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}'. 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. In order to put a symbol back, it must have been the symbol which ended at the current position. The specified symbol ends at {0}, but the current position is {1} Unexpected literal following the '{0}' directive. Expected '{1}'. Unexpected end of file following the '{0}' directive. Expected '{1}'.