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 argument '{0}' is invalid. Media types which match all types or match all subtypes are not supported. The content-type '{0}' added in the '{1}' property is invalid. Media types which match all types or match all subtypes are not supported. 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. 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 AntiForgeryOptions.RequireSsl = true, but the current request is not an SSL request. The method '{0}' on type '{1}' returned an instance of '{2}'. Make sure to call Unwrap on the returned value to avoid unobserved faulted Task. The method '{0}' on type '{1}' returned a Task instance even though it is not an asynchronous method. A claim of type '{0}' was not present on the provided ClaimsIdentity. 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 extending IAdditionalDataProvider by overriding the DefaultAdditionalDataProvider or a custom type that can provide some form of unique identifier for the current user. The class ReflectedActionFilterEndPoint only supports ReflectedActionDescriptors. The view component name '{0}' matched multiple types:{1}{2} {1} is the newline character The async view component method '{0}' should be declared to return Task<T>. A view component must return a non-null value. The view component method '{0}' should be declared to return a value. A view component named '{0}' could not be found. An invoker could not be created for the view component '{0}'. Could not find an '{0}' method matching the parameters. Could not find an '{0}' or '{1}' method matching the parameters. View components only support returning {0}, {1} or {2}. Replacing the action context is not supported. An action invoker could not be created for action '{0}'. The action descriptor must be of type '{0}'. Value cannot be null or empty. The '{0}' property of '{1}' must not be null. The '{0}' method of type '{1}' cannot return a null value. The supplied route values are ambiguous and can select multiple sets of actions. Property '{0}' is of type '{1}', but this method requires a value of type '{2}'. The partial view '{0}' was not found or no view engine supports the searched locations. The following locations were searched:{1} The value '{0}' is invalid. False Not Set True ViewData value must not be null. The expression compiler was unable to evaluate the indexer expression '{0}' because it references the model parameter '{1}' which is unavailable. The passed expression of expression node type '{0}' is invalid. Only simple member access expressions for model properties are supported. The IModelMetadataProvider was unable to provide metadata for expression '{0}'. Must call 'Contextualize' method before using this HtmlHelper instance. There is no ViewData item of type '{0}' that has the key '{1}'. The parameter '{0}' must evaluate to an IEnumerable when multiple selection is allowed. The ViewData item that has the key '{0}' is of type '{1}' but must be of type '{2}'. The '{0}' template was used with an object of type '{1}', which does not implement '{2}'. Templates can be used only with field access, property access, single-dimension array index, or single-parameter custom indexer expressions. Unable to locate an appropriate template for type {0}. The model item passed is null, but this ViewDataDictionary instance requires a non-null model item of type '{0}'. The model item passed into the ViewDataDictionary is of type '{0}', but this ViewDataDictionary instance requires a model item of type '{1}'. No route matches the supplied values. If an {0} provides a result value by setting the {1} property of {2} to a non-null value, then it cannot call the next filter by invoking {3}. If an {0} cancels execution by setting the {1} property of {2} to 'true', then it cannot call the next filter by invoking {3}. The partial view '{0}' was not found. The following locations were searched:{1} The view '{0}' was not found. The following locations were searched:{1}. Unable to locate an implementation of IAuthorizationService. OnAuthorization is not implemented by this filter, use OnAuthorizationAsync instead. The value must be greater than or equal to zero. The type provided to '{0}' must implement '{1}'. 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} Cannot return null from an action method with a return type of '{0}'. Value types cannot be activated by '{0}'. The type '{0}' must derive from '{1}'. No encoding found for output formatter '{0}'. There must be at least one supported encoding registered in order for the output formatter to write content. No encoding found for input formatter '{0}'. There must be at least one supported encoding registered in order for the formatter to read content. Unsupported content type '{0}'. No supported media type registered for output formatter '{0}'. There must be at least one supported media type registered in order for the output formatter to write content. The following errors occurred with attribute routing information:{0}{0}{1} {0} is the newline. {1} is the formatted list of errors using AttributeRoute_IndividualErrorMessage The attribute route '{0}' cannot contain a parameter named '{{{1}}}'. Use '[{1}]' in the route template to insert the value '{2}'. For action: '{0}'{1}Error: {2} {1} is the newline. An empty replacement token ('[]') is not allowed. Token delimiters ('[', ']') are imbalanced. The route template '{0}' has invalid syntax. {1} {1} is the specific error message. While processing template '{0}', a replacement value for the token '{1}' could not be found. Available tokens: '{2}'. A replacement token is not closed. An unescaped '[' token is not allowed inside of a replacement token. Use '[[' to escape. The value must be either '{0}' or '{1}'. Unable to find the required services. Please add all the required services by calling '{0}' inside the call to '{1}' or '{2}' in the application startup code. Two or more routes named '{0}' have different templates. Action: '{0}' - Template: '{1}' Formats an action descriptor display name and it's associated template. Attribute routes with the same name '{0}' must have the same template:{1}{2} {0} is the name of the attribute route, {1} is the newline, {2} is the list of errors formatted using ActionDescriptor_WithNamedAttributeRouteAndDifferentTemplate Error {0}:{1}{2} {0} is the error number, {1} is Environment.NewLine {2} is the error message Could not find a replacement for view expansion token '{0}'. {0} must be executed before {1} can be invoked. The result of value factory cannot be null. A method '{0}' must not define attribute routed actions and non attribute routed actions at the same time:{1}{2}{1}{1}Use 'AcceptVerbsAttribute' to create a single route that allows multiple HTTP verbs and defines a route, or set a route template in all attributes that constrain HTTP verbs. {0} is the MethodInfo.FullName, {1} is Environment.NewLine, {2} is the formatted list of actions defined by that method info. Action: '{0}' - Route Template: '{1}' - HTTP Verbs: '{2}' (none) Multiple actions matched. The following actions matched route data and had all constraints satisfied:{0}{0}{1} 0 is the newline - 1 is a newline separate list of action display names Could not find file: {0} {0} is the value for the provided path Type: '{0}' - Name: '{1}' The input was not valid. If an {0} provides a result value by setting the {1} property of {2} to a non-null value, then it cannot call the next filter by invoking {3}. If the '{0}' property is not set to true, '{1}' property must be specified. The action '{0}' has ApiExplorer enabled, but is using conventional routing. Only actions which use attribute routing support ApiExplorer. The media type "{0}" is not valid. MediaTypes containing wildcards (*) are not allowed in formatter mappings. The format provided is invalid '{0}'. A format must be a non-empty file-extension, optionally prefixed with a '.' character. The property '{0}' on controller '{1}' cannot be activated. No URL for remote validation could be found. '{0}' is invalid. The '{0}' cache profile is not defined. The model's runtime type '{0}' is not assignable to the type '{1}'.