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 provided anti-forgery token failed a custom data check. The provided anti-forgery token was meant for a different claims-based user than the current user. The required anti-forgery cookie "{0}" is not present. The anti-forgery token could not be decrypted. If this application is hosted by a Web Farm or cluster, ensure that all machines are running the same version of ASP.NET Web Pages and that the <machineKey> configuration specifies explicit encryption and validation keys. AutoGenerate cannot be used in a cluster. The required anti-forgery form field "{0}" is not present. The anti-forgery cookie token and form field token do not match. Validation of the provided anti-forgery token failed. The cookie "{0}" and the form field "{1}" were swapped. The provided anti-forgery token was meant for user "{0}", but the current user is "{1}". The anti-forgery system has the configuration value AntiForgeryConfig.RequireSsl = true, but the current request is not an SSL request. The assembly "{0}" is already registered. An application module is already registered for virtual path "{0}". Unable to find an application module with the name "{0}". The assembly "{0}" is not a registered application module. The resource file "{0}" could not be found. A claim of type '{0}' was not present on the provided ClaimsIdentity. A claim of type 'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier' or 'http://schemas.microsoft.com/accesscontrolservice/2010/07/claims/identityprovider' was not present on the provided ClaimsIdentity. To enable anti-forgery token support with claims-based authentication, please verify that the configured claims provider is providing both of these claims on the ClaimsIdentity instances it generates. If the configured claims provider instead uses a different claim type as a unique identifier, it can be configured by setting the static property AntiForgeryConfig.UniqueClaimTypeIdentifier. Index length must be exactly one. Index must be of type string or int when getting a value. Index must be of type string when setting a value. The parameter conversion from type "{0}" to type "{1}" failed. See the inner exception for more information. The parameter conversion from type "{0}" to type "{1}" failed because no type converter can convert between these types. An HttpContext is required to perform this operation. Check that this operation is being performed during a web request. Value "{0}" specified in "{1}" is an invalid value for the SessionState directive. Possible values are: "{2}". At most one SessionState value can be declared per page. RequestScope cannot be created when _AppStart is executing. Storage scope is read only. Storage scopes cannot be created when _AppStart is executing. The provided identity of type '{0}' is marked IsAuthenticated = true but does not have a value for Name. By default, the anti-forgery system requires that all authenticated identities have a unique Name. If it is not possible to provide a unique Name for this identity, consider setting the static property AntiForgeryConfig.AdditionalDataProvider to an instance of a type that can provide some form of unique identifier for the current user. Validation parameter names in unobtrusive client validation rules cannot be empty. Client rule type: {0} Validation parameter names in unobtrusive client validation rules must start with a lowercase letter and consist of only lowercase letters or digits. Validation parameter name: {0}, client rule type: {1} Validation type names in unobtrusive client validation rules cannot be empty. Client rule type: {0} Validation type names in unobtrusive client validation rules must consist of only lowercase letters. Invalid name: "{0}", client rule type: {1} Validation type names in unobtrusive client validation rules must be unique. The following validation type was seen more than once: {0} The UrlData collection is read-only. Input format is invalid. Values do not match. Value must be a decimal between {0} and {1}. Value must be an integer between {0} and {1}. Value is invalid. This field is required. Max length: {0}. String must be between {0} and {1} characters. Files with leading underscores ("_") cannot be served. The file "{0}" cannot be requested directly because it calls the "{1}" method. The following file could not be rendered because its extension "{0}" might not be supported: "{1}". The file "{0}" could not be rendered, because it does not exist or is not a valid page. The layout page "{0}" could not be found at the following path: "{1}". The "RenderBody" method has already been called. The "RenderBody" method has not been called for layout page "{0}". Section already defined: "{0}". The "RenderSection" method has already been called for the section named "{0}". Section not defined: "{0}". The following sections have been defined but have not been rendered for the layout page "{0}": "{1}".