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 The active parser must be the same as either the markup or code parser. 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. The "CancelBacktrack" method can be called only while in a look-ahead process started with the "BeginLookahead" method. "EndBlock" was called without a matching call to "StartBlock". 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> } End of file was reached before the end of the block comment. All comments started with "/*" sequence must be terminated with a matching "*/" sequence. 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}". 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. } 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 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 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. @section Header { ... } In CSHTML, the @section keyword is case-sensitive and lowercase (as with all C# keywords) "<text>" and "</text>" tags cannot contain attributes. 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. The 'inherits' keyword must be followed by a type name on the same line. 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}" character end of file space or line break 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: "@@" The {0} property of the {1} structure cannot be null. Expected a "{0}" after the helper parameters. Expected a "{0}" after the helper name. Helper parameter list is missing a closing ")". Helper blocks cannot be nested within each other. Parser was started with a null Context property. The Context property must be set BEFORE calling any methods on the parser. "{0}" is a reserved word and cannot be used in implicit expressions. An explicit expression ("@()") must be used. Unexpected {0} after helper keyword. All helpers must have a name which starts with an "_" or alphabetic character. The remaining characters must be either "_" or alphanumeric. Cannot resume this symbol. Only the symbol immediately preceding the current one can be resumed. Cannot finish span, there is no current block. Call StartBlock at least once before finishing a span Cannot complete the tree, there are still open blocks. Cannot complete the tree, StartBlock must be called at least once. Cannot complete action, the parser has finished. Only CompleteParse can be called to extract the final parser results after the parser has finished 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>> <<unknown>> 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 "{" after "@" character. Once inside the body of a code block (@if {}, @{}, etc.) you do not need to use "@{" to switch to code. line break <<newline sequence>> <<razor comment>> <<text>> <<white space>> The parser provided to the ParserContext was not a Markup Parser. 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 [BG][{0}] Shutdown [BG][{0}] Startup [BG][{0}] {1} changes arrived [BG][{0}] Discarded {1} changes [BG][{0}] Collecting {1} discarded changes Disabled [P][{0}] {3} Change in {2} milliseconds: {1} [P][{0}] Received Change: {1} Enabled [Razor] {0} [BG][{0}] no changes arrived? [BG][{0}] Parse Complete in {1} milliseconds [M][{0}] Queuing Parse for: {1} [Razor] Editor Tracing {0} [BG][{0}] Trees Compared in {1} milliseconds. Different = {2} Section blocks ("{0}") cannot be nested. Only one level of section blocks are allowed. Tag Helper '{0}'s attributes must have names. The tag helper '{0}' must not have C# in the element's attribute declaration area. A TagHelperCodeGenerator must only be used with TagHelperBlocks. Directive '{0}' must have a value. Directive '{0}'s value must be surrounded in double quotes. 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}'. TagHelper attributes must be welformed. Non-string tag helper attribute values must not be empty. Add an expression to this attribute value. 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. @'{0}' directives must not appear in non-string tag helper attribute values. 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. Attribute '{0}' on tag helper element '{1}' requires a value. Tag helper bound attributes of type '{2}' cannot be empty or contain only whitespace.