text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 . See also {0}. The tuples have differing lengths of {0} and {1} The resulting type would be infinite when unifying '{0}' and '{1}' A type parameter is missing a constraint '{0}' The unit of measure '{0}' does not match the unit of measure '{1}' The type '{0}' does not match the type '{1}' The type '{0}' is not compatible with the type '{1}'{2} {0} {0} This expression has type\n\t{0}\nbut is here used with type\n\t{1}{2} Type mismatch. Expecting a\n\t{0}\nbut given a\n\t{1}{2}.\n Type constraint mismatch when applying the default type '{0}' for a type inference variable. Consider adding further type constraints Type constraint mismatch. The type \n\t{0}\nis not compatible with type\n\t{1}{2}\n Uppercase variable identifiers should not generally be used in patterns, and may indicate a misspelt constructor name. Discriminated union cases and exception labels must be uppercase identifiers {0} \n\nPossible overload: '{0}'. \n\nPossible best overload: '{0}'. This function takes too many arguments, or is used in a context where a function is not expected Member constraints with the name '{0}' are given special status by the F# compiler as certain .NET types are implicitly augmented with this member. This may result in compilation failures if you attempt to invoke the member constraint from your own code. Note, the OCaml-compatibility exception type Not_found is now mapped to System.Collections.Generic.KeyNotFoundException, rather than System.IndexOutOfRangeException. This means a number of F# functions now raise KeyNotFoundException instead of IndexOutOfRangeException. If you explicitly catch IndexOutOfRangeException in your code you may need to adjust your exception handling accordingly. This change was made because IndexOutOfRangeException is a CLR-reserved exception which should not be raised in user or library code. {0}. A definition to be compiled as a .NET event does not have the expected form. Only property members can be compiled as .NET events. Implicit object constructors for structs must take at least one argument The type implements the interface '{0}' but this is not revealed by the signature. You should list the interface in the signature, as the interface will be discoverable via dynamic type casts and/or reflection. This value is not a function and cannot be applied. Did you forget to terminate a declaration? This value is not a function and cannot be applied The type '{0}' expects {1} type argument(s) but is given {2} Lookup on object of indeterminate type based on information prior to this program point. A type annotation may be needed prior to this program point to constrain the type of the object. This may allow the lookup to be resolved. Duplicate definition of {0} '{1}' The {0} '{1}' can not be defined because the name '{2}' clashes with the {3} '{4}' in this type or module Two members called '{0}' have the same argument counts and/or signatures. To overload methods with identical argument counts use an 'OverloadID' attribute. Duplicate definition of {0} '{1}' The {0} '{1}' is not defined. A construct with this name was found in FSharp.PowerPack.dll, which contains some modules and types that were implicitly referenced in some previous versions of F#. You may need to add an explicit reference to this DLL in order to compile this code. internal error: the type {0} did not contain the {1} '{2}' internal error: the module/namespace '{0}' from compilation unit '{1}' did not contain the {2} '{3}' This field is not mutable The fields '{0}' and '{1}' are from different types '{0}' is bound twice in this pattern A use of the function '{0}' does not match a type inferred elsewhere. The inferred type of the function is\n\t{1}.\nThe type of the function required at this point of use is\n\t{2}{3}\nThis error may be due to limitations associated with generic recursion, i.e. type inference requires that generic functions and members are instantiated in only one way within their own recursive scope, e.g. within a 'let rec' collection or within a group of classes. Consider splitting these recursive bindings into two groups. Invalid runtime coercion or type test from type {0} to {1}\n{2} This runtime coercion or type test from type\n\t{0}\n to \n\t{1}\ninvolves an indeterminate type based on information prior to this program point. Runtime type tests are not allowed on some types. Further type annotations are needed. The static coercion from type\n\t{0}\nto \n\t{1}\n involves an indeterminate type based on information prior to this program point. Static coercions are not allowed on some types. Further type annotations are needed. A coercion from the value type \n\t{0}\nto the type \n\t{1}\nwill involve boxing. Consider using 'box' instead This type is 'abstract' since some abstract members have not been given an implementation. If this is intentional then add the '[<AbstractClass>]' attribute to your type. This construct causes code to be less generic than indicated by its type annotations. The type variable implied by the use of a '#', '_' or other type annotation at or near '{0}' has been constrained to be type '{1}'. This construct causes code to be less generic than indicated by the type annotations. The unit-of-measure variable '{0} has been constrained to be measure '{1}'. This construct causes code to be less generic than indicated by the type annotations. The type variable '{0} has been constrained to be type '{1}'. identifier integer literal floating point literal decimal literal character literal keyword 'base' symbol '(*)' symbol '$' infix operator infix operator symbol ':>'" " symbol '::' symbol '{0} infix operator infix operator infix operator prefix operator symbol ':?>' infix operator infix operator symbol '&' symbol '&&' symbol '||' symbol '<' symbol '>' symbol '?' symbol '??' symbol ':?' integer.. symbol '..' quote symbol symbol '*' type application symbol ':' symbol ':=' symbol '<-' symbol '=' symbol '>.' symbol '>|]' symbol '-' symbol '+' or '-' operator name symbol ',' symbol '.' symbol '|' symbol # symbol '_' symbol ';' symbol ';;' symbol '(' symbol ')' symbol 'splice' start of quotation symbol '[' symbol '[|' symbol '[<' symbol '{' symbol '{<' symbol '|]' symbol '>}' symbol '>]' end of quotation symbol ']' symbol '}' keyword 'public' keyword 'private' keyword 'internal' keyword 'constraint' keyword 'instance' keyword 'delegate' keyword 'inherit' keyword 'constructor' keyword 'default' keyword 'override' keyword 'abstract' reserved keyword 'virtual' keyword 'class' keyword 'member' keyword 'static' keyword 'namespace' start of structured construct incomplete structured construct at or before this point keyword 'then' keyword 'else' keyword 'let' or 'use' binder keyword keyword 'do' keyword 'with' keyword 'function' keyword 'fun' end of input internal dummy token keyword 'do!' yield yield! keyword 'interface' keyword 'elif' symbol '->' symbol '->>' keyword 'sig' keyword 'struct' keyword 'upcast' keyword 'downcast' keyword 'null' reserved keyword keyword 'module' keyword 'and' keyword 'as' keyword 'assert' keyword 'asr' keyword 'downto' keyword 'exception' keyword 'false' keyword 'for' keyword 'fun' keyword 'function' keyword 'finally' keyword 'lazy' keyword 'match' reserved keyword 'method' keyword 'mutable' keyword 'new' keyword 'of' keyword 'open' keyword 'or' keyword 'void' keyword 'extern' keyword 'interface' keyword 'rec' keyword 'to' keyword 'true' keyword 'try' keyword 'type' keyword 'val' keyword 'inline' keyword 'when' keyword 'while' keyword 'with' keyword 'if' keyword 'do' keyword 'done' keyword 'in' symbol '(' or '[' keyword 'begin' keyword 'end' directive inactive code lex failure whitespace comment line comment string text byte array literal string literal end of input Unexpected end of input Unexpected {0} in interaction in directive in field declaration in discriminated union case declaration in binding in binding in member definition in definitions in member signature in value signature in type signature in lambda expression in union case in extern declaration in object expression in if/then/else expression in open declaration in module or namespace signature in pattern matching in begin/end expression in record expression in type definition in exception definition in type name in attribute list in quotation literal in type constraint in implementation file in definition in signature file in pattern in expression in type in type arguments keyword symbol (due to indentation-aware syntax) . Expected {0} or other token. . Expected {0}, {1} or other token. . Expected {0}, {1}, {2} or other token. The type '{0}' cannot be used as the source of a type test or runtime coercion The type '{0}' does not have any proper subtypes and cannot be used as the source of a type test or runtime coercion. The type '{0}' does not have any proper subtypes and need not be used as the target of a static coercion This upcast is unnecessary - the types are identical This type test or downcast will always hold {0} The member '{0}' does not have the correct type to override any given virtual method The member '{0}' does not have the correct type to override the corresponding abstract method. The required signature is '{0}'. This constructor is applied to {0} argument(s) but expects {1} The two sides of this 'or' pattern bind different sets of variables Module '{0}' contains\n\t{1}\nbut its signature specifies\n\t{2}\n{3}. The module contains the constructor\n\t{0}\nbut its signature specifies\n\t{1}\n{2}. The exception definitions are not compatible because {0}. The module contains the exception definition\n\t{1}\nbut its signature specifies\n\t{2} The module contains the field\n\t{0}\nbut its signature specifies\n\t{1}\n{2}. Module '{0}' requires a {1} '{2}' The address-of operator may result in non-verifiable code. Its use is restricted to passing byrefs to functions that require them {0} Thread static and context static 'let' bindings are deprecated. Instead use a declaration of the form 'static val mutable <ident> : <type>' in a class. Add the 'DefaultValue' attribute to this declaration to indicate that the value is initialized to the default value on each new thread. This lookup uses a deprecated feature, where a class type is inferred from the use of a class field label. Consider using a type annotation to make it clear which class the field comes from. This expression is a function value, i.e. is missing arguments. Its type is {0}. This expression should have type 'unit', but has type '{0}'. If assigning to a property use the syntax 'obj.Prop <- expr'. This recursive use will be checked for initialization-soundness at runtime. This warning is usually harmless, and may be suppressed by using #nowarn "40" or --nowarn 40. The value '{0}' will be evaluated as part of its own definition This value will be eventually evaluated as part of its own definition. You may need to make the value lazy or a function. Value '{0}'{1}. " will evaluate '{0}'" Bindings may be executed out-of-order because of this forward reference. This and other recursive references to the object(s) being defined will be checked for initialization-soundness at runtime through the use of a delayed reference. This is because you are defining one or more recursive objects, rather than recursive functions. This warning may be suppressed by using #nowarn "40" or --nowarn 40. Recursive references to the object being defined will be checked for initialization soundness at runtime through the use of a delayed reference. Consider placing self-references in members or within a trailing expression of the form '<ctor-expr> then <expr>'. Recursive references to the object being defined will be checked for initialization soundness at runtime through the use of a delayed reference. Consider placing self-references within 'do' statements after the last 'let' binding in the construction sequence. The containing type can use 'null' as a representation value for its nullary union case. Invoking an abstract or virtual member or an interface implementation on a null value will lead to an exception. If necessary add a dummy data value to the nullary constructor to avoid 'null' being used as a representation for this type. The containing type can use 'null' as a representation value for its nullary union case. This member will be compiled as a static member. The member '{0}' doesn't correspond to a unique abstract slot based on name and argument count alone . Multiple implemented interfaces have a member with this name and argument count . Consider implementing interfaces '{0}' and '{1}' explicitly. . Additional type annotations may be required to indicate the relevant override. This warning can be disabled using #nowarn "70" or --nowarn 70. {0} parse error parse error: unexpected end of file {0} internal error: {0}\nPlease build a small example that reproduces this problem and report it to fsbugs@microsoft.com. {0} Incomplete pattern matches on this expression. For example, the value '{0}' may indicate a case not covered by the pattern(s). For example, the value '{0}' may indicate a case not covered by the pattern(s). However, a pattern rule with a 'when' clause might successfully match this value. . Sequence expressions involving incomplete matches on 'for' and 'let' constructs are deprecated and will raise an IncompleteMatchFailure exception in a future revision of the F# language. Please use a separate match expression instead, adding '()' for the failing branch. This rule will never be matched This value is not mutable This value is not local This construct is deprecated . {0} {0}. This warning can be disabled using '--nowarn 57' or '#nowarn "57"'. Uses of this construct may result in the generation of unverifiable .NET IL code. This warning can be disabled using '--nowarn 9' or '#nowarn "9"'. This construct is for compatibility with OCaml. {0}This warning can be disabled using '--mlcompatibility', '--nowarn 62' or '#nowarn "62"'. This construct is deprecated: {0}. This construct is deprecated: it is only for use in the F# library The following fields require values: {0} Value restriction. The value '{0}' has generic type\n\t{1}\nEither make the arguments to '{2}' explicit or, if you do not intend for it to be generic, add a type annotation. Value restriction. The value '{0}' has generic type\n\t{1}\nEither make '{2}' into a function with explicit arguments or, if you do not intend for it to be generic, add a type annotation. Value restriction. This member has been inferred to have generic type\n\t{0}\nConstructors and property getters/setters cannot be more generic than the enclosing type. Add a type annotation to indicate the exact types involved. Value restriction. The value '{0}' has been inferred to have generic type\n\t{1}\nEither make the arguments to '{2}' explicit or, if you do not intend for it to be generic, add a type annotation. Value restriction. The value '{0}' has been inferred to have generic type\n\t{1}\nEither define '{2}' as a simple data term, make it a function with explicit arguments or, if you do not intend for it to be generic, add a type annotation. syntax error {0} {0} Override implementations in augmentations are now deprecated. Override implementations should be given as part of the initial declaration of a type. Override implementations should be given as part of the initial declaration of a type. Interface implementations in augmentations are now deprecated. Interface implementations should be given on the initial declaration of a type. Interface implementations should be given on the initial declaration of a type. A required assembly reference is missing. You must add a reference to assembly '{0}'. The type referenced through '{0}' is defined in an assembly that is not referenced. You must add a reference to assembly '{1}'. The command-line option '{0}' has been deprecated. {1} #I directives may only occur in F# script files (extensions .fsx or .fsscript). Either move this code to a script file, add a '-I' compiler option for this reference or delimit the directive with delimit it with '#if INTERACTIVE'/'#endif'. #r directives may only occur in F# script files (extensions .fsx or .fsscript). Either move this code to a script file, add a '-r' compiler option for this reference or delimit the directive with '#if INTERACTIVE'/'#endif'. #R 'copy after compile' references are no longer supported. If using a script file (extensions .fsx or .fsscript), change to '#r', otherwise add a post-compilation build step in your build environment to copy your files locally after the build. This directive may only be used in F# script files (extensions .fsx or .fsscript). Either remove the directive, move this code to a script file or delimit the directive with '#if INTERACTIVE'/'#endif'. Unable to find the file '{0}' in any of\n {1} Assembly reference '{0}' was not found or is invalid One or more warnings in loaded file.\n One or more errors in loaded file.\n Loaded files may only be F# source files (extension .fs). This F# script file (.fsx or .fsscript) will be treated as an F# source file Invalid assembly name '{0}' from InternalsVisibleTo attribute in {1} Invalid assembly name '{0}' from InternalsVisibleTo attribute (assembly filename not available) Could not load file '{0}' because it does not exist or is inaccessible {0} (Code={1}) internal error: {0}\nPlease build a small example that reproduces this problem and report it to fsbugs@microsoft.com. Error emitting 'System.Reflection.AssemblyCultureAttribute' attribute -- 'Executables cannot be satellite assemblies, Culture should always be empty' Option '--delaysign' overrides attribute 'System.Reflection.AssemblyDelaySignAttribute' given in a source file or added module Option '--keyfile' overrides attribute 'System.Reflection.AssemblyKeyFileAttribute' given in a source file or added module Option '--keycontainer' overrides attribute 'System.Reflection.AssemblyNameAttribute' given in a source file or added module PDB files cannot be generated when running on Mono