!This program cannot be run in DOS mode.
`.rsrc
@.reloc
9QOP )UU
9v )UU
'PRH )UU
F y )UU
(8 )UU
F~ )UU
#'p )UU
+ .o^
+ .o^
% "r&a
% #r0a
% $r:a
% %rFa
% &rRa
% 'rba
% (rna
% )rxa
% 6rfb
% 7r~b
% Ar~b
% Jr$c
% Kr.c
% Lr8c
% NrHc
% OrVc
% Prdc
% Qrxc
_b`}
_b`}
i (m.
] _b`T
] _b_
] _b`T8
] _bf_T
kwD]BW
kwD];^
kwD]B^
kwD];g
p '(1<
p (1<
p (1<
p '(1<
* s
. _o^
_ @
% rR8
% rx8
% $rZ9
% 'rF:
% (r|:
% +r~;
% -r0<
% /r$=
% 0rP=
% 5r4>
% 6r`>
% ;rL?
% <rn?
% @rB@
% Er<A
% FrbA
% IrQB
% JrwB
% Nr_C
% VrSE
% WruE
% ]rGF
% ^reF
% cr'G
% drMG
% gr3H
% hrmH
% kr!I
% lraI
% pr=J
% qryJ
% tr5K
% urqK
% xr5L
% yrkL
% |ruM
% ~r=N
% *r!w
#'p )UU
Z* P*
P* Z* d* n* n*(
+ .o^
+ .o^
+*.s3`
] _b
Z~[(
Z~[(
+*.s[h
$ ( $ ((0l
a* `*
p '( q
p )( q
p +( q
p $( q
p -( q
lSystem.Resources.ResourceReader, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089#System.Resources.RuntimeResourceSet
PADPADP-p
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADhsAAAADAATwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwAC4AMAAuADAALgAxAAAAbgBvAGkAcwByAGUAVgAgAHkAbABiAG0AZQBzAHMAQQABAAgAOAAAADAALgAwAC4AMAAuADEAAABu
lSystem.Resources.ResourceReader, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089#System.Resources.RuntimeResourceSet
PADPADP
% `F:
*t!Tjw!w@
<5"f7K"
pt#s-{#
/% io%`
/6'KZ?'B
E'Z}]'O
*:(Awx(
J<)o2@)
9* Cf*W
(+>q/+
M,[rT,
$/T4_/
Rc5rGo5)
Y;O{j;``
l=lBy=
HE^YfE-
K>2$L r@L
%lPzgtP*
>T?wLT_
TbJ U,
3U:pCU
G]X(e]
=`gXD`e
<ca?Ec
dZ"2d[
}Med2geL
e&TDf/e}fw
$nQ"1n-}2n
onKqwn
]r(6]rj
z(dtzvkwz=L
@The attempted operation is not valid. The data reader is closed.
=The element in the collection parameter '{0}' cannot be null.
FThe element in the collection parameter '{0}' cannot be null or empty.
\Format of the initialization string does not conform to specification starting at index {0}.
FCalling '{0}' when the data reader is closed is not a valid operation.
+The GetSchemaTable method is not supported.
The attempted operation is not valid. The nested data reader has been implicitly closed because its parent data reader has been read or closed.
0Internal .NET Framework Data Provider error {0}.
fBuffer offset '{1}' plus the bytes available '{0}' is greater than the length of the passed in buffer.
-The DataDirectory substitute is not a string.
!Data length '{0}' is less than 0.
nThe data reader has more than one field. Multiple fields are not valid for EDM primitive or enumeration types.
The data reader is incompatible with the specified '{0}'. A member of the type, '{1}', does not have a corresponding column in the data reader with the same name.
oThe data reader is incompatible with the function mapping '{1}'. The column with the name '{0}' does not exist.
The data reader is incompatible with the specified function mapping, and the type of a row could not be determined for the type mapping.
xCannot create a value for property '{0}' of type '{1}'. Only properties of primitive or enumeration types are supported.
,The parameter data type of {0} is not valid.
9Destination buffer is not valid (size of {0}) offset: {1}
-The {0} enumeration value, {1}, is not valid.
.Invalid usage of escape delimiters '[' or ']'.
QInvalid parameter Size value '{0}'. The value must be greater than or equal to 0.
4Source buffer is not valid (size of {0}) offset: {1}
cThe query attempted to call '{0}' over a nested query, but '{0}' did not have the appropriate keys.
4The nested query does not have the appropriate keys.
Keyword not supported: '{0}'.
XThe CommandBehavior.SequentialAccess property must be specified for this command object.
DThe nested query is not supported. Operation1='{0}' Operation2='{1}'
6There was an attempt to read, but no data was present.
=No query mapping view exists for the specified set '{0}.{1}'.
At dataOffset '{0}' {2} attempt is not valid. With CommandBehavior.SequentialAccess, you may only read from dataOffset '{1}' or greater.
Attempt to read from column ordinal '{0}' is not valid. With CommandBehavior.SequentialAccess, you may only read from column ordinal '{1}' or greater.
QThe ADO.NET Data Provider you are using does not support canonical command trees.
>Unable to handle an unknown TypeCode {0} returned by Type {1}.
The Entity Framework was already using a DbConfiguration instance before an attempt was made to add an 'Loaded' event handler. 'Loaded' event handlers can only be added as part of application start up before the Entity Framework is used. See http://go.microsoft.com/fwlink/?LinkId=260883 for more information.
!The alias '{0}' was already used.
SEach alias in a schema must be unique. Alias '{0}' was already used in this schema.
zAll SSDL artifacts must target the same provider. The Provider '{0}' is different from '{1}' that was encountered earlier.
All SSDL artifacts must target the same provider. The ProviderManifestToken '{0}' is different from '{1}' that was encountered earlier.
AAll elements in a schema must be contained in the Schema element.
The EntitySet for the End '{0}' in AssociationSet '{1}'was not specified, and cannot be inferred because the EntitySet is ambiguous. More than one EntitySet could be used; an explicit End element with an EntitySet attribute must be specified.
RFunction '{0}' and {1} space type '{0}' cannot have the same fully qualified name.
qThe function call cannot be resolved, because one or more passed arguments match more than one function overload.
{Function '{0}' with the same {1} space type parameters already exists. Make sure that function overloads are not ambiguous.
The name '{0}' is ambiguous. '{0}' is defined in both the '{1}' namespace and the '{2}' namespace. To disambiguate, either use a fully qualified name or define a namespace alias.
kThe specified migration name '{0}' is ambiguous. Specify the full migration id including timestamp instead.
The string '{0}' was not in the expected format to be deserialized by the {1}. Serialized values are expected to have the format '{2}'.
^An object of type '{0}' cannot be serialized by the {1}. Only '{2}' objects can be serialized.
EThe argument '{0}' cannot be null, empty or contain only white space.
>The argument to the function must be a conceptual schema type.
1The argument to the function must be an CLR type.
{0} is out of range.
6Value {0} is not valid. Expected a non-negative value.
GThe argument types '{0}' and '{1}' are incompatible for this operation.
aDestination array was not long enough. Check arrayIndex and length, and the array's lower bounds.
pMore than one migrations configuration type was found in the assembly '{0}'. Specify the name of the one to use.
More than one migrations configuration type '{0}' was found in the assembly '{1}'. Specify the fully qualified name of the one to use.
No migrations configuration type was found in the assembly '{0}'. (In Visual Studio you can use the Enable-Migrations command from Package Manager Console to add a migrations configuration).
LThe migrations configuration type '{0}' was not found in the assembly '{1}'.
JThe assembly '{0}' specified does not exist in the assemblies enumeration.
The entity type of one of the ends of the specified association type does not match the entity type of the corresponding entity set end.
HAt least one SSDL artifact is required for creating StoreItemCollection.
Attempt to add member {0} to structural type {1} failed. Member has DataSpace {2}, structural type has DataSpace {3}. They must be the same.
'{0}' is not a valid migration. Explicit migrations must be used for both source and target when scripting the upgrade between them.
'{0}' is not a valid target migration. When targeting a previously applied automatic migration, use the full migration id including timestamp.
Automatic migration was not applied because it would result in data loss. Set AutomaticMigrationDataLossAllowed to 'true' on your DbMigrationsConfiguration to allow application of automatic migrations even if they might cause data loss. Alternately, use Update-Database with the '-Force' option, or scaffold an explicit migration.
Unable to update database to match the current model because there are pending changes and automatic migration is disabled. Either write the pending model changes to a code-based migration or enable automatic migration. Set DbMigrationsConfiguration.AutomaticMigrationsEnabled to true to enable automatic migration.
AutomaticMigration
Could not apply auto-migration '{0}' because it includes modification function creation operations. When using auto-migrations, modification function creation operations are only supported when migrating to the current model.
nThe annotation name '{0}' is not valid. Annotation names have the same restrictions as C# and EDM identifiers.
Unexpected connection state. When using a wrapping provider ensure that the StateChange event is implemented on the wrapped DbConnection.
The type '{0}' passed to DbConfiguration.LoadConfiguration does not derive from DbContext. Only DbContext types can be used for DbConfiguration discovery.
The foreign key column name '{0}' specified for the '{1}' annotation is not valid. The column name to annotate must match a column name set using the MapKey method.
!Unknown namespace or alias ({0}).
NavigationProperty '{0}' is not valid. Type '{1}' of FromRole '{2}' in AssociationType '{3}' must exactly match with the type '{4}' on which this NavigationProperty is declared on.
;NavigationProperty is not valid. {0} is not a Relationship.
FNavigationProperty is not valid. The FromRole and ToRole are the same.
QNavigationProperty is not valid. The role {0} is not defined in Relationship {1}.
The parameter {0} in function '{1}' in schema '{2}' has an invalid parameter direction {3}. Valid parameter directions are: In, Out, and InOut.
The parameter {0} in function '{1}' in schema '{2}' has an invalid parameter direction {3}. The only valid value for this parameter is In.
kPrecision and Scale combination is not valid. Precision ({0}) must be greater than or equal to Scale ({1}).
Both property '{0}' on type '{1}' and property '{2}' on type '{3}' map to column '{4}' on table '{5}' but the configuration of the column for property '{1}.{0}' is incompatible with the configuration of the column for property '{3}.{2}'. The column type and configuration must be the same for all properties that map to a given column in a TPH table. {6}
The base type '{0}' must be mapped to functions because its derived type '{1}' is mapped to functions. When mapping an inheritance hierarchy to functions, ensure that the root type of the hierarchy is also mapped to functions.
NThe upper and lower limits of the BETWEEN expression cannot be un-typed nulls.
UThe BETWEEN lower limit type '{0}' is not compatible with the upper limit type '{1}'.
[The BETWEEN lower limit type '{0}' is not order-comparable with the upper limit type '{1}'.
WThe BETWEEN value type '{0}' is not order-comparable with the limits common type '{1}'.
BootstrapMigration
tBoth minimum and maximum values must be provided for '{0}' in type '{1}' since '{0}' is not specified as a constant.
The value of the calculated enumeration type member is not valid according to its data type 'http://www.w3.org/2001/XMLSchema:long'.
The generic 'Set' method cannot be called with a proxy type. Either use the actual entity type or call the non-generic 'Set' method.
The function or function import '{0}' is not composable. A non-composable function or function import cannot be called in a query expression.
RCannot convert literal '{0}' to '{1}'. Numeric literal specification is not valid.
Cannot create an empty multiset.
*A multiset of un-typed NULLs is not valid.
ACannot define key members on both the base and the derived types.
You cannot use Ignore method on the property '{0}' on type '{1}' because this type inherits from the type '{2}' where this property is mapped. To exclude this property from your model, use NotMappedAttribute or Ignore method on the base type.
G'{0}' cannot be instantiated because it is defined as an abstract type.
kAll artifacts loaded into an ItemCollection must have the same version. Multiple versions were encountered.
7'{0}' cannot be resolved into a valid type or function.
SCannot set the base type '{0}' on type '{1}' because it creates cyclic inheritance.
Q'{0}' is a system namespace and cannot be used as an Alias. Use some other Alias.
<Argument '{0}' is not valid. The set contains a null value.
_A circular ComplexType hierarchy was detected. Self-referencing ComplexTypes are not supported.
Using the same DbCompiledModel to create contexts against different types of database servers is not supported. Instead, create a separate DbCompiledModel for each type of server being used.
The type '{0}' was not mapped. Check that the type has not been explicitly excluded by using the Ignore method or NotMappedAttribute data annotation. Verify that the type was defined as a class, is not primitive or generic, and does not inherit from ComplexObject.
1The class '{0}' has no parameterless constructor.
,Properties are not supported on value types.
%Indexed properties are not supported.
$Static properties are not supported.
#The property getter does not exist.
#The property setter does not exist.
&The property uses an unsupported type.
QThe '{0}' collection used in the call to '{1}' must contain at least one element.
The RelatedEnd with role name '{0}' from relationship '{1}' has already been loaded. This can occur when using a NoTracking merge option. Try using a different merge option when querying for the related object.
An EntityCollection of {0} objects could not be returned for role name '{1}' in relationship '{2}'. Make sure that the EdmRelationshipAttribute that defines this relationship has the correct RelationshipMultiplicity for this role name. For more information, see the Entity Framework documentation.
TThe Load method cannot return the {0} when the related object is in a deleted state.
The source query for this EntityCollection or EntityReference cannot be returned when the related object is in either an added state or a detached state and was not originally retrieved using the NoTracking merge option.
WThe relationship '{0}' does not match any relationship defined in the conceptual model.
A navigation property that returns an EntityCollection cannot be changed if the existing EntityCollection contains items that are not in the new EntityCollection.
%-- Executing asynchronously at {0}{1}
-- Canceled in {0} ms{1}
*-- Completed in {0} ms with result: {1}{2}
&-- Failed in {0} ms with error: {1}{2}
-- Executing at {0}{1}
KFunctions declaring command text cannot also declare a store function name.
4Functions declaring command text cannot be composed.
An error was reported while committing a database transaction but it could not be determined whether the transaction succeeded or failed on the database server. See the inner exception and http://go.microsoft.com/fwlink/?LinkId=313468 for more information.
The specified parameter '{0}' of type '{1}' is not valid. Only scalar parameters (such as Int32, Decimal, and Guid) are supported.
The specified use of parameter '{0}' to produce a value of type '{1}' is not supported by LINQ to Entities in a compiled query.
yThe specified parameter type '{0}' is not valid. Only scalar parameters (such as Int32, Decimal, and Guid) are supported.
The property '{0}' could not be reported as changing. This occurred because EntityComplexMemberChanging was called with a property name that is not a complex property. For more information, see the Entity Framework documentation.
:This complex object is already attached to another object.
ZNullable complex types are not supported. The complex property '{0}' must not allow nulls.
oThe function import '{0}' cannot have ComplexType ReturnType '{1}' and an EntitySet specified at the same time.
Nested ComplexType property '{0}' in the ReturnType '{1}' of the function '{2}' is not supported, please consider flattening the nested ComplexType property.
jThe type '{0}' has already been configured as an entity type. It cannot be reconfigured as a complex type.
=Mapping function imports returning entities is not supported.
OFunctions and function imports that can be composed must declare a return type.
XThere is no underlying support for the '+' operation on strings in the current provider.
Type '{0}' is derived from the type '{1}' that is the type for EntitySet '{2}'. Type '{0}' defines new concurrency requirements that are not allowed for sub types of base EntitySet types.
A second operation started on this context before a previous asynchronous operation completed. Use 'await' to ensure that any asynchronous operations have completed before calling another method on this context. Any instance members are not guaranteed to be thread safe.
The call to DbConfiguration.{0} failed because the configuration is locked. The protected methods and properties of DbConfiguration are intended to be called only from the constructor of a class derived from DbConfiguration and cannot be called after the DbConfiguration object is in use.
The default DbConfiguration instance was used by the Entity Framework before the '{0}' type was discovered. An instance of '{0}' must be set at application start before using any Entity Framework features or must be registered in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=260883 for more information.
An instance of '{0}' cannot be set because an instance of '{1}' is already being used. Only one DbConfiguration type can be used in an application. See http://go.microsoft.com/fwlink/?LinkId=260883 for more information.
The index with name '{0}' on table '{1}' has conflicting configuration for different columns in the index. All configuration for a given index on a given table must be consistent: {2}
NCustom annotation '{0}' = '{1}' conflicts with custom annotation '{0}' = '{2}'
The navigation property '{0}' declared on type '{1}' has been configured with conflicting cascade delete operations using 'WillCascadeOnDelete'.
VConflicting configuration settings were specified for column '{0}' on table '{1}': {2}
"{0} = {1} conflicts with {2} = {3}
gThe navigation property '{0}' declared on type '{1}' has been configured with conflicting foreign keys.
The navigation property '{0}' declared on type '{1}' has been configured with conflicting modification function mapping information.
dIndexAttributes with name '{0}' cannot be merged because they contain conflicting configuration: {1}
IndexAttributes with identity '{0}' and name '{1}' cannot be merged because they ambiguously match multiple, conflicting IndexAttributes.
\Index attribute property '{0}' = '{1}' conflicts with index attribute property '{0}' = '{2}'
Property '{0}' on type '{1}' is attributed with two IndexAttributes with name '{2}' that contain conflicting configuration: {3}
Values of incompatible types ('{1}' and '{2}') were assigned to the '{0}' discriminator column. Values of the same type must be specified. To explicitly specify the type of the discriminator column use the HasColumnType method.
nThe navigation property '{0}' declared on type '{1}' has been configured with conflicting mapping information.
iThe navigation property '{0}' declared on type '{1}' has been configured with conflicting multiplicities.
WConflicting configuration settings were specified for property '{0}' on type '{1}': {2}
Annotation '{0}' value '{1}' conflicts with value '{2}' for table '{3}'. Annotations of a given name configured for a given table must be specified only once or have matching values in each configuration.
4Failed to close connection at {0} with error: {1}{2}
Closed connection at {0}{1}
Disposed connection at {0}{1}
#Cancelled open connection at {0}{1}
3Failed to open connection at {0} with error: {1}{2}
BFailed to open connection asynchronously at {0} with error: {1}{2}
Opened connection at {0}{1}
*Opened connection asynchronously at {0}{1}
1Facet '{0}' must not be specified for type '{1}'.
Configuration for DbContext type '{0}' is specified multiple times in the application configuration. Each context can only be configured once.
The type '{0}' does not inherit from DbContext. Context factories can only be registered for context types that inherit from DbContext.
{The target context '{0}' is not constructible. Add a default constructor or provide an implementation of IDbContextFactory.
vUnable to add the convention '{0}'. Could not find an existing convention of type '{1}' in the current convention set.
The specified convention '{0}' cannot be added before or after '{1}'. Both conventions must share the same base class (Convention) or implement the same interface (IConceptualModelConvention<T> or IStoreModelConvention<T>).
The specified convention of type '{0}' is not a valid convention. Conventions must derive from Convention or implement IStoreConvention or IConceptualConvention.
'{0}' could not be resolved in the current scope or context. Make sure that all referenced variables are in scope, that required schemas are loaded, and that namespaces are referenced correctly.
.The specified aggregate function is not valid.
>DbAndExpression requires arguments with a common Boolean type.
ODbApplyExpression input and apply arguments cannot have the same variable name.
<The unsigned type '{0}' cannot be promoted to a signed type.
ADbArithmeticExpression arguments must have a numeric common type.
>{0} requires arguments with compatible collection ResultTypes.
NDbExpressionBinding requires an input expression with a collection ResultType.
bA valid ResultType could not be inferred from the ResultTypes of the specified 'Then' expressions.
KDbCaseExpression requires an equal number of 'When' and 'Then' expressions.
AThe requested cast is not allowed: from type '{0}' to type '{1}'.
The DataSpace is not valid.
1The specified parameter name is not valid: '{0}'.
@DbComparisonExpression requires arguments with comparable types.
ZThe type '{0}' does not match the EDM enumeration type '{1}' or its underlying type '{2}'.
Only enumeration or primitive types may be used as constant value types. DbConstantExpression cannot be created using an instance of type '{0}'.
@The specified value is not an instance of a valid constant type.
5The specified value is not an instance of type '{0}'.
uA relationship end named '{0}' is not declared by the relationship type '{1}' from the destination MetadataWorkspace.
NThe EntityContainer '{0}' was not found in the destination MetadataWorkspace.
LThe EntitySet '{0}.{1}' was not found in the destination MetadataWorkspace.
FThe function '{0}' was not found in the destination MetadataWorkspace.
lA navigation property named '{0}' is not declared by the type '{1}' from the destination MetadataWorkspace.
aA property named '{0}' is not declared by the type '{1}' from the destination MetadataWorkspace.
BThe destination MetadataWorkspace does not contain the type '{0}'.
3DbCrossJoinExpression requires at least two inputs.
The specified DbCrossJoinExpression inputs contain expression bindings with a duplicate variable name, '{2}'. The first occurrence is at index {0}, the second is at index {1}.
;DbDerefExpression requires an argument of a reference type.
bThe 'Distinct' operation cannot be applied to the collection ResultType of the specified argument.
When unwrapSingleProperty is specified the argument expression must have the following ResultType: a CollectionType with a structured element type that declares exactly one property.
(The specified command tree is not valid.
The ResultType of the specified expression is not compatible with the required type. The expression ResultType is '{0}' but the required type is '{1}'.
8The expression list has an incorrect number of elements.
NThe specified relationship ends are not defined by the same relationship type.
The method result type '{0}' is not supported for this method argument. A method that produces an instance of a DbExpression-derived type or an anonymous type with DbExpression-derived properties is required.
The specified element expressions cannot be contained by the same collection because no common element type can be inferred from their ResultTypes.
NThe specified relationship type does not define an end with the specified name
]The specified argument result types matched more than one overload of the function 'Edm.{0}'.
JNo function named 'Edm.{0}' having the specified argument types was found.
KFunction metadata used in DbFunctionExpression cannot include command text.
Function metadata used in DbFunctionExpression must allow composition. Non-composable functions or functions that include command text are not allowed in expressions. Such functions can only be executed independently.
NFunction metadata used in DbFunctionExpression cannot have a void return type.
BThe specified metadata cannot be used because it is not read-only.
SThe current provider does not support any type that is compatible with Edm.Boolean.
QThe current provider does not support any type that is compatible with Edm.Int32.
RThe current provider does not support any type that is compatible with Edm.String.
m{0} requires an expression argument with a polymorphic result type that is compatible with the type argument.
.The specified type is not polymorphic: '{0}'.
0The expression '{0}' is of an unsupported type.
<DbEntityRefExpression requires an argument of an EntityType.
<DbRefKeyExpression requires an argument of a reference type.
SDbGroupExpressionBinding requires an input expression with a collection ResultType.
jAn aggregate named '{0}' cannot be used because the specified group keys include a key with the same name.
0At least one group key or aggregate is required.
nThe specified group key is not valid because equality comparison cannot be performed on its ResultType: '{0}'.
aAt most one DbGroupAggregate can be specified in the list of aggregates of a DbGroupByExpression.
GDbInExpression requires the same result type for the input expressions.
6A collection of '{0}' is not a valid argument for {1}.
PThe argument to DbIsNullExpression cannot have a CollectionType of a ResultType.
\The argument to DbIsNullExpression must refer to a primitive, enumeration or reference type.
VThe left and right arguments of a DbJoinExpression cannot have the same variable name.
ILimit must be a DbConstantExpression or a DbParameterReferenceExpression.
&Limit must have an integer ResultType.
%Limit must have a non-negative value.
iThe specified member is not associated with the same MetadataWorkspace or data space as the command tree.
^The specified EntitySet is not valid because its EntityContainer property has a value of null.
mThe specified EntitySet is not associated with the same MetadataWorkspace or data model as the command tree.
QThe specified EntityType is not valid because its KeyMembers collection is empty.
ZThe specified EntityType is not valid because its KeyMembers property has a value of null.
kThe specified function is not associated with the same MetadataWorkspace or data space as the command tree.
uThe specified function parameter is not associated with the same MetadataWorkspace or data model as the command tree.
]The specified function is not valid because its ReturnParameter property has a value of null.
gThe specified type is not associated with the same MetadataWorkspace or data model as the command tree.
MDbNewInstanceExpression cannot create an instance of the abstract type '{0}'.
ODbNewInstanceExpression cannot create an instance of the memberless type '{0}'.
A CollectionType is required.
The specified related entity is not compatible with this new instance constructor. The constructed instance is not an instance of the EntityType required by the source end of the related entity.
-A collection, entity or row type is required.
9DbNotExpression requires an argument with a Boolean type.
=DbOrExpression requires arguments with a common Boolean type.
OAn Instance property of type DbExpression is required for an instance property.
mDbRefExpression requires an EntityType from the same hierarchy as the EntityType of the referenced EntitySet.
6Navigating composition relationships is not supported.
^The specified navigation requires a navigation source of a type that is compatible with '{0}'.
}The specified target relationship End is not declared by the same relationship type as the specified source relationship End.
bA target relationship End with multiplicity of 'One' or 'ZeroOrOne' is required for this argument.
QThe specified target relationship End is the same as the source relationship End.
The specified target entity reference expression is not valid because it does not produce a reference to an entity of the same type or of a subtype of the EntityType referred to by the specified target End.
HThe target entity reference expression must have a reference ResultType.
ICount must be a DbConstantExpression or a DbParameterReferenceExpression.
&Count must have an integer ResultType.
%Count must have a non-negative value.
LA collation specifier is only valid for a sort key with a string ResultType.
CDbSortClause expressions must have a type that is order comparable.
hAn error occurred while preparing definition of the function '{0}'. See the inner exception for details.
The result type '{0}' specified in the declaration of the function '{1}' does not match the result type '{2}' of the function definition.
Definition of the function '{0}' contains a direct or indirect reference to itself. Recursive function definitions are not supported.
|The function '{0}' has no defining expression. A user-defined function needs a defining expression for successful execution.
#{0} requires a collection argument.
`The name '{2}' was specified twice, at index {0} and index {1}. Duplicate names are not allowed.
5An empty list is not a valid value for this argument.
nThe specified expression contains multiple references to the parameter '{0}' that have different result types.
^The specified expression contains {0} metadata from a data space other than the target, '{1}'.
`The specified expression contains {0} metadata from a workspace other than the target workspace.
BThe referenced variable '{0}' is not defined in the current scope.
xThe ResultType of the referenced variable '{0}' does not match the type specified in this variable reference expression.
An instance of '{0}' could not be created because it does not define a parameterless constructor. Every type derived from EntityTypeConfiguration in an assembly must have a parameterless constructor when using AddFromAssembly to add Code First configurations from that assembly.
GFailed to create instance of type '{0}'. The type must not be abstract.
vThe type '{0}' does not inherit from '{1}'. Entity Framework code-based configuration classes must inherit from '{1}'.
bThe type '{0}' does not inherit from '{1}'. Migrations configuration types must extend from '{1}'.
lThe type '{0}' does not inherit from '{1}'. Migrations SQL generator implementations must extend from '{1}'.
FFailed to create instance of type '{0}'. The type must not be generic.
_Failed to create instance of type '{0}'. The type must have a public parameterless constructor.
[The CREATEREF type '{0}' is not a sub-type or super-type of the EntitySet EntityType '{1}'.
]The CREATEREF type must specify an EntityType. The type specification '{0}' represents '{1}'.
aliased expression
aliased namespace import
logical AND expression
ANYELEMENT expression
APPLY clause
BETWEEN expression
CASE expression
CASE/ELSE expression
CASE/WHEN/THEN expression
CAST expression
collated ORDER BY clause item
collection type definition
command expression
CREATEREF expression
DEREF expression
division operation
ELEMENT expression
equals expression
escaped identifier
EXCEPT expression
EXISTS expression
expression list
FLATTEN expression
FROM/APPLY clause
FROM clause
FROM clause item
FROM clause list
FROM/JOIN clause
function '{0}()'
function definition
greater than expression
!greater than or equals expression
GROUP BY clause
GROUPPARTITION expression
HAVING predicate
identifier
IN set expression
INTERSECT expression
IS NOT NULL expression
IS NOT OF expression
IS NULL expression
IS OF expression
JOIN clause
JOIN/ON clause
KEY expression
less than expression
less than or equals expression
LIKE expression
ORDER BY/LIMIT sub-clause
constant literal
member access expression
$function, method or type constructor
subtraction operation
modulus operation
multiplication operation
MULTISET constructor
namespace import
namespace import list
NAVIGATE expression
logical NOT expression
NOT BETWEEN expression
not equals expression
NOT IN set expression
NOT LIKE expression
NULL literal
OFTYPE expression
OFTYPE ONLY expression
logical OR expression
ORDER BY clause
ORDER BY clause item
OVERLAPS expression
parenthesized expression
addition operation
query expression
query statement
REF expression
reference type definition
RELATIONSHIP expression
RELATIONSHIP expression list
ROW constructor
row type definition
SELECT clause
SELECT VALUE clause
SET expression
simple identifier
ORDER BY/SKIP sub-clause
TOP sub-clause
TREAT expression
type '{0}' constructor
type name
+type name with type specification arguments
unary minus operation
unary plus operation
UNION expression
UNION ALL expression
WHERE predicate
4A cycle was detected in the type hierarchy of '{0}'.
Update
The model backing the '{0}' context has changed since the database was created. Consider using Code First Migrations to update the database (http://go.microsoft.com/fwlink/?LinkId=238269).
The DbContextDatabaseInitializer entry 'key="{0}" value="{1}"' in the application configuration is not valid. Entries should be of the form 'key="DatabaseInitializerForType MyNamespace.MyDbContextClass, MyAssembly" value="MyNamespace.MyInitializerClass, MyAssembly"' or 'key="DatabaseInitializerForType MyNamespace.MyDbContextClass, MyAssembly" value="Disabled"'. Consider using the <entityFramework> configuration section to set the database initializer (http://go.microsoft.com/fwlink/?LinkID=237468).
;Database '{0}' cannot be created because it already exists.
ZAn exception occurred while initializing the database. See the InnerException for details.
Failed to set database initializer of type '{0}' for DbContext type '{1}' specified in the application configuration. See inner exception for details.
Failed to set database initializer of type '{0}' for DbContext type '{1}' specified in the application configuration. Entries should be of the form 'key="DatabaseInitializerForType MyNamespace.MyDbContextClass, MyAssembly" value="MyNamespace.MyInitializerClass, MyAssembly"' or 'key="DatabaseInitializerForType MyNamespace.MyDbContextClass, MyAssembly" value="Disabled"'. Also verify that 'DatabaseInitializerArgumentForType' entries are present for every parameter of the database initializer constructor. See inner exception for details. Consider using the <entityFramework> configuration section to set the database initializer (http://go.microsoft.com/fwlink/?LinkID=237468).
Model compatibility cannot be checked because the database does not contain model metadata. Model compatibility can only be checked for databases created using Code First or Code First Migrations.
Model compatibility cannot be checked because the DbContext instance was not created using Code First patterns. DbContext instances created from an ObjectContext or using an EDMX file cannot be checked for compatibility.
The collection navigation property '{0}' on the entity of type '{1}' cannot be set because the entity type does not define a navigation property with a set accessor.
The DbConfiguration type '{0}' specified in the DbConfigurationTypeAttribute constructor could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260883 for more information.
The DbConfiguration type '{0}' specified in the application config file could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260883 for more information.
ONo connection string named '{0}' could be found in the application config file.
The context factory type '{0}' does not have a public parameterless constructor. Either add a public parameterless constructor, create an IDbContextFactory implementation in the context assembly, or register a context factory using DbConfiguration.
<The DbConnectionFactory instance returned a null connection.
Cannot initialize a DbContext from an entity connection string or an EntityConnection instance together with a DbCompiledModel. If an entity connection string or EntityConnection instance is used, then the model will be created from the metadata in the connection. If a DbCompiledModel is used, then the connection supplied should be a standard database connection (for example, a SqlConnection instance) rather than an entity connection.
ONo connection string named '{0}' could be found in the application config file.
The context cannot be used while the model is being created. This exception may be thrown if the context is used inside the OnModelCreating method or if the same context instance is accessed by multiple threads concurrently. Note that instance members of DbContext and related classes are not guaranteed to be thread safe.
JThe operation cannot be completed because the DbContext has been disposed.
An error occurred while saving entities that do not expose foreign key properties for their relationships. The EntityEntries property will return null because a single entity cannot be identified as the source of the exception. Handling of exceptions while saving can be made easier by exposing foreign key properties in your entity types. See the InnerException for details.
The transaction passed in is not associated with the current connection. Only transactions associated with the current connection may be used.
The transaction passed in must have a non-null connection. A null connection indicates the transaction has already been completed.
^The DbContext class cannot be used with models that have multiple entity sets per type (MEST).
zThe connection string '{0}' in the application's configuration file does not contain the required providerName attribute."
0The provider factory returned a null connection.
The connection is already enlisted in a user transaction. The first transaction should be completed before attempting to engage the connection in another transaction.
The connection is already participating in a transaction. The first transaction should be committed or rolled back before attempting to engage the connection in another transaction.
No '{0}' instance was passed to the IDbDependencyResolver.GetService method. A '{0}' instance must be supplied when attempting to resolve an '{1}' dependency.
No name was passed to the IDbDependencyResolver.GetService method. The provider invariant name must be supplied when attempting to resolve a '{0}' dependency.
XThe expression passed to method {0} must represent a property defined on the type '{1}'.
"The property '{0}' from the property path '{1}' is not a complex property on type '{2}'. Property paths must be composed of complex properties for all except the final property."
"The property path '{0}' cannot be used for navigation properties. Property paths can only be used to access primitive or complex properties."
The property '{0}' on type '{1}' is not a complex property. The ComplexProperty method can only be used with complex properties. Use the Property, Reference or Collection method.
The property '{0}' on type '{1}' is not a navigation property. The Reference and Collection methods can only be used with navigation properties. Use the Property or ComplexProperty method.
The property '{0}' on type '{1}' is not a primitive property, complex property, collection navigation property, or reference navigation property.
The property '{0}' on type '{1}' is not a primitive or complex property. The Property method can only be used with primitive or complex properties. Use the Reference or Collection method.
Member '{0}' cannot be called for the entity of type '{1}' because the entity does not exist in the context. To add an entity to the context call the Add or Attach method of DbSet<{1}>.
The property '{0}' on type '{1}' is a reference navigation property. The Reference method should be used instead of the Collection method.
The property '{0}' on type '{1}' is a collection navigation property. The Collection method should be used instead of the Reference method.
The generic type argument '{0}' cannot be used with the Member method when accessing the collection navigation property '{1}' on entity type '{2}'. The generic type argument '{3}' must be used instead.
The navigation property '{0}' on entity type '{1}' cannot be used for entities of type '{2}' because it refers to entities of type '{3}'.
The property '{0}' on entity type '{1}' cannot be used for objects of type '{2}' because it is a property for objects of type '{3}'.
cValidation failed for one or more entities. See 'EntityValidationErrors' property for more details.
JCannot create a {0}<{1}> from a non-generic {0} for objects of type '{2}'.
The Include path expression must refer to a navigation property defined on the type. Use dotted paths for reference navigation properties and the Select operator for collection navigation properties.
[The specified DbMappingViewCacheFactory has failed to create a DbMappingViewCache instance.
The DbMappingViewCache type '{0}' specified in the DbMappingViewCacheTypeAttribute constructor could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application.
The context type '{0}' must derive from the System.Data.Entity.DbContext type or the System.Data.Entity.Core.Objects.ObjectContext type.
oMultiple instances of DbMappingViewCacheTypeAttribute that specify the same context type '{0}' are not allowed.
lCannot create a {0}<{1}, {2}> from a non-generic {0} for entities of type '{3}' with property of type '{4}'.
The type '{0}' does not inherit from DbContext. The DbMigrationsConfiguration.ContextType property must be set to a type that inherits from DbContext.
The 'MigrationsDirectory' property of 'DbMigrationsConfiguration' was set to the absolute path '{0}'. The migrations directory must be set to a relative path for a sub-directory under the Visual Studio project root.
QThe context type '{0}' must have a public constructor taking an EntityConnection.
*Input, output, or bidirectional parameter.
5Size of variable length data types (string & arrays).
When used by a DataAdapter.Update, the source column name that is used to find the DataSetColumn name in the ColumnMappings. This is to copy a value between the parameter and a data row.
When used by a DataAdapter.Update (UpdateCommand only), the version of the DataRow value that is used to update the data source.
gCannot get value for property '{0}' from entity of type '{1}' because the property has no get accessor.
eCannot set value for property '{0}' on entity of type '{1}' because the property has no set accessor.
Member '{0}' cannot be called for property '{1}' because the entity of type '{2}' does not exist in the context. To add an entity to the context call the Add or Attach method of DbSet<{2}>.
Member '{0}' cannot be called for property '{1}' on entity of type '{2}' because the property is not part of the Entity Data Model.
Cannot set value for property '{0}' on entity of type '{1}' because the property has no set accessor and is in the '{2}' state.
{A property of a complex type must be set to an instance of the generic or non-generic DbPropertyValues class for that type.
]Cannot copy values from DbPropertyValues for type '{0}' into DbPropertyValues for type '{1}'.
hCannot copy from property values for object of type '{0}' into property values for object of type '{1}'.
The property '{0}' in the entity of type '{1}' is null. Store values cannot be obtained for an entity with a null complex property.
1{0} cannot be used for entities in the {1} state.
UCannot set non-nullable property '{0}' of type '{1}' to null on object of type '{2}'.
zCannot set the value of the nested property '{0}' because value of the complex property '{1}' to which it belongs is null.
Cannot set the original value of the nested property '{0}' because the original value of the complex property '{1}' to which it belongs is null.
The value of the complex property '{0}' on entity of type '{1}' is null. Complex properties cannot be set to null and values cannot be set for null complex properties.
The value of the nested property values property '{0}' on the values for entity of type '{1}' is null. Nested property values cannot be set to null and values cannot be set for null complex properties.
FThe '{0}' property does not exist or is not mapped for the type '{1}'.
-The set of property value names is read-only.
dCannot assign value of type '{0}' to property '{1}' of type '{2}' in property values for type '{3}'.
Data binding directly to a store query (DbSet, DbQuery, DbSqlQuery, DbRawSqlQuery) is not supported. Instead populate a DbSet with data, for example by calling Load on the DbSet, and then bind to local data. For WPF bind to DbSet.Local. For WinForms bind to DbSet.Local.ToBindingList(). For ASP.NET WebForms you can bind to the result of calling ToList() on the query or use Model Binding, for more information see http://go.microsoft.com/fwlink/?LinkId=389592.
Cannot call the {0} method for an entity of type '{1}' on a DbSet for entities of type '{2}'. Only entities of type '{2}' or derived from type '{2}' can be added, attached, or removed.
Cannot call the Create method for the type '{0}' on a DbSet for entities of type '{1}'. Only entities of type '{1}' or derived from type '{1}' can be created.
The type '{0}' is mapped as a complex type. The Set method, DbSet objects, and DbEntityEntry objects can only be used with entity types, not complex types.
EThe entity type {0} is not part of the model for the current context.
XMultiple entities were found in the Added state that match the given primary key values.
The type '{0}' is not attributed with EdmEntityTypeAttribute but is contained in an assembly attributed with EdmSchemaAttribute. POCO entities that do not use EdmEntityTypeAttribute cannot be contained in the same assembly as non-POCO entities that use EdmEntityTypeAttribute.
JThe entity found was of type {0} when an entity of type {1} was requested.
xThe type of one of the primary key values did not match the type defined in the entity. See inner exception for details.
fThe number of primary key values passed must match number of primary key values defined on the entity.
~An unexpected exception was thrown during validation of '{0}' when invoking {1}.Validate. See the inner exception for details.
}An unexpected exception was thrown during validation of '{0}' when invoking {1}.IsValid. See the inner exception for details.
QThe DEREF argument must be a reference type. The passed argument is a '{0}' type.
The default DbConfiguration instance was used by the Entity Framework before an attempt was made to set an instance of '{0}'. The '{0}' instance must be set at application start before using any Entity Framework features or must be registered in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=260883 for more information.
@Default values are allowed only for non-spatial primitive types.
The {0} could not be registered with the MetadataWorkspace because its version ('{1}') is different from the version ('{2}') already associated with the MetadataWorkspace.
JScripting the downgrade between two specified migrations is not supported.
-Annotation '{0}' is already defined in '{1}'.
|The configured column orders for the table '{0}' contains duplicates. Ensure the specified column order values are distinct.
$The End Name {0} is already defined.
cEach member name in an EntityContainer must be unique. A member with name '{0}' is already defined.
The EntitySet '{0}' with schema '{1}' and table '{2}' was already defined. Each EntitySet must refer to a unique schema and table.
.Enumeration members have to have unique names.
WA member named {0} cannot be defined in class {1}. It is defined in ancestor class {2}.
Each member name in an EntityContainer must be unique. The member '{0}' is already defined in EntityContainer '{1}'. Because EntityContainer '{2}' extends EntityContainer '{1}', you cannot have a member with the same name in EntityContainer '{2}'.
Duplicate parameter name: {0}
oKey specified in EntityType '{0}' is not valid. Property '{1}' is referenced more than once in the Key element.
A configuration for type '{0}' has already been added. To reference the existing configuration use the Entity<T>() or ComplexType<T>() methods.
The parameters of Function '{0}' are converted to conceptual side type '{1}', and the function with the same conceptual side type parameters already exists. Please make sure that function overloads are not ambiguous.
wThe inline function '{0}' with the same parameters already exists. Make sure that function overloads are not ambiguous.
1Only one {0} element is allowed per relationship.
The Entity Framework provider type '{0}' did not have a static property or field named 'Instance'. Entity Framework providers must declare a static property or field named 'Instance' that returns the singleton instance of the provider.
No Entity Framework provider found for the ADO.NET provider with invariant name '{0}'. Make sure the provider is registered in the 'entityFramework' section of the application config file. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information.
The 'Instance' member of the Entity Framework provider type '{0}' did not return an object that inherits from 'System.Data.Entity.Core.Common.DbProviderServices'. Entity Framework providers must inherit from this class and the 'Instance' member must return the singleton instance of the provider. This may be because the provider does not support Entity Framework 6 or later; see http://go.microsoft.com/fwlink/?LinkId=260882 for more information.
The Entity Framework provider type '{0}' registered in the application config file for the ADO.NET provider with invariant name '{1}' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information.
Anonymous type
Closure type
nCalling the CreateOrderedEnumerable generic method on the result of a LINQ to Entities query is not supported.
*A cycle was detected in a LINQ expression.
The specified method '{0}' on the type '{1}' cannot be translated into a LINQ to Entities store expression because its return type does not match the return type of the function specified by its DbFunction attribute.
8This function can only be invoked from LINQ to Entities.
rLINQ to Entities query expressions can only be constructed from instances that implement the IQueryable interface.
BThe argument type, '{0}', is not the same as the enum type '{1}'."
'{0}' is not a valid metadata type for type filtering operations. Type filtering is only valid on entity types and complex types.
pThis method supports the LINQ to Entities infrastructure and is not intended to be used directly from your code.
.The member '{0}' is not a property or a field.
8Property indexers are not supported in LINQ to Entities.
The method 'Skip' is only supported for sorted input in LINQ to Entities. The method 'OrderBy' must be called before the method 'Skip'.
]The ThenBy method must follow either the OrderBy method or another call to the ThenBy method.
UThe parameter '{0}' was not bound in the specified LINQ to Entities query expression.
~A navigation property of type '{0}' is not valid. '{1}' or a single implementation of '{2}' was expected, but '{3}' was found.
#Unknown LINQ binding of type '{0}'.
&Unknown LINQ expression of type '{0}'.
The specified type member '{0}' is not supported in LINQ to Entities. Only initializers, entity members, and entity navigation properties are supported.
jThe specified LINQ expression of type '{0}' cannot be translated into a LINQ to Entities store expression.
kThe specified member '{0}' on the type '{1}' cannot be translated into a LINQ to Entities store expression.
kThe specified method '{0}' on the type '{1}' cannot be translated into a LINQ to Entities store expression.
The specified method '{0}' on the type '{1}' cannot be translated into a LINQ to Entities store expression because one or more passed arguments match more than one function overload.
The specified method '{0}' on the type '{1}' cannot be translated into a LINQ to Entities store expression because no overload matches the passed arguments.
The specified LINQ expression of type '{0}' cannot be translated into a valid provider-specific LINQ to Entities store expression equivalent.
The specified member '{0}' on the type '{1}' cannot be translated into a valid provider-specific LINQ to Entities store expression equivalent.
iThe method '{0}' is only supported in LINQ to Entities when the argument is a string variable or literal.
nIn constructors and initializers, only property or field parameter bindings are supported in LINQ to Entities.
wUnable to cast the type '{0}' to type '{1}'. LINQ to Entities only supports casting EDM primitive or enumeration types.
Casting to Decimal is not supported in LINQ to Entities queries, because the required precision and scale information cannot be inferred.
nCannot compare elements of type '{0}'. Only primitive types, enumeration types and entity types are supported.
yUnable to create a constant value of type '{0}'. Only primitive types or enumeration types are supported in this context.
SOnly parameterless constructors and initializers are supported in LINQ to Entities.
iThe specified LINQ expression contains references to queries that are associated with different contexts.
[A type that implements IEnumerable '{0}' cannot be initialized in a LINQ to Entities query.
IThe LINQ expression node type '{0}' is not supported in LINQ to Entities.
The type '{0}' appears in two structurally incompatible initializations within a single LINQ to Entities query. A type can be initialized in two places in the same query, but only if the same properties are set in both places and those properties are set in the same order.
bThe method 'Include' is only supported by LINQ to Entities when the argument is a string constant.
TOnly list initializer items with a single element are supported in LINQ to Entities.
The '{0}' expression with an input of type '{1}' and a check of type '{2}' is not supported. Only entity types and complex types are supported in LINQ to Entities queries.
jThe key selector type for the call to the '{0}' method is not comparable in the underlying store provider.
gThe method 'MergeAs' is only supported by LINQ to Entities when the argument is a MergeOption constant.
zLINQ to Entities does not recognize the method '{0}' method, and this method cannot be translated into a store expression.
xThe method '{0}' cannot be translated into a LINQ to Entities store expression. Consider using the method '{1}' instead.
The method 'First' can only be used as a final query operation. Consider using the method 'FirstOrDefault' in this instance instead.
The methods 'Single' and 'SingleOrDefault' can only be used as a final query operation. Consider using the method 'FirstOrDefault' in this instance instead.
SThe entity or complex type '{0}' cannot be constructed in a LINQ to Entities query.
Unable to create a null constant value of type '{0}'. Only entity types, enumeration types or primitive types are supported in this context.
KThe method '{0}' is not supported when called on an instance of type '{1}'.
AThis method is not supported against a materialized query result.
kCannot compare EntityKeys referring to types '{0}' and '{1}' because they do not share a common super-type.
]Cannot compare '{0}'. Only primitive types, enumeration types and entity types are supported.
member '{0}' of
type '{0}'
rThe method '{0}' is only supported in LINQ to Entities when the argument '{1}' is a non-negative integer constant.
pThe method '{0}' is only supported in LINQ to Entities when there are no trim characters specified as arguments.
UUnable to process the type '{0}', because it has no known mapping to the value layer.
cThe ObjectContext parameter ('{0}') in a compiled query can only be used as the source for queries.
bThe method '{0}' is not supported in LINQ to Entities when the argument '{1}' has the value '{2}'.
]The method '{0}' is only supported in LINQ to Entities when the argument '{1}' is a constant.
eThe connection can not be overridden because this context was created from an existing ObjectContext.
The type of the TypeUsage object specified for the metadata parameter is not compatible with the type to which an EdmMember belongs.
IThe data space of the item does not match the data space of the EdmModel.
FNavigationProperty is not valid. The FromRole and ToRole are the same.
_NavigationProperty is not valid. Role '{0}' or Role '{1}' is not defined in Relationship '{2}'.
PComposable function imports are not supported for version 1.0 or 2.0 EDM Models.
Type '{0}' is derived from type '{1}' that is the type for EntitySet '{2}'. Type '{0}' defines new concurrency requirements that are not allowed for subtypes of base EntitySet types.
4A cycle was detected in the type hierarchy of '{0}'.
'The end name '{0}' is already defined.
cEach member name in an EntityContainer must be unique. A member with name '{0}' is already defined.
sThe key specified in EntityType '{0}' is not valid. Property '{1}' is referenced more than once in the Key element.
TEach Name and PluralName in a relationship must be unique. '{0}' is already defined.
End '{0}' on relationship '{1}' cannot have an operation specified because its multiplicity is '*'. Operations cannot be specified on ends with multiplicity '*'.
|The property '{0}' in EntityType '{1}' is not valid. All properties that are part of the EntityKey must be of PrimitiveType.
@EntitySet '{0}' is based on type '{1}' that has no keys defined.
OProperty '{0}' has a CollectionKind specified but is not a collection property.
jProperty '{0}' has a CollectionKind specified. CollectionKind is only supported in version 1.1 EDM models.
lComplexType '{0}' is marked as abstract. Abstract ComplexTypes are only supported in version 1.1 EDM models.
pComplexType '{0}' has a BaseType specified. ComplexType inheritance is only supported in version 1.1 EDM models.
bThe referenced EntitySet '{0}' for End '{1}' could not be found in the containing EntityContainer.
nKey usage is not valid. The {0} class cannot define keys because one of its base classes ('{1}') defines keys.
VKey part '{0}' for type '{1}' is not valid. All parts of the key must be non-nullable.
aName '{0}' cannot be used in type '{1}'. Member names cannot be the same as their enclosing type.
Multiplicity conflicts with the referential constraint in Role '{0}' in relationship '{1}'. Because at least one of the properties in the Dependent Role is non-nullable, multiplicity of the Principal Role must be '1'.
Multiplicity conflicts with the referential constraint in Role '{0}' in relationship '{1}'. Because all of the properties in the Dependent Role are non-nullable, multiplicity of the Principal Role must be '1'.
Multiplicity is not valid in Role '{0}' in relationship '{1}'. Because all the properties in the Dependent Role are nullable, multiplicity of the Principal Role must be '0..1'.
Multiplicity is not valid in Role '{0}' in relationship '{1}'. Valid values for multiplicity for the Principal Role are '0..1' or '1'.
Multiplicity is not valid in Role '{0}' in relationship '{1}'. Because the Dependent Role properties are not the key properties, the upper bound of the multiplicity of the Dependent Role must be '*'.
Multiplicity is not valid in Role '{0}' in relationship '{1}'. Because the Dependent Role refers to the key properties, the upper bound of the multiplicity of the Dependent Role must be '1'.
?OnDelete can be specified on only one End of an EdmAssociation.
SThere is no property with name '{0}' defined in the type referred to by Role '{1}'.
_A property cannot be of type '{0}'. The property type must be a ComplexType or a PrimitiveType.
rA property cannot be of type '{0}'. The property type must be a ComplexType, a PrimitiveType, or a CollectionType.
jA property cannot be of type {0}. The property type must be a ComplexType, a PrimitiveType or an EnumType.
Properties referred by the Dependent Role '{0}' must be a subset of the key of the EntityType '{1}' referred to by the Dependent Role in the referential constraint for relationship '{2}'.
HEntityType '{0}' has no key defined. Define the key for this EntityType.
mThe number of properties in the Dependent and Principal Roles in a relationship constraint must be identical.
MA nullable ComplexType is not supported. Property '{0}' must not allow nulls.
TEach property name in a type must be unique. Property name '{0}' is already defined.
In relationship '{0}', the Principal and Dependent Role of the referential constraint refer to the same Role in the relationship type.
Role '{0}' in AssociationSets '{1}' and '{2}' refers to the same EntitySet '{3}' in EntityContainer '{4}'. Make sure that if two or more AssociationSets refer to the same AssociationType, the ends do not refer to the same EntitySet.
mThe namespace '{0}' is a system namespace and cannot be used by other schemas. Choose another namespace name.
The types of all properties in the Dependent Role of a referential constraint must be the same as the corresponding property types in the Principal Role. The type of property '{0}' on entity '{1}' does not match the type of property '{2}' on entity '{3}' in the referential constraint '{4}'.
NEach type name in a schema must be unique. Type name '{0}' is already defined.
DependentEnd must not be null.
ToProperties must not be empty.
EntityType must not be null.
ElementType must not be null.
SourceSet must not be null.
TargetSet must not be null.
AssociationEnd must not be null.
ElementType must not be null.
)The specified name is not allowed: '{0}'.
AThe specified name must not be longer than 480 characters: '{0}'.
Association must not be null.
ResultEnd must not be null.
)The type is not a valid EdmTypeReference.
!The name is missing or not valid.
lA property cannot be of type '{0}'. The property type must be a ComplexType, a PrimitiveType or an EnumType.
yThe EDMVersion of the item collection {0} is not an EDMVersion that the runtime supports. The supported versions are {1}.
Creating a DbModelBuilder or writing the EDMX from a DbContext created using Database First or Model First is not supported. EDMX can only be obtained from a Code First DbContext created without using an existing DbCompiledModel.
Creating a DbModelBuilder or writing the EDMX from a DbContext created using an existing ObjectContext is not supported. EDMX can only be obtained from a Code First DbContext created without using an existing DbCompiledModel.
Writing the EDMX file or using Migrations from a DbContext created using a DbCompiledModel that is not in the DbModelStore cache is not supported. Ensure that the DbCompiledModel is stored in the DbModelStore cache.
iThe ELEMENT operator is not supported in this version of Entity Framework. It is reserved for future use.
\Values of enumerated types decorated with the FlagsAttribute can not be converted to string.
4Values of type '{0}' can not be converted to string.
RThe CommandText element is empty. Add the command text to the CommandText element.
TThe DefiningQuery element is empty. Add the query text to the DefiningQuery element.
c{0} does not contain a schema definition, or the XmlReader provided started at the end of the file.
{0} is not valid.
\The source XmlReader does not contain a schema definition or started at the end of the file.
Sequence contains no elements
KTo enable migrations for '{0}', use Enable-Migrations -ContextTypeName {0}.
;More than one context type was found in the assembly '{0}'.
rMore than one context type '{0}' was found in the assembly '{1}'. Specify the fully qualified name of the context.
0No context type was found in the assembly '{0}'.
;The context type '{0}' was not found in the assembly '{1}'.
UEach Name and PluralName in a relationship must be unique. '{0}' was already defined.
End '{0}' on relationship '{1}' cannot have operation specified since its multiplicity is '*'. Operations cannot be specified on ends with multiplicity '*'.
:End '{0}' on relationship '{1}' must specify multiplicity.
cThis store command cannot be cloned because the underlying store provider does not support cloning.
sThe correct DbType cannot be inferred based on the value that has been set for the EntityParameter.DbType property.
\CommandText property value cannot be retrieved because the CommandTree property is not null.
\CommandTree property value cannot be retrieved because the CommandText property is not null.
oThe connection could not be opened because it is broken. The connection must be closed before it can be opened.
This EntityCommand is based on a prepared command definition and cannot be re-prepared. To create an equivalent command with different parameters, create a new command definition and call its CreateCommand method.
WCannot set the CommandText property value because the CommandTree property is not null.
WCannot set the CommandTree property value because the CommandText property is not null.
QCannot perform the update operation because the adapter's connection is not open.
^An error occurred while executing the command definition. See the inner exception for details.
^An error occurred while preparing the command definition. See the inner exception for details.
SAn error occurred while executing the command. See the inner exception for details.
mThe command could not be executed, because the connection metadata is incompatible with the command metadata.
The connection is not open.
broken
closed
fSome required information is missing from the connection string. The '{0}' keyword is always required.
TA connection string must be set on the connection before you attempt this operation.
The command is still associated with an open data reader. Changes cannot be made on this command and this command cannot be executed until the data reader is closed.
=The DbConnection parameter '{0}' contains no ProviderFactory.
WParameters must have a unique ParameterName. A second instance of '{0}' was discovered.
One of the parameters in the EntityParameterCollection is null or empty. A name must begin with a letter and contain only letters, numbers, and underscores.
'The EdmType '{0}' is not a scalar type.
QThe EdmType '{0}' is not consistent with the DbType provided for parameter '{1}'.
oAn error occurred while starting a transaction on the provider connection. See the inner exception for details.
]An error occurred while closing the provider connection. See the inner exception for details.
jExecution of the command requires an open and available connection. The connection's current state is {0}.
DOther keywords are not allowed when the 'Name' keyword is specified.
nThe store data provider failed to return information for the {0} request. See the inner exception for details.
REntityCommand.CommandText was not specified for the StoredProcedure EntityCommand.
sThe function import '{0}' is composable. Only non-composable function imports can be executed as stored procedures.
pThe declared type of navigation property {0}.{1} is not compatible with the result of the specified navigation.
The specified named connection is either not found in the configuration, not intended to be used with the EntityClient provider, or not valid.
The parameter '{0}' is not an input-only parameter. The EntityClient provider only allows input-only parameters when the CommandType property is set to CommandText.
The parameter name '{0}' is not valid. A valid parameter name must begin with a letter and contain only letters, numbers, and underscores.
The ADO.NET provider with invariant name '{0}' is either not registered in the machine or application config file, or could not be loaded. See the inner exception for details.
The value of EntityCommand.CommandText is not valid for a StoredProcedure command. The EntityCommand.CommandText value must be of the form 'ContainerName.FunctionImportName'.
[The transaction is either not associated with the current connection or has been completed.
/MetadataWorkspace must have {0} pre-registered.
#The '{0}' keyword is not supported.
iThe connection string of the named connection '{0}' cannot contain a 'Name' keyword in the configuration.
@The EntityCommand.CommandText property has not been initialized.
LCannot perform the operation because the adapter does not have a connection.
LCannot perform the operation because the command does not have a connection.
{The update operation cannot be performed, because the adapter's connection is not associated with a valid store connection.
The underlying provider failed.
&The underlying provider failed on {0}.
UEntityClient cannot be used to create a command definition from a store command tree.
A null was returned after calling the '{0}' method on a store provider instance of type '{1}'. The store provider might not be functioning correctly.
No modifications to connection are permitted after the metadata has been registered either by opening a connection or constructing the connection with a MetadataWorkspace.
kAn error occurred while reading from the store provider's data reader. See the inner exception for details.
iThe data reader returned by the store data provider does not have enough columns for the query requested.
The connection is already in a transaction and cannot participate in another transaction. EntityClient does not support parallel transactions.
CThe FunctionImport '{1}' could not be found in the container '{0}'.
aThe container '{0}' specified for the FunctionImport could not be found in the current workspace.
The EntityParameter '{0}' must have a value from which the DbType can be inferred, or a supported DbType must be set as the value of the EntityParameter.DbType property.
ZThe function import '{0}' cannot be executed because it is not mapped to a store function.
nThe only EntityCommand.CommandType values supported by the EntityClient provider are Text and StoredProcedure.
ZThe DbType '{0}' is not valid for the EntityParameter.DbType property on the '{1}' object.
$The specified value is not a string.
0The metadata locations in the connection string.
-The connection name in the connection string.
@The underlying provider invariant name in the connection string.
5The inner connection string in the connection string.
cThe EntityContainer name must be unique. An EntityContainer with the name '{0}' is already defined.
TEntityContainer '{0}' cannot extend itself. Specify some other EntityContainer name.
Context
Named ConnectionString
Source
The property '{0}' in EntityType '{1}' is not valid. All properties that are part of the EntityKey must be of enumeration or primitive type.
}The property '{0}' in EntityType '{1}' is not valid. EntityKey properties that are of type '{2}' are currently not supported.
The property '{0}' in EntityType '{1}' is not valid. Type '{2}' of the property maps to '{3}' and EntityKey properties that are of type '{4}' are currently not supported.
5EntityKey values cannot be changed once they are set.
The requested operation could not be completed, because a mismatched EntityKey was returned from the EntityKey property on an object of type '{0}'.
7An EntityKey must have at least one key name and value.
wThe EntitySet '{0}' obtained from the metadata workspace is incompatible with the EntitySet required by this EntityKey.
The provided list of key-value pairs contains an incorrect number of entries. There are {1} key fields defined on type '{0}', but {2} were provided.
jThe type of the key field '{0}' is expected to be '{1}', but the value provided is actually of type '{2}'.
6The name '{0}' contains characters that are not valid.
yThe EntitySet name cannot be null or empty, and must be qualified with an EntityContainer name that is not null or empty.
6The EntityKey does not contain a valid EntitySet name.
}The required entry '{0}' was not found in the provided input. This entry is required by the key fields defined on type '{1}'.
mNo corresponding object layer type found for the key field '{0}' whose type in the conceptual layer is '{1}'.
EThe key-value pairs that define an EntityKey cannot be null or empty.
wThe key field '{0}' cannot have a value of null. A non-null value is required for the key fields defined on type '{1}'.
sThe requested operation could not be completed, because a null EntityKey property value was returned by the object.
The property '{1}' on type '{0}' cannot be mapped because it has been explicitly excluded from the model or it is of a type not supported by the DbModelBuilderVersion being used.
Properties for type '{0}' can only be mapped once. Ensure the MapInheritedProperties method is only used during one call to the Map method.
Properties for type '{0}' can only be mapped once. Ensure the Properties method is used and that repeated calls specify each non-key property only once.
Properties for type '{0}' can only be mapped once. The non-key property '{1}' is mapped more than once. Ensure the Properties method specifies each non-key property only once.
The entity types '{0}' and '{1}' cannot share table '{2}' because they are not in the same type hierarchy or do not have a valid one to one foreign key relationship with matching primary keys between them.
The association '{0}' between entity types '{1}' and '{2}' is invalid. In a TPC hierarchy independent associations are only allowed on the most derived types.
GInvalid index {0} for this EntityParameterCollection with {1} elements.
_An EntityParameter with ParameterName '{0}' is not contained by this EntityParameterCollection.
_Attempted to remove an EntityParameter that is not contained by this EntityParameterCollection.
NThe EntityParameter is already contained by another EntityParameterCollection.
lThe property '{0}' on type '{1}' cannot be set because the collection is already set to an EntityCollection.
There is already a generated proxy type for the object layer type '{0}'. This occurs when the same object layer type is mapped by two or more different models in an AppDomain.
IThe entity wrapper stored in the proxy does not reference the same proxy.
There is no metadata information available for the proxy type for '{0}'. This exception can be caused when a proxy type for an entity is detached from an ObjectContext. See InnerException for details.
fMultiplicity constraint violated. The role '{0}' of the relationship '{1}' has multiplicity 1 or 0..1.
A referential integrity constraint violation occurred: A primary key property that is a part of referential integrity constraint cannot be changed when the dependent object is Unchanged unless it is being set to the association's principal object. The principal object must be tracked and not marked for deletion.
^The EntityKey property cannot be set to EntityNotValidKey, NoEntitySetKey, or a temporary key.
The object could not be added or attached because its EntityReference has an EntityKey property value that does not match the EntityKey for this object.
An EntityReference of type '{0}' could not be returned for role name '{1}' in relationship '{2}'. Make sure that the EdmRelationshipAttribute that defines this relationship has the correct RelationshipMultiplicity for this role name. For more information, see the Entity Framework documentation.
A relationship multiplicity constraint violation occurred: An EntityReference expected at least one related object, but the query returned no related objects from the data store.
A relationship multiplicity constraint violation occurred: An EntityReference can have no more than one related object, but the query returned more than one related object. This is a non-recoverable error.
TThe EntitySet already has an EntityContainer, it cannot be added to this collection.
OThe EntitySet '{0}' that was passed in does not belong to the conceptual model.
@The EntitySet {0} is based on type {1} that has no keys defined.
jThe type '{0}' has already been configured as a complex type. It cannot be reconfigured as an entity type.
dThe EntityType specified for the metadata parameter is not compatible with the specified EntitySet.
TAn entity object cannot be referenced by multiple instances of IEntityChangeTracker.
WThe value '{0}' of the enumeration type member '{1}' cannot be converted to '{2}' type.
An error occurred while attempting to generate the body SQL of the stored procedure '{0}' for entity type '{1}'. This can happen if the entity type has both a self-referencing association and a store-generated key. See the inner exception for details.
The configured execution strategy '{0}' does not support user initiated transactions. See http://go.microsoft.com/fwlink/?LinkId=309381 for additional information.
TThe minimum delay of '{0}' must be less than or equal to the maximum delay of '{1}'.
HThe delay '{0}' is invalid. Delay must be greater than or equal to zero.
Maximum number of retries ({0}) exceeded while executing database operations with '{1}'. See inner exception for the most recent failure.
Streaming queries are not supported by the configured execution strategy '{0}'. See http://go.microsoft.com/fwlink/?LinkId=309381 for additional information.
Expansion of |DataDirectory| failed while processing the connection string. Ensure that |DataDirectory| is set to a valid fully-qualified path.
BThe expression in the CREATEREF operator is not a valid EntitySet.
(The specified expression cannot be NULL.
3The specified expression must be of CollectionType.
1The specified expression must be of numeric type.
1The specified expression must be of Boolean type.
>{0} must refer to an EntityType. The passed type is {1} '{2}'.
7The specified expression type must be equal-comparable.
?{0} must refer to a nominal type. The passed type is {1} '{2}'.
5The specified expression cannot be of CollectionType.
HThe following information may be useful in resolving the previous error:
6Facet declaration requires type attribute declaration.
3{0} facet isn't allowed for properties of type {1}.
5Facets cannot be specified for non-scalar type '{0}'.
3Could not find the conceptual model type for '{0}'.
&Could not find the CLR type for '{0}'.
&Could not find the CLR type for '{0}'.
An error occurred accessing the database. This usually means that the connection to the database failed. Check that the connection string is correct and that the appropriate DbContext constructor is being used to specify it or find it in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=386386 for information on DbContext and connections. See the inner exception for details of the failure.
?Could not resolve the aggregate function '{0}' in this context.
)Could not retrieve the provider manifest.
]The ForeignKeyAttribute on property '{0}' on type '{1}' is not valid. Name must not be empty.
The ForeignKeyAttribute on property '{0}' on type '{1}' is not valid. The foreign key name '{2}' was not found on the dependent type '{3}'. The Name value should be a comma separated list of foreign key property names.
The ForeignKeyAttribute on property '{0}' on type '{1}' is not valid. The navigation property '{2}' was not found on the dependent type '{1}'. The Name value should be a valid navigation property name.
Unable to determine a composite foreign key ordering for foreign key on type {0}. When using the ForeignKey data annotation on composite foreign key properties ensure order is specified by using the Column data annotation or the fluent API.
The foreign key component '{0}' is not a declared property on type '{1}'. Verify that it has not been explicitly excluded from the model and that it is a valid primitive property.
The function import '{0}' has a parameter of a collection or reference type. Parameters of a collection or reference type are not allowed in function imports.
The function import '{0}' is declared as composable and side-effecting. A function import can be either composable or side-effecting, but not both.
The function import '{0}' specifies an entity set and an entity set path. A function import may only specify one of these values but not both.
kThe function import '{0}' returns entities of type '{1}' that cannot exist in the declared EntitySet '{2}'.
qThe function import '{0}' has a non-nullable parameter. Only nullable parameters are allowed in function imports.
HFunctionImport '{0}' returns entities but does not specify an EntitySet.
OThe function import '{0}' specifies an entity set but does not return entities.
`EntitySet '{0}' is not valid in FunctionImport '{1}'. Unable to find an EntitySet with the name.
Return type is not valid in FunctionImport '{0}'. The FunctionImport must return a collection of scalar values or a collection of entities.
pReturn type is not valid in FunctionImport '{0}'. The FunctionImport must return Scalar, Entity, or ComplexType.
Return type is not valid in FunctionImport '{0}'. The FunctionImport can have no return type or return a collection of scalar values, a collection of complex types or a collection of entities.
Type '{0}' is not valid in function '{1}'. The function must have return type and parameters expressed in conceptual side primitive types.
zType '{0}' is not valid in function '{1}'. The function must have return type and parameters expressed in primitive types.
OA '{0}' exception occurred while processing the query. See the inner exception.
General query error
|The type that contains generated views '{0}' must derive from the System.Data.Entity.Infrastructure.DbMappingViewCache type.
^The EntitySet '{0}' for which the view has been specified could not be found in the workspace.
unknown
warning
The query syntax is not valid.
]EdmComplexTypeAttribute and EdmEntityTypeAttribute can not be used on the generic type '{0}'.
QThe GROUPPARTITION operator is allowed only in the context of a query expression.
QINTERNAL ERROR: The group variable must be present in one of the existing scopes.
AThe GROUP BY clause key expression type must be equal-comparable.
Unable to calculate model hash because no mapping was found between conceptual model container '{0}' and store model container '{1}'. Ensure that the names match those defined in the EDMX or Code First model.
Unable to calculate model hash because the model contained more than one container. Choose the conceptual and store model containers to use by passing their names to the appropriate overload of the ComputeMappingHashValue method.
8The HAVING clause must be preceded by a GROUP BY clause.
The source IQueryable doesn't implement IDbAsyncEnumerable{0}. Only sources that implement IDbAsyncEnumerable can be used for Entity Framework asynchronous operations. For more details see http://go.microsoft.com/fwlink/?LinkId=287068.
The provider for the source IQueryable doesn't implement IDbAsyncQueryProvider. Only providers that implement IDbAsyncQueryProvider can be used for Entity Framework asynchronous operations. For more details see http://go.microsoft.com/fwlink/?LinkId=287068.
TThe CREATEREF key expression type is not compatible with the EntityKey element type.
LThe CREATEREF key expression is not compatible with the EntityKey structure.
in the current FROM clause
in GROUP BY clause
#as a column name in ROW constructor
in the SELECT projection list
YObjects of type '{0}' are not compatible with objects of type '{1}' and cannot be merged.
The specified association foreign key columns '{0}' are invalid. The number of columns specified must match the number of primary key columns.
#The Provider Manifest is incorrect.
The index component '{0}' is not a declared property on type '{1}'. Verify that it has not been explicitly excluded from the model and that it is a valid primitive property.
In EntityContainer '{4}', the Role for the End with the EntitySet '{0}' in the AssociationSet '{1}' was not supplied, and there is more than one End in the Relationship '{2}' that could match the type '{3}'. Provide the Role attribute to disambiguate the End.
In EntityContainer '{4}', the Role for the End with the EntitySet '{0}', in the AssociationSet '{1}' was not supplied, and there were no Ends in the Relationship '{2}' that matched the type '{3}'.
The Role for the End with the EntitySet {0} in the AssociationSet {1} was not supplied and the End found matches one that is already defined. Change the EntitySet to one which has a type of a different End of the Relationship.
InitialCreate
4The INNER JOIN expression must have an ON predicate.
The type '{0}' registered in the application config file as an IDbInterceptor not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application.
The type '{0}' registered in the application config file as an IDbInterceptor does not implement the IDbInterceptor interface. Interceptors must implement this interface.
OThe Action {0} on {1} is not recognized. Valid actions are 'None' or 'Cascade'.
Q'{0}' is a reserved keyword and cannot be used as an alias, unless it is escaped.
JINTERNAL ERROR: The argument type for the aggregate function is not valid.
8The type '{0}' is not supported in the UNION expression.
MBaseType ({0}) is not valid. The BaseType for {1} must be another EntityType.
NBaseType ({0}) is not valid. The BaseType for {1} must be another ComplexType.
LBaseType ({0}) is not valid. The BaseType for {1} must be a structured type.
2The THEN/ELSE expression types are not compatible.
[The CASE/WHEN/THEN expression is not valid, because all resulting expressions are un-typed.
]The CAST expression is not valid. There is no valid conversion from type '{0}' to type '{1}'.
6The CAST argument expression must be of a scalar type.
0The CAST type argument must be of a scalar type.
The derived type '{0}' has already been mapped using the chaining syntax. A derived type can only be mapped once using the chaining syntax.
aItemCollection is not valid. For '{0}' space, the CollectionType should be MappingItemCollection.
^Argument '{0}' is not valid. The specified mapping already exists or property paths are empty.
The properties expression '{0}' is not valid. The expression should represent a property: C#: 't => t.MyProperty' VB.Net: 'Function(t) t.MyProperty'. When specifying multiple properties use an anonymous type: C#: 't => new {{ t.MyProperty1, t.MyProperty2 }}' VB.Net: 'Function(t) New With {{ t.MyProperty1, t.MyProperty2 }}'.
The expression '{0}' is not a valid property expression. The expression should represent a property: C#: 't => t.MyProperty' VB.Net: 'Function(t) t.MyProperty'. Use dotted paths for nested properties: C#: 't => t.MyProperty.MyProperty' VB.Net: 'Function(t) t.MyProperty.MyProperty'.
The complex member '{0}' in type '{1}' and the complex member '{2}' in type '{3}' are incompatible because they have a different number of members.
1The CREATEREF key expression must be of row type.
WThe argument type '{0}' is not compatible with the property '{1}' of formal type '{2}'.
It is not valid to use the type constructor on type '{0}'. This type must have one of the following constructors: Entity, ComplexType, or RelationType.
eThe database name '{0}' is invalid. Database names must be of the form [<schema_name>.]<object_name>.
LThe DateTimeOffset literal '{0}' exceeds the range of DateTimeOffset values.
5The day '{0}' is not valid in DateTime literal '{1}'.
IThe day '{0}' is not valid for the month '{1}' in DateTime literal '{2}'.
k'{0}' is not a member of type '{1}'. Type '{1}' is the result of dereferencing an expression of type '{2}'.
Default value ({0}) is not valid for Binary. Value must be of form 0x123 where 123 stands for a non-empty sequence of hex digits.
NDefault value ({0}) is not valid for Boolean. The value must be true or false.
SDefault value ({0}) is not valid for DateTime. The value must be in the form '{1}'.
YDefault value ({0}) is not valid for DateTimeOffset. The value must be in the form '{1}'.
Default value ({0}) is not compatible with the facets specified for Decimal. The value must be a decimal number with scale less than or equal to {1} and precision less than or equal to {2}.
`Default value ({0}) is not valid. The value must be a floating point number between {1} and {2}.
Default value ({0}) is not valid for GUID. The value must be enclosed in single quotes in the form 'dddddddd-dddd-dddd-dddd-dddddddddddd'.
JDefault value ({0}) is not valid. Expected an integer between {1} and {2}.
ODefault value ({0}) is not valid for Time. The value must be in the form '{1}'.
Values of type '{0}' cannot be used as type discriminator values. Supported types include byte, signed byte, bool, int16, int32, int64, and string.
<The DISTINCT/ALL argument is not valid in type constructors.
FThe DISTINCT/ALL argument is only valid for group aggregate functions.
tDocumentation content is not valid. The Documentation element can only contain Summary and LongDescription elements.
4The EDM version {0} is not supported by the runtime.
@All 'EdmMember' instances must be a valid member of the EdmType.
$Escaped identifiers cannot be empty.
<The query text consists only of comments and/or white space.
AThe End {0} has a different Type than the EntitySet it refers to.
TThere is no Role with name '{0}' defined in relationship '{1}'. Check and try again.
)No EntityContainer found with name '{0}'.
4The End {0} does not match any Ends on the {1} type.
jThe EntityParameterCollection only accepts non-null EntityParameter type objects, not objects of type {0}.
fThe EntityType objects '{0}' and '{1}' are incompatible because they do not share a common super-type.
RThe EntitySet with the specified name '{0}' does not exist in the EntityContainer.
^The referenced EntitySet {0} for End {1} could not be found in the containing EntityContainer.
iAn EntitySet cannot be of type {0}. The property type must be an EntityType, or an AssociationEntityType.
{Not all properties for type '{0}' have been mapped. Either map those properties or explicitly excluded them from the model.
The type '{0}' was not mapped. Check that the type has not been explicitly excluded by using the Ignore method or NotMappedAttribute data annotation. Verify that the type was defined as a class, is not primitive or generic, and does not inherit from EntityObject.
The entity '{0}' in type '{1}' and the entity '{2}' in type '{3}' are incompatible because they do not share a common super-type.
PThe specified type cannot be used as the underlying type of an enumeration type.
*The escaped identifier '{0}' is not valid.
ZThe escaped identifier '{0}' has a mismatch of opening ('[') and closing (']') delimiters.
@The expression has been classified as a {0}; a {1} was expected.
WSpecified file '{0}' has extension '{1}' that is not valid. The valid extension is {2}.
9The FLATTEN argument must be a collection of collections.
Properties referred by the Principal Role {0} must be exactly identical to the key of the EntityType {1} referred to by the Principal Role in the relationship constraint for Relationship {2}. Make sure all the key properties are specified in the Principal Role.
xThe identifier '{0}' is not valid because it is not contained either in an aggregate function or in the GROUP BY clause.
2Hour '{0}' is not valid in DateTime literal '{1}'.
?The 'from' end could not be inferred in the relationship '{0}'.
=The 'to' end could not be inferred in the relationship '{0}'.
The element type '{0}' and the CollectionType '{1}' are not compatible. The IN expression only supports entity, scalar and reference types.
3Left correlation is not allowed in the JOIN clause.
PThe KEY argument expression must be of reference type. The passed type is '{0}'.
bKey usage is not valid. {0} cannot define keys because one of its base classes ({1}) defines keys.
HThe specified key Member '{0}' does not exist in the Members collection.
8Key: {0} is not valid. {1} is not a valid property name.
UKey Part: '{0}' for type {1} is not valid. All parts of the key must be non nullable.
QCOLLATE can only be used with sort keys of string type. The passed type is '{0}'.
)The {0} literal value '{1}' is not valid.
$MaxLength must be greater than zero.
]Name {0} cannot be used in type {1}. Member names cannot be the same as their enclosing type.
5'{0}' has been resolved as a {1}; a {2} was expected.
cA namespace, type, or function name must be a single name or any number of names separated by dots.
The specified metadata path is not valid. A valid path must be either an existing directory, an existing file with extension '.csdl', '.ssdl', or '.msl', or a URI that identifies an embedded resource.
4Minute '{0}' is not valid in DateTime literal '{1}'.
TThe WITH RELATIONSHIP clause is only supported when defining read-only view queries.
3Month '{0}' is not valid in DateTime literal '{1}'.
Multiplicity conflicts with the referential constraint in Role '{0}' in relationship '{1}'. Because one/all of the properties in the Dependent Role is non-nullable, multiplicity of the Principal Role must be '1'.
Multiplicity conflicts with the referential constraint in Role '{0}' in relationship '{1}'. Because all of the properties in the Dependent Role are non-nullable, multiplicity of the Principal Role must be '1'.
Multiplicity is not valid in Role '{0}' in relationship '{1}'. Because all the properties in the Dependent Role are nullable, multiplicity of the Principal Role must be '0..1'.
Multiplicity is not valid in role '{0}' in relationship '{1}'. Valid values for multiplicity for Principal Role are '0..1' or '1'.
mMultiplicity is not valid in Role '{0}' in relationship '{1}'. The Lower Bound of the multiplicity must be 0.
Multiplicity is not valid in Role '{0}' in relationship '{1}'. Because the Dependent Role properties are not the key properties, the upper bound of the multiplicity of the Dependent Role must be *.
Multiplicity is not valid in Role '{0}' in relationship '{1}'. Because the Dependent Role refers to the key properties, the upper bound of the multiplicity of the Dependent Role must be 1.
{1} ({0}) is not valid.
!The namespace alias is not valid.
No schema encountered with '{0}' namespace. Make sure the namespace is correct or the schema defining the namespace is specified.
u'{0}' is not a valid namespace or alias name. You must use the current schema namespace or alias to qualify the type.
The property '{0}' on type '{1}' cannot be configured as a navigation property because type '{2}' was configured as a complex type.
An "is not null" condition cannot be specified on property '{0}' on type '{1}' because this property is not included in the model. Check that the property has not been explicitly excluded from the model by using the Ignore method or NotMappedAttribute data annotation.
@Un-typed NULL arguments are not valid in arithmetic expressions.
@Un-typed NULL arguments are not valid in comparison expressions.
TThe non-nullable member '{0}' of type '{1}' cannot be initialized with a NULL value.
VError in Function '{0}'. Aggregate Functions should take at least one input parameter.
]OnDelete, OnLock, and other such elements can be specified on only one End of an Association.
!The operator symbol is not valid.
1The command parameter syntax '@{0}' is not valid.
xType of parameter '{0}' in function '{1}' is not valid. The aggregate function parameter type must be of CollectionType.
^{0} member '{1}' and {2} member '{3}' are incompatible because they do not have a common type.
z{0} member '{1}' in type '{2}' and {3} member '{4}' in type '{5}' are incompatible because they do not have a common type.
9The ON predicate is not allowed in the CROSS JOIN clause.
1The value '{0}' is not a valid PrimitiveTypeKind.
The properties expression '{0}' is not valid. The expression should represent a property: C#: 't => t.MyProperty' VB.Net: 'Function(t) t.MyProperty'. When specifying multiple properties use an anonymous type: C#: 't => new {{ t.MyProperty1, t.MyProperty2 }}' VB.Net: 'Function(t) New With {{ t.MyProperty1, t.MyProperty2 }}'.
The expression '{0}' is not a valid property expression. The expression should represent a property: C#: 't => t.MyProperty' VB.Net: 'Function(t) t.MyProperty'.
LThere is no property with name '{0}' defined in type referred by Role '{1}'.
rA property cannot be of type {0}. The property type must be an inline type, a scalar type, or an enumeration type.
$The punctuation symbol is not valid.
aThe query is not valid because it contains the association type '{0}', which cannot be projected.
jRelationship {0} is not valid. Multiplicity ({1}) is not valid. Multiplicity must be: '*', '0..1', or '1'.
_Relationship {0} is not valid. End type ({1}) is not valid. The End type must be an EntityType.
7'{0}' is not a valid member of the '{1}' relationship.
XThe RelationshipSet with the specified name '{0}' does not exist in the EntityContainer.
RA RelationshipSet cannot be of type {0}. The property type must be a Relationship.
#'{0}' is not a valid resource name.
,Invalid return type for composable function.
iComplex type '{0}' and complex type '{1}' are incompatible because they have different number of members.
cRow type '{0}' and row type '{1}' are incompatible because they have a different number of columns.
Row member '{0}' in type '{1}' and row member '{2}' in type '{3}' are incompatible because they have a different number of columns.
,INTERNAL ERROR: The save point is not valid.
*Schema specified is not valid. Errors: {0}
-INTERNAL ERROR: The scope index is not valid.
4Second '{0}' is not valid in DateTime literal '{1}'.
The SELECT VALUE expression cannot be aliased in this context. SELECT VALUE expression can be aliased only when ORDER BY is specified.
ASELECT VALUE can have only one expression in the projection list.
)The simple identifier '{0}' is not valid.
{The simple identifier '{0}' must contain basic Latin characters only. To use UNICODE characters, use an escaped identifier.
TMaxLength '{0}' is not valid. Length must be between '{1}' and '{2}' for '{3}' type.
RSRID '{0}' is not valid. Its value must be between '{1}' and '{2}' for '{3}' type.
sThe type '{0}' has already been mapped to table '{1}'. Specify all mapping aspects of a table in a single Map call.
pMap was called more than once for type '{0}' and at least one of the calls didn't specify the target table name.
Properties referred by the Dependent Role {0} must be a subset of the key of the EntityType {1} referred to by the Dependent Role in the referential constraint for Relationship {2}.
LThe WITH RELATIONSHIP clause is only supported for entity type constructors.
-The '{0}' argument must be of CollectionType.
<The unsigned type '{0}' cannot be promoted to a signed type.
G'{0}' is only valid in metadata file paths when running inside ASP.NET.
The value {0} is not valid for ParameterTypeSemantics attribute. Valid values are 'ExactMatchOnly', 'AllowImplicitPromotion' or 'AllowImplicitConversion'.
CThe multiplicity '{1}' is not valid for the relationship end '{0}'.
2Year '{0}' is not valid in DateTime literal '{1}'.
The InversePropertyAttribute on property '{2}' on type '{3}' is not valid. The property '{0}' is not a valid navigation property on the related type '{1}'. Ensure that the property exists and is a valid reference or collection navigation property.
A relationship cannot be established from property '{0}' on type '{1}' to property '{0}' on type '{1}'. Check the values in the InversePropertyAttribute to ensure relationship definitions are unique and reference from one navigation property to its corresponding inverse navigation property.
2AggregateOp encountered outside of GroupBy method.
Unexpected VarDefOp
Unexpected VarDefListOp
/The specified Op is of an unsupported type: {0}
YThe IS [NOT] NULL expression must be of entity, reference, enumeration or primitive type.
GThe item with identity '{0}' already exists in the metadata collection.
IThe member with identity '{0}' does not exist in the metadata collection.
HEntityType '{0}' has no key defined. Define the key for this EntityType.
WThe key expression '{0}' must have at least one reference to the immediate input scope.
The key component '{0}' is not a declared property on type '{1}'. Verify that it has not been explicitly excluded from the model and that it is a valid primitive property.
dA key is registered for the derived type '{0}'. Keys can only be registered for the root type '{1}'.
Can not override the connection for this context with an EntityConnection because the original connection was a standard DbConnection.
Can not override the connection for this context with a standard DbConnection because the original connection was an EntityConnection.
BThe left argument of the set expression must be of CollectionType.
Calling '{0}' is not valid for type '{1}' because it is configured as a complex type. '{0}' is only allowed when configuring entity types.
VCalling '{0}' is not valid for type '{1}' because it has been excluded from the model.
The entity type '{0}' on which the navigation property '{1}' is declared is not a base type for the type '{2}' referred to by the inverse navigation property '{3}'.
The property '{0}' cannot be configured as a navigation property. The property must be a valid entity type and the property should have a non-abstract getter and setter. For collection properties the type must implement ICollection<T> where T is a valid entity type.
The entity type '{0}' to which the navigation property '{1}' refers does not derive from the type '{2}' on which the inverse navigation property '{3}' is declared.
lThe property '{0}' cannot be configured. Only scalar properties can be configured using the Property method.
KMultiplicity '{0}' is not compatible with the property '{1}' of type '{2}'.
KMultiplicity '{0}' is not valid. Multiplicity must be: '*', '0..1', or '1'.
uScale cannot be configured for the DateTime property '{0}', only precision can be configured for DateTime properties.
}Only precision was configured for Decimal property '{0}'. Both precision and scale must be configured for Decimal properties.
Precision without scale has been configured for property '{0}'. Precision without scale can only be configured for DateTime properties.
Precision and scale have been configured for property '{0}'. Precision and scale can only be configured for Decimal properties.
fThe property '{0}' is not a Byte array. IsRowVersion can only be configured for Byte array properties.
ZThe property '{0}' is not a String. IsUnicode can only be configured on String properties.
uThe property '{0}' is not a String or Byte array. Length can only be configured for String and Byte array properties.
iThe property '{0}' of type '{1}' cannot be marked as optional because it cannot be assigned a null value.
&LIKE arguments must be of string type.
@There is no EDM type that corresponds to the literal type '{0}'.
8INTERNAL ERROR: The literal type '{0}' is not supported.
collection
column
complex
entity
entity container
enum member
function
query inline function
keyword
namespace, type or function
namespace
primitive
reference
value expression
*Target database is already at version {0}.
!Applying explicit migration: {0}.
"Applying automatic migration: {0}.
Explicit
No pending explicit migrations.
$Applying explicit migrations: [{1}].
Reverting migrations: [{1}].
#Reverting automatic migration: {0}.
"Reverting explicit migration: {0}.
Running Seed method.
Target database is: {0}.
3'{1}' (DataSource: {0}, Provider: {2}, Origin: {3})
;The specified literal has a malformed single quote payload.
=The specified literal has a malformed string literal payload.
@Malformed XML. Element starting at ({0},{1}) has no closing tag.
>MappingViewCacheFactory is already set and cannot be modified.
Type '{0}' in conceptual side cannot be mapped to type '{1}' on the object side. Both the types must be abstract or both must be concrete types.
The EntitySetMapping in EntityContainerMapping for EntityContainer '{0}' must contain only mapping fragments and no query view. The EntitySetMapping contains only query views and the view for this EntityContainerMapping will not be generated.
HThe EntityContainer '{0}' for the storage model has already been mapped.
fAn EdmType cannot be mapped to CLR classes multiple times. The EdmType '{0}' is mapped more than once.
TThe value specified for the condition is not compatible with the type of the member.
YThe Member '{0}' in the conceptual model type '{1}' is not present in the CLR type '{2}'.
YThe Member '{0}' in the CLR type '{1}' is not present in the conceptual model type '{2}'.
The type '{0}' of the member '{1}' in the conceptual side type '{2}' does not match with the type '{3}' of the member '{4}' on the object side type '{5}'.
The '{0}' property on the conceptual model type '{1}' is of type '{2}'. The property '{3}' on the CLR type '{4}' is of type '{5}'. The property types must match.
The number of members in the conceptual type '{0}' does not match with the number of members on the object side type '{1}'. Make sure the number of members are the same.
The type '{0}'('{1}') of the member '{2}' in the conceptual type '{3}' doesn't match with the type '{4}'('{5}') of the member '{6}' on the object side type '{7}'.
The multiplicity '{0}' on End '{1}' in the conceptual side Association '{2}' doesn't match with multiplicity '{3}' on end '{4}' on the object side Association '{5}'.
OThe version of EdmItemCollection must match the version of StoreItemCollection.
|The version of the loaded mapping files must be the same as the version of loaded EdmItemCollection and StoreItemCollection.
MakeColumnsDistinct flag can only be placed within a container that does not generate update views. Mark GenerateUpdateViews attribute to 'false' within EntityContainerMapping.
DThe conceptual AssociationSet '{0}' cannot be mapped multiple times.
WMore than one property map found for property '{0}' when using case-insensitive search.
.The type '{0}' has been mapped more than once.
6The query view specified for EntitySet '{0}' is empty.
DThe IsTypeOf({0}) query view specified for EntitySet '{1}' is empty.
KThe query view specified for EntitySet '{0}' for EntityType '{1}' is empty.
The EntitySet '{0}' used for creating the Ref expression does not match the EntitySet '{1}' declared on the AssociationSetEnd '{2}' of the AssociationSet '{3}'.
Type '{0}' defined in the conceptual model cannot be mapped to type '{1}' from the object layer. An enumeration type cannot be mapped to a non-enumeration type.
ZNon-empty enumeration value must be specified for condition mapping for enumeration '{0}'.
DEnumeration value '{0}' specified in condition mapping is not valid.
The enumeration type '{0}' defined in the object layer does not have a member that corresponds to the member '{1}' whose value is '{2}' of the enumeration type '{3}' defined in the conceptual model.
The underlying type '{0}' of the enumeration type '{1}' defined in the conceptual model does not match the underlying type '{2}' of the enumeration type '{3}' defined in the object layer.
The key properties of all entity types returned by the function import '{0}' must be mapped to the same non-nullable columns returned by the storage function.
The condition value specified for {0} is not compatible with the type returned by the storage provider. Column name: '{1}', ResultType: '{2}'.
An {0} element can only be declared for a FunctionImport declaring an EntitySet. FunctionImport '{1}' does not declare an EntitySet.
?Unable to resolve to a specific overload of the function '{0}'.
;The FunctionImport '{0}' does not exist in container '{1}'.
1The FunctionImport '{0}' has already been mapped.
_The return type '{0}' of the function import '{1}' is abstract and cannot be mapped implicitly.
gImport function has a parameter '{0}' but no corresponding parameter was found in the storage function.
The storage function parameter '{0}' of type '{1}' does not match the corresponding FunctionImport parameter of enumeration type '{2}' with underlying type '{3}'. The underlying type of the enumeration parameter for a function defined in the conceptual model must match the corresponding storage function parameter type.
\Parameter '{0}' has mode '{1}' in the storage function but mode '{2}' in the FunctionImport.
uParameter '{0}' has type '{1}' in the storage that is not compatible with type '{2}' declared for the FunctionImport.
The EntityType '{0}' specified is not the declared type '{1}' nor a derivation of the type of the EntitySet '{2}' for FunctionImport '{3}'.
xNo mapping specified for the conceptual property '{0}' of type '{1}' in the result mapping of the function import '{2}'.
}The number of ResultMapping elements for the FunctionImport '{0}' does not match the number of specified ReturnType elements.
Mapping of the function import '{0}' is not valid. ComplexTypeMapping is supported only for function imports returning a collection of ComplexType.
Mapping of the function import '{0}' is not valid. EntityTypeMapping is supported only for function imports returning a collection of EntityType.
wMapping of the function import '{0}' is not valid. Storage function return type is expected to be a collection of rows.
Mapping of the function import '{0}' is not valid. Mapped type '{1}' is not compatible with the return type of the function import.
?Rows affected parameter '{0}' does not exist in function '{1}'.
LRows affected parameter '{0}' has mode '{1}'. Must have mode '{2}' or '{3}'.
PRows affected parameter '{0}' is of type '{1}'. Must be an integer numeric type.
The function import '{0}' can be mapped only to a store function that returns rows with one column. The store function '{1}' returns rows with multiple columns.
|The return type '{0}' of the function import '{1}' is not compatible with the return type '{2}' of the store function '{3}'.
*The storage function '{0}' does not exist.
The composable function import '{0}' is mapped to the non-composable store function '{1}'. Composable function imports can be mapped only to composable table-valued store functions.
The non-composable function import '{0}' is mapped to the composable store function '{1}'. Non-composable function imports can be mapped only to stored procedures.
fStorage function has a parameter '{0}' but no corresponding parameter was found in the FunctionImport.
The function import mapping cannot produce an entity from the '{0}' type hierarchy. Ensure that conditions unambiguously imply some type in the hierarchy. See line(s) '{1}'.
The function import mapping cannot produce an entity of type '{0}'. Ensure that conditions unambiguously imply the type. See line(s) '{1}'.
vThe type returned by the storage provider is not supported for type conditions. Column name: '{0}', ResultType: '{1}'.
"Mapping not valid error"
MThe EntityType '{0}' is Abstract and cannot be mapped using Function Mapping.
MThe EntityType '{0}' used in IsTypeOf does not have any concrete descendants.
GThe EntityType '{0}' is Abstract and can be mapped only using IsTypeOf.
gThe AssociationSet '{0}' cannot have a Condition because it does not provide maps for the End elements.
[The AssociationSet '{0}' specified as part of this MSL does not exist in MetadataWorkspace.
\The AssociationType '{0}' specified as part of this MSL does not exist in MetadataWorkspace.
cAssociationType Name should be specified when providing a function mapping or End property mapping.
Content not valid. The conceptual side Member or Property '{0}' specified as part of this MSL does not exist in MetadataWorkspace.
SThe Column '{0}' specified as part of this MSL does not exist in MetadataWorkspace.
YThe Complex Type '{0}' specified as part of this MSL does not exist in MetadataWorkspace.
SBoth conceptual model and column members cannot be specified for condition mapping.
KBoth Value and IsNull attributes cannot be specified for condition mapping.
Condition cannot be specified for Column member '{0}' because it is marked with a 'Computed' or 'Identity' StoreGeneratedPattern.
SEither conceptual model or Column Members must be specified for condition mapping.
JEither Value or IsNullAttribute has to be specified for condition mapping.
3Member '{0}' specified in Condition does not exist.
lCondition can not be specified on values of member '{0}'. Value conditions are not supported for type '{1}'.
7Conditions are not supported on complex-valued members.
ZExpecting only EntitySetMapping, AssociationSetMapping, or FunctionImportMapping elements.
rThe conceptual side Member or Property '{0}' has multiple mappings specified as part of the same mapping fragment.
dThe Member or Property '{0}' has multiple conditions specified as part of the same mapping fragment.
BAt least one property must be mapped in the set mapping for '{0}'.
YThe End property '{0}' specified as part of this MSL does not exist in MetadataWorkspace.
|The property '{0}' is not a key member of the EntityType. Only key members can be mapped as part of the EndProperty mapping.
uThe EntityContainer '{0}' for the conceptual model specified as part of this MSL does not exist in MetadataWorkspace.
VThe EntitySet '{0}' specified as part of this MSL does not exist in MetadataWorkspace.
WThe EntityType '{0}' specified as part of this MSL does not exist in MetadataWorkspace.
qThe EntityType '{0}' specified is not the declared type '{1}' or a derivation of the type of the EntitySet '{2}'.
RAssociationType '{0}' has a referential integrity constraint and cannot be mapped.
}AssociationType '{0}' has a primary key to primary key referential integrity constraint. Any mappings for it will be ignored.
Content in MSL is not valid.
-Unclosed parenthesis in IsOfType declaration.
rThe EntityContainer '{0}' for the storage model specified as part of this MSL does not exist in MetadataWorkspace.
RThe Table '{0}' specified as part of this MSL does not exist in MetadataWorkspace.
4A table mapping element is expected but not present.
|Only EntityTypeMapping and QueryView elements are allowed when the EntityType name is not specified on the EntitySetMapping.
FXML parsing failed for mapping schema. Schema Error Information : {0}.
PXML Schema validation failed for mapping schema. Schema Error Information : {0}.
_The AssociationType '{0}' specified is not the declared type '{1}' of the AssociationSet '{2}'.
Invalid root element found in the mapping file. Make sure that the root element's local name is 'Mapping' and the namespaceURI is '{0}', '{1}' or '{2}'.
CThe property '{0}' on the conceptual side is not a scalar property.
Member Mapping specified is not valid. The type '{0}' of member '{1}' in type '{2}' is not compatible with '{3}' of member '{4}' in type '{5}'.
pThe query view generated for the EntitySet '{0}' is not valid. The query parser threw the following error : {1}.
pThe query view specified for the EntitySet '{0}' is not valid. The query parser threw the following error : {1}.
The ResultType of the query view expression specified for the EntitySet '{0}' is not assignable to the element type of the EntitySet.
If an EntitySet or AssociationSet includes a query view, all related entity and association sets in the EntityContainer must also define query views. The following sets require query views: {0}.
GlobalItem with name '{0}' exists both in conceptual model and storage model. Make sure that every item has a unique name across conceptual model and storage model.
zMultiple object sets per type are not supported. The object sets '{0}' and '{1}' can both contain instances of type '{2}'.
[A mapping function binding specifies an ambiguous function {0} with more than one overload.
rA function mapping includes multiple result bindings for a single property. Property name: {0}. Column names: {1}.
^A function mapping for 'to' role {0} is not permitted because it is a foreign key association.
bThe EntityType '{0}' includes function mappings for AssociationSet '{1}' that requires type '{2}'.
AssociationSet instances may only be mapped using functions in one EntitySetMapping or AssociationSetMapping. The following AssociationSet instances are mapped in multiple locations: {0}.
~An association End mapping has a 'to' Role {0} with multiplicity greater than one. A maximum multiplicity of one is supported.
hAn association End mapping specifies an AssociationSet {0} that does not exist in the current container.
^An association End mapping defines a from Role {0} that is not bound to the current EntitySet.
The EntitySet '{0}' includes function mappings for AssociationSet '{1}', but none exists in element '{2}' for type '{3}'. AssociationSets must be consistently mapped for all operations.
bAn association End mapping specifies a Role {0} that does not exist in the current AssociationSet.
@Unable to find ComplexType {0} in the current MetadataWorkspace.
ZAn EntityType Mapping containing a function mapping cannot specify the TableName property.
If an EntitySet mapping includes a function binding, function bindings must be included for all types. The following types do not have function bindings: {0}.
mA mapping function bindings specifies a function {0} but does not map the following function parameters: {1}.
If some of the EntitySet or the AssociationSet mapped to the same store EntitySet, and one of the sets includes a function mapping, all related entity and AssociationSets in the EntityContainer must also define function mappings. The following sets require function mappings: {0}.
?Cannot determine the version for the current parameter binding.
A function mapping includes parameter bindings for two different Ends of the same AssociationSet. Only one End of a particular AssociationSet may be mapped within a single function mapping. End Roles: {0}, {1}. AssociationSet: {2}.
An EntityType Mapping function binding cannot map multiple types. Function mappings may be specified only for EntityType mappings for single types -- do not use the 'IsTypeOf' modifier or specify multiple types.
A mapping function binding specifies a function {0} that is not supported. Only functions that cannot be composed are supported.
A mapping function binding specifies a function {0} with an unsupported parameter: {1}. Output parameters may only be mapped through the {2} property. Use result bindings to return values from a function invocation.
*The parameter {0} is bound multiple times.
>The function parameter {0} is not defined in the function {1}.
0The property {0} does not exist in the type {1}.
_The property {0} is not a key of {1}. Association End mappings may only include key properties.
Parameter Mapping specified is not valid. The type '{0}' of member '{1}' in type '{2}' is not compatible with '{3}' of parameter '{4}' in function '{5}'.
9The EntityType {0} is mapped to functions more than once.
=A mapping function binding specifies an unknown function {0}.
OThis function mapping can only contain bindings to 'current' property versions.
PThis function mapping can only contain bindings to 'original' property versions.
IThe Complex Type {0} does not match the type of the current property {1}.
AThe mapping for EntityContainer '{0}' was not found in Workspace.
?Object mapping could not be found for Type with identity '{0}'.
<The store provider did not return a valid EdmType for '{0}'.
$The connection is not of type '{0}'.
FA single QueryView is defined for multiple types within EntitySet {0}.
LIsTypeOf( ) QueryView is already defined for EntitySet {0} and TypeName {1}.
@QueryView is already defined for EntitySet {0} and TypeName {1}.
UIsTypeOf({0}) QueryView should not be specified for {1} EntitySet's element type {0}.
^Property maps cannot be specified for EntitySet '{0}' because a query view has been specified.
dTypeName property must be defined for all but the first QueryViews within mapping for EntitySet {0}.
The Storage Map can be looked up only from the type in conceptual model. It cannot be looked up from type in the following space: {0}.
The conceptual side property '{0}' has already been mapped to a storage property with type '{1}'. If the conceptual side property is mapped to multiple properties in the storage model, make sure that all the properties in the storage model have the same type.
rStore EntitySet name should not be specified on set mapping for Set '{0}' because a query view is being specified.
RThe first QueryView must not be type-specific. Try removing the TypeName property.
nThe query view specified for '{0}' EntitySet's type(s) '{1}' contains an unsupported expression of kind '{2}'.
The query view specified for the EntitySet '{0}' includes a call to the Function '{1}'. Only storage Functions may be referenced in a query view.
The query view specified for the EntitySet '{0}' initializes an instance of type '{1}'. Only types assignable to the element type of the EntitySet are permitted.
The query view specified for the EntitySet '{0}' contains a reference to member '{1}' of kind '{2}'. Only columns may be referenced.
The query view specified for the EntitySet '{0}' includes a scan of the '{1}' EntitySet. Only storage EntitySets may be referenced in a query view.
FNo views were found in assemblies or could be generated for {0} '{1}'.
uAn object of type '{0}' with the same key already exists in an added state. An object in this state cannot be merged.
:The result of a query cannot be enumerated more than once.
XThe specified cast from a materialized '{0}' type to a nullable '{1}' type is not valid.
QThe specified cast from a materialized '{0}' type to the '{1}' type is not valid.
The cast to value type '{0}' failed because the materialized value is null. Either the result type's generic parameter or the query must use a nullable type.
,This property cannot be set to a null value.
1The property '{0}' cannot be set to a null value.
All objects in the EntitySet '{0}' must have unique primary keys. However, an instance of type '{1}' and an instance of type '{2}' both have the same primary key value.
}The '{2}' property on '{1}' could not be set to a '{3}' value. You must set this property to a non-null value of type '{0}'.
JOnly primitive types, entity types, and complex types can be materialized.
The MaxLengthAttribute on property '{0}' on type '{1} is not valid. The Length value must be greater than zero. Use MaxLength() without parameters to indicate that the string or array can have the maximum allowable length.
MaxLengthAttribute must have a Length value that is greater than zero. Use MaxLength() without parameters to indicate that the string or array can have the maximum allowable length.
LThe field {0} must be a string or array type with a maximum length of '{1}'.
UThe entity set or function import '{0}' is not defined in the entity container '{1}'.
Errors Found During Generation:
_'{0}' is not valid data space for {1}. {1} supports only DataSpace.CSpace and DataSpace.SSpace.
Cannot scaffold the next migration because the target database was created with a version of Code First earlier than EF 4.3 and does not contain the migrations history table. To start using migrations against this database, ensure the current model is compatible with the target database and execute the migrations Update process. (In Visual Studio you can use the Update-Database command from Package Manager Console to execute the migrations Update process).
Inconsistent metadata error
#Method invocation is not supported.
uThe specified target migration '{0}' does not exist. Ensure that target migration refers to an existing migration id.
In VB.NET projects, the migrations namespace '{0}' must be under the root namespace '{1}'. Update the migrations project's root namespace to allow classes under the migrations namespace to be added.
Unable to generate an explicit migration because the following explicit migrations are pending: [{0}]. Apply the pending explicit migrations before attempting to generate a new explicit migration.
YMinimum and maximum values must be greater than or equal to zero for '{0}' in type '{1}'.
rMinimum and maximum values cannot be identical for '{0}' in type '{1}' because '{0}' is not specified as constant.
mMinimum and maximum value must not be specified for '{0}' in type '{1}' since '{0}' is specified as constant.
DMinLengthAttribute must have a Length value that is zero or greater.
LThe field {0} must be a string or array type with a minimum length of '{1}'.
|Minimum value '{0}' specified for '{1}' in type '{2} is not valid. Minimum value must be always less than the maximum value.
pNumber of Properties in the Dependent and Principal Role in a relationship constraint must be exactly identical.
LThe relationship '{0}' does not contain the required referential constraint.
zMissing default value for '{0}' in type '{1}'. Default value must be specified because the '{0}' is specified as constant.
The EntitySet for the End '{0}' in AssociationSet '{1}' was not specified, and cannot be inferred because none of the EntitySet elements are of the correct type.
UThe type '{0}' is of PrimitiveTypeKind {1} which must have the facet description {2}.
!The name is missing or not valid.
8Schema must specify a value for the Namespace attribute.
The property '{0}' cannot be used as a key property on the entity '{1}' because the property type is not a valid key type. Only scalar types, string and byte[] are supported key types.
hThe type '{0}' cannot be used to filter properties. Only scalar types, string, and byte[] are supported.
Unable to determine composite primary key ordering for type '{0}'. Use the ColumnAttribute (see http://go.microsoft.com/fwlink/?LinkId=386388) or the HasKey method (see http://go.microsoft.com/fwlink/?LinkId=386387) to specify an order for composite primary keys.
A parameter binding to the property '{0}' was not found on the modification function '{1}'. Ensure that the parameter is valid for this modification operation and that it is not database generated.
An original value parameter binding to the property '{0}' was not found on the modification function '{1}'. Ensure that the parameter is a concurrency token.
'Sequence contains more than one element
GMore than one item in the metadata collection match the identity '{0}'.
0Sequence contains more than one matching element
The assembly '{0}' contains more than one type derived from '{1}'. Either use DbConfigurationTypeAttribute on the DbContext type to specify the DbConfiguration type, define the DbConfiguration type to use in the application's config file, or ensure that the assembly contains at most one type derived from '{1}'.
KThe parameter '{0}' was defined more than once in the parameter collection.
IThe variable '{0}' was defined more than once in the variable collection.
Multiple potential primary key properties named '{0}' but differing only by case were found on entity type '{1}'. Configure the primary key explicitly using the HasKey fluent API or the KeyAttribute data annotation.
(Multiset element types are incompatible.
AThe namespace alias '{0}' was used in a previous USING directive.
)The namespace '{0}' was already imported.
UThe navigation property '{0}' declared on type '{1}' cannot be the inverse of itself.
The navigation property '{0}' is not a declared property on type '{1}'. Verify that it has not been explicitly excluded from the model and that it is a valid navigation property.
The EntityType '{0}' that the NavigationProperty '{1}' is declared on is not the same type '{4}' referred by the end '{3}' of the RelationshipType '{2}' that this NavigationProperty represents.
The namespace '{0}' is a system namespace and is implicitly referred by every schema. You cannot specify an explicit reference to this namespace.
DThe nested aggregate {0} cannot be used inside of the aggregate {1}.
QType '{0}' in Assembly '{1}' is a nested class. Nested classes are not supported.
The type '{0}' that is being loaded conflicts with the type '{1}' that is already loaded because they have the same namespace and name.
WNo overload of aggregate function '{0}.{1}' is compatible with argument types in '{2}'.
No overload of canonical aggregate function '{0}.{1}' is compatible with the argument types in '{2}'. Consult provider-specific function documentation for store functions with similar functionality.
No overload of canonical function '{0}.{1}' is compatible with the argument types in '{2}'. Consult provider-specific function documentation for potential store functions with similar functionality.
IThe '{0}' namespace is reserved for the Entity Framework code generation.
-The space '{0}' has no associated collection.
QNo overload of function '{0}.{1}' is compatible with the argument types in '{2}'.
%Sequence contains no matching element
No MigrationSqlGenerator found for provider '{0}'. Use the SetSqlGenerator method in the target migrations configuration class to register additional SQL generators.
>No property with the name '{0}' is declared by the type '{1}'.
NArgument '{0}' is invalid. The specified function is not marked as composable.
\Functions that cannot be composed may not set the aggregate or built-in function attributes.
AFunctions that cannot be composed must not declare a return type.
fThe Mode of all parameters in the ReturnParameter collection must be set to ParameterMode.ReturnValue.
~'{0}' is not a member of '{1}'. To extract a property of a collection element, use a sub-query to iterate over the collection.
D'{0}' is not a member of type '{1}' in the currently loaded schemas.
;Type '{0}' is neither a sub-type nor a super-type of '{1}'.
'The PrimitiveType is not a binary type.
6The given primitive type is not a DateTimeOffset type.
)The PrimitiveType is not a DateTime type.
(The PrimitiveType is not a Decimal type.
5Type {0} is not defined in namespace {1} (Alias={2}).
)Type {0} is not defined in namespace {1}.
pThe Type {0} is not qualified with a namespace or alias. Only primitive types can be used without qualification.
'The PrimitiveType is not a string type.
,The given primitive type is not a Time type.
fAt least one of the input paths is not valid because either it is too long or it has incorrect format.
YThe EntitySets parameter must not be null for functions that return multiple result sets.
6A NULL literal cannot be promoted to a CollectionType.
SThe EdmRelationshipAttribute for the relationship '{1}' has a null parameter '{0}'.
\The RelationshipName parameter of an EdmRelationshipAttribute in the assembly '{0}' is null.
GThe number of entity sets should match the number of return parameters.
/The type constructor argument '{0}' is missing.
^The number of arguments passed to the type '{0}' constructor exceeds its formal specification.
The changes to the database were committed successfully, but an error occurred while updating the object context. The ObjectContext might be in an inconsistent state. Inner exception message: {0}
SAn object with a temporary EntityKey value cannot be attached to an object context.
NAn object with a null EntityKey value cannot be attached to an object context.
PThe object cannot be deleted because it was not found in the ObjectStateManager.
SThe object cannot be detached because it is not attached to the ObjectStateManager.
Cannot explicitly load {0} for entities that are detached. Objects loaded using the NoTracking merge option are always detached.
UCannot load {0} using a context different than that with which the object was loaded.
The DefaultContainerName property has already been set for this ObjectContext. This property cannot be changed after it has been set.
\The following objects have not been refreshed because they were not found in the store: {0}.
The operation failed: The relationship could not be changed because one or more of the foreign-key properties is non-nullable. When a change is made to a relationship, the related foreign-key property is set to a null value. If the foreign-key does not support null values, a new relationship must be defined, the foreign-key property must be assigned another non-null value, or the unrelated object must be deleted.
The EntityContainer name could not be determined. The provided EntitySet name must be qualified by the EntityContainer name, such as 'EntityContainerName.EntitySetName', or the DefaultContainerName property must be set for the ObjectContext.
The object in the ObjectContext is of type '{0}', but the modified object provided is of type '{1}'. The two objects must be of the same EntityType for changes to be applied.
The object cannot be attached because it is already in the object context. An object can only be reattached when it is in an unchanged state.
2The EntityContainer name '{0}' could not be found.
The existing object in the ObjectContext is in the {0} state. Changes can only be applied when the existing object is in an unchanged or modified state.
The existing object in the ObjectContext is in the {0} state. Original values can be changed when the existing object is in an unchanged, modified or deleted state.
The specified entity cannot be deleted from the ObjectSet because the entity is a member of the EntitySet '{0}.{1}' instead of the EntitySet '{2}.{3}' that is referenced by the ObjectSet. Use the DeleteObject method on the ObjectSet that contains the entity, or use the ObjectContext.DeleteObject method if you want to delete the entity without validating its EntitySet.
The specified entity cannot be detached from the ObjectSet because the entity is a member of the EntitySet '{0}.{1}' instead of the EntitySet '{2}.{3}' that is referenced by the ObjectSet. Use the Detach method on the ObjectSet that contains the entity, or use the ObjectContext.Detach method if you want to delete the entity without validating its EntitySet.
An object that has a key that matches the key of the supplied object could not be found in the ObjectStateManager. Verify that the object to which changes must be applied is not in the Added state and that its key values match the key values of the supplied object.
The EntitySet name could not be determined. To attach an object, supply a valid EntitySet name and make sure that the object has a valid EntityKey.
,The EntitySet name '{0}' could not be found.
WWhen executing a command, parameters must be exclusively database parameters or values.
The stored procedure or function '{0}' does not have a return type. ExecuteFunction only supports stored procedures and functions that have a return type.
;The parameter at index {0} in the parameters array is null.
The stored procedure or function '{1}' returned the type '{0}'. ExecuteFunction only supports stored procedures and functions that return collections of entity objects or collections of complex objects.
jThe type parameter '{0}' in ExecuteFunction is incompatible with the type '{1}' returned by the function.
NThe specified CommandTimeout value is not valid. It must be a positive number.
fThe supplied connection is not valid because it contains insufficient mapping or metadata information.
nThe supplied connection string is not valid, because it contains insufficient mapping or metadata information.
lThe specified default EntityContainer name '{0}' could not be found in the mapping and metadata information.
IThe specified EntitySet '{0}.{1}' does not contain results of type '{2}'.
oThe EntitySet name '{0}.{1}' from the object's EntityKey does not match the expected EntitySet name, '{2}.{3}'.
The EntitySet name '{0}.{1}' from the entity's EntityKey does not match the expected EntitySet name '{2}.{3}' from the '{4}' parameter.
ZThe EntitySet, '{0}', from the entity's EntityKey does not match the entity's type, '{1}'.
The EntityState value passed for the entity is not valid. The EntityState value must be one of the following: Added, Deleted, Detached, Modified, or Unchanged.
YThe specified entity type, '{0}', does not match the type '{1}' from the EntitySet '{2}'.
The EntityState value passed for the relationship is not valid. The EntityState value must be one of the following: Added, Deleted, Detached, or Unchanged. Relationships cannot be set to the Modified state.
QThe result type '{0}' may not be abstract and must include a default constructor.
The EntitySet could not be determined for the specified entity type '{0}' because there is more than one EntitySet defined for this type in multiple EntityContainers in the metadata. Use the overload of the CreateObjectSet<TEntity>() method that takes a string parameter if you want to use the TEntity type and a specific EntitySet.
The EntitySet could not be determined for the specified entity type '{0}' because there is more than one EntitySet defined for this type in the EntityContainer '{1}'. Use the overload of the CreateObjectSet<TEntity>() method that takes a string parameter if you want to use the TEntity type and a specific EntitySet.
{There are no EntitySets defined for the specified entity type '{0}'. If '{0}' is a derived type, use the base type instead.
IMapping and metadata information could not be found for EntityType '{0}'.
The element at index {0} in the collection of objects to refresh is in the added state. Objects in this state cannot be refreshed.
The element at index {0} in the collection of objects to refresh is a duplicate of an object that is already in the collection.
IThe element at index {0} in the collection of objects to refresh is null.
The element at index {0} in the collection of objects to refresh has a null EntityKey property value or is not attached to this ObjectStateManager.
pThe ObjectContext instance has been disposed and can no longer be used for operations that require a connection.
@An object with the specified EntityKey value could not be found.
The provided EntitySet name must be qualified by the EntityContainer name, such as 'EntityContainerName.EntitySetName', or the DefaultContainerName property must be set for the ObjectContext.
QThe selector expression for LoadProperty must be a MemberAccess for the property.
\The refresh attempt has failed because an unexpected entity was returned by the data source.
kThe '{0}' column is mapped to multiple properties '{1}'. Ensure a separate column exists for each property.
A parameter named '{0}' already exists in the parameter collection. Parameter names must be unique in the parameter collection.
tA parameter '{0}' already exists in the parameter collection. Parameters must be unique in the parameter collection.
BA parameter named '{0}' was not found in the parameter collection.
Parameters cannot be added or removed from the parameter collection, and the parameter collection cannot be cleared after a query has been evaluated or its trace string has been retrieved.
The specified parameter name '{0}' is not valid. Parameter names must begin with a letter and can only contain letters, numbers, and underscores.
The specified parameter type '{0}' is not valid. Only scalar types, such as System.Int32, System.Decimal, System.DateTime, and System.Guid, are supported.
@A connection must be specified before the query can be executed.
The specified query name '{0}' is not valid. Query names must begin with a letter and can only contain letters, numbers, and underscores.
rThe specified ObjectQuery is not valid for this operation because it is associated with a different ObjectContext.
x'{0}' is not a valid type for type filtering operations. Type filtering is only valid on entity types and complex types.
Query builder methods are not supported for LINQ to Entities queries. For more information, see the Entity Framework documentation.
The result type of the query is neither an EntityType nor a CollectionType with an entity element type. An Include path can only be specified for a query with one of these result types.
wA specified Include path is not valid. The EntityType '{0}' does not declare a navigation property with the name '{1}'.
TThere was an error parsing the Include path. An empty navigation property was found.
^The result type of the query could not be determined because the required metadata is missing.
The collection in the projection is of type '{0}'. For a collection to be materialized to a projection, it must be of type ICollection<T>, IList<T>, ISet<T> or of a concrete type that implements ICollection<T> and has a parameterless constructor.
[The array type '{0}' cannot be initialized in a query result. Consider using '{1}' instead.
[The ObjectStateEntry is a key entry and its current and original values are not accessible.
LThe ObjectStateEntry is a key entry. Delete cannot be called on key entries.
EThe ObjectStateEntry is a key entry and its state cannot be modified.
SThe property '{0}' is part of the object's key information and cannot be modified.
cThe object is in a detached or deleted state. An ObjectStateEntry in this state cannot be modified.
cThe ObjectStateEntry is a relationship entry. The state of relationship entries cannot be modified.
yThe ObjectStateEntry is a relationship entry. The current and original values of relationship entries cannot be modified.
VThe EntityKey property can only be set when the current value of the property is null.
The property '{0}' does not have a valid entity mapping on the complex type. For more information, see the Entity Framework documentation.
The property '{0}' does not have a valid entity mapping on the entity object. For more information, see the Entity Framework documentation.
The change cannot be tracked because the state of the object changed from '{0}' to '{1}' since the previous call to EntityMemberChanging or EntityComplexMemberChanging on the same change tracker with the same property name. For information about properly reporting changes, see the Entity Framework documentation.
The entity of type '{0}' references the same complex object of type '{1}' more than once. Complex objects cannot be referenced multiple times by the same entity.
vThis ObjectStateEntry does not have current values. Objects in a deleted or detached state cannot have current values.
EntityMemberChanged or EntityComplexMemberChanged was called without first calling EntityMemberChanging or EntityComplexMemberChanging on the same change tracker with the same property name. For information about properly reporting changes, see the Entity Framework documentation.
yThe object is in a detached state. This operation cannot be performed on an ObjectStateEntry when the object is detached.
The value for the complex property could not be set. Complex properties must be set to an object that implements IExtendedDataRecord.
The original value for the property '{0}' cannot be set to null because the '{1}' member on the entity type '{2}' is not nullable.
xThis ObjectStateEntry does not have original values. Objects in an added or detached state cannot have original values.
A RelationshipManager object cannot be returned for this ObjectStateEntry instance. Only an ObjectStateEntry that represents an entity has an associated RelationshipManager.
YProperty '{0}' is not a valid property on the object referenced by this ObjectStateEntry.
P{0} cannot be called because the object is not in a modified or unchanged state.
The original value for the property '{0}' cannot be set because it is a complex property. Individual scalar properties can be set on a complex type if the type is first obtained as a OriginalValueRecord from the entity's original values.
iThe original value for the property '{0}' cannot be set because the property is part of the entity's key.
The navigation property '{0}' on entity of type '{1}' must implement ICollection<T> in order for Entity Framework to be able to track changes in collections.
AcceptChanges cannot continue because the object's EntityKey value is null or is not a temporary key. This can happen when the EntityKey property is modified while the object is in an added state.
Cannot change relationship's state to the state other than added or detached if the source or target entity is in the added state.
Cannot change relationship's state to the state other than deleted or detached if the source or target entity is in the deleted state.
[Cannot change state of a relationship if one of the ends of the relationship is a KeyEntry.
Saving or accepting changes failed because more than one entity of type '{0}' have the same primary key value. Ensure that explicitly set primary key values are unique. Ensure that database-generated primary keys are configured correctly in the database and in the Entity Framework model. Use the Entity Designer for Database First/Model First configuration. Use the 'HasDatabaseGeneratedOption" fluent API or 'DatabaseGeneratedAttribute' for Code First configuration.
A RelationshipManager cannot be returned for this object. A RelationshipManager can only be returned for objects that are either tracked by the ObjectStateManager or that implement IEntityWithRelationships.
sThe ChangeRelationshipState method is not supported for relationships that are defined by using foreign-key values.
The object state cannot be changed. This exception may result from one or more of the primary key properties being set to null. Non-Added objects cannot have null primary key values. See inner exception for details.
SConflicting changes to the role '{0}' of the relationship '{1}' have been detected.
CObjects in a detached state do not exist in the ObjectStateManager.
An object with the same key already exists in the ObjectStateManager. The existing object is in the {0} state. An object can only be added to the ObjectStateManager again if it is in the added state.
The object cannot be added to the object context. The object's EntityKey has an ObjectStateEntry that indicates that the object is already participating in a different relationship.
An object with a key that matches the key of the supplied object could not be found in the ObjectStateManager. Verify that the key values of the supplied object match the key values of the object to which changes must be applied.
7EntityType '{0}' does not exist in the EntitySet '{1}'.
*The object's EntityKey value is not valid.
The value of a property that is part of an object's key does not match the corresponding property value stored in the ObjectContext. This can occur if properties that are part of the key return inconsistent or incorrect values or if DetectChanges is not called after changes are made to a property that is part of the key.
The object cannot be attached because the value of a property that is a part of the EntityKey does not match the corresponding value in the EntityKey.
UThe supplied EntityKey does not have a corresponding entry in the ObjectStateManager.
hThe ObjectStateManager does not contain an ObjectStateEntry with a reference to an object of type '{0}'.
Attaching an entity of type '{0}' failed because another entity of the same type already has the same primary key value. This can happen when using the 'Attach' method or setting the state of an entity to 'Unchanged' or 'Modified' if any entities in the graph have conflicting key values. This may be because some entities are new and have not yet received database-generated key values. In this case use the 'Add' method or the 'Added' entity state to track the graph and then set the state of non-new entities to 'Unchanged' or 'Modified' as appropriate.
The IBindingList.AddNew method is not supported when binding to a collection of abstract types. You must instead use the IList.Add method.
HThe object or data row on the data binding interface cannot be replaced.
The object could not be added to the bound collection. The specific EntitySet for the object of type '{0}' could not be determined.
aThe object being added is of a type that is not compatible with the type of the bound collection.
QThe index-based insert operation is not supported on this data binding interface.
BUpdates cannot be performed on a read-only data binding interface.
]The OFTYPE collection element type must refer to an EntityType. The passed type is {0} '{1}'.
^The OFTYPE collection element type must refer to a nominal type. The passed type is {0} '{1}'.
MThe OFTYPE ONLY type argument is not valid because '{0}' is an abstract type.
]The function '{0}' is not marked as FunctionImport and cannot be added to the EntityContainer
MEntity connections are not supported; only storage connections are supported.
FThe operation cannot be performed because the collection is read only.
@The operation cannot be performed because the item is read only.
7The ORDER BY sort key(s) type must be order-comparable.
The index with name '{0}' on table '{1}' has the same column order of '{2}' specified for columns '{3}' and '{4}'. Make sure a different order value is used for the IndexAttribute on each column of a multi-column index.
vThe table '{0}' was configured but is not used in any mappings. Verify the mapping configuration for '{0}' is correct.
_Each parameter name in a function must be unique. The parameter name '{0}' was already defined.
;The command parameter '{0}' of type '{1}' is not supported.
,The command parameter '{0}' was not defined.
>INTERNAL ERROR: The parser found an error and cannot continue.
.INTERNAL ERROR: The input stream is not valid.
The Foreign Key on table '{0}' with columns '{1}' could not be created because the principal key columns could not be determined. Use the AddForeignKey fluent API to fully specify the Foreign Key.
ZThe {0} expression type must be promotable to an Edm.Int64 type. The passed type is '{1}'.
NThe {0} expression must be a command parameter or an integral numeric literal.
?The {0} expression value must be greater than or equal to zero.
The {0} operand of {1} is not valid because its type '{2}' cannot be compared for equality. Only primitive, enumeration, entity, row, and reference types can be compared for equality.
6The left expression must be of numeric or string type.
7The right expression must be of numeric or string type.
The collection navigation property '{0}' of type '{1}' returned null. For a collection to be initialized automatically, it must be of type ICollection<T>, IList<T>, ISet<T> or of a concrete type that implements ICollection<T> and has a parameterless constructor.
TUnable to set field/property {0} on entity type {1}. See InnerException for details.
NThe navigation property of type '{0}' is not a single implementation of '{1}'.
;The precision '{0}' must be greater than the scale '{1}'.
WPrecision '{0}' is not valid. Precision must be between '{1}' and '{2}' for '{3}' type.
UEach property name in a type must be unique. Property name '{0}' was already defined.
The property '{0}' is not a declared property on type '{1}'. Verify that the property has not been explicitly excluded from the model by using the Ignore method or NotMappedAttribute data annotation. Make sure that it is a valid primitive property.
G{0} property is not valid. A type is already defined for this property.
0The provider did not create a CommandDefinition.
8The provider did not return a ProviderManifest instance.
;The provider did not return a ProviderManifestToken string.
The provider did not return a 'DbSpatialServices' instance. In order to use the 'DbGeography' or 'DbGeometry' spatial types the EF provider being used must support spatial types and all prerequisites for the provider must be installed. See http://go.microsoft.com/fwlink/?LinkId=287183 for details.
0CreateDatabase is not supported by the provider.
6CreateDatabaseScript is not supported by the provider.
0DatabaseExists is not supported by the provider.
0DeleteDatabase is not supported by the provider.
BEscaping within like expressions is not supported by the provider.
QThe underlying provider returned null when trying to escape the specified string.
The provider for invariant name '{0}' is specified in the application configuration multiple times with different provider type names. The provider type names have to be unique for each configured provider.
4The storage provider manifest could not be obtained.
Unable to determine the provider name for provider factory of type '{0}'. Make sure that the ADO.NET provider is installed or registered in the application config.
Unable to determine the DbProviderFactory type for connection of type '{0}'. Make sure that the ADO.NET provider is installed or registered in the application config.
This provider does not support the specified command tree. EntityClient should be used to create a command definition from this command tree.
8The provider returned null from CreateCommandDefinition.
9The provider returned null for the informationType '{0}'.
Because the underlying provider had overridden DbProviderManifest.SupportsEscapingLikeArgument to return true, the DbProviderManifest.EscapeLikeArgument method must also be implemented by the provider.
AThe REF argument must be of EntityType. The passed type is '{0}'.
[The REF argument must specify an EntityType. The type specification '{0}' represents '{1}'.
^ReferenceType element can only refer to an EntityType. '{0}' is not declared as an EntityType.
TThe related end expression type '{0}' must be promotable to the 'to' end type '{1}'.
5The related end expression must be of reference type.
<An item cannot be added to a fixed size Array of type '{0}'.
The object in the '{0}' role cannot be automatically added to the context because it was retrieved using the NoTracking merge option. Explicitly attach the entity to the ObjectContext before defining the relationship.
xThe relationship between the two objects cannot be defined because they are attached to different ObjectContext objects.
@An item cannot be removed from a fixed size Array of type '{0}'.
The {0} object could not be serialized. This type of object cannot be serialized when the RelationshipManager belongs to an entity object that does not implement IEntityWithRelationships.
The relationship cannot be defined because the EntitySet name '{0}.{1}' is not valid for the role '{2}' in association set name '{3}.{4}'.
{An object of type '{0}' cannot be added, attached, or removed from an EntityCollection that contains objects of type '{1}'.
mAn object of type '{0}' cannot be set or removed from the Value property of an EntityReference of type '{1}'.
nThe object being attached to the source object is not attached to the same ObjectContext as the source object.
uThe object being attached is in an added or deleted state. Relationships cannot be created for objects in this state.
The object at index {0} in the specified collection of objects is not attached to the same ObjectContext as source object of this EntityCollection.
GThe object at index {0} in the specified collection of objects is null.
The object at index {0} in the specified collection of objects is in an added or deleted state. Relationships cannot be created for objects in this state.
Attach is not a valid operation when the source object associated with this related end is in an added, deleted, or detached state. Objects loaded using the NoTracking merge option are always detached.
tWhen an object is returned with a NoTracking merge option, Load cannot be called when the IsLoaded property is true.
When an object is returned with a NoTracking merge option, Load can only be called when the EntityCollection or EntityReference does not contain objects.
Related objects cannot be loaded using the {0} merge option. Relationships cannot be created when one object was retrieved using a NoTracking merge option and the other object was retrieved using a different merge option.
Requested operation is not allowed when the owner of this RelatedEnd is null. RelatedEnd objects that were created with the default constructor should only be used as a container during serialization.
KThe {0} could not be loaded because it is not attached to an ObjectContext.
@At least one related end in the relationship could not be found.
The object could not be added to the EntityCollection or EntityReference. An object that is attached to an ObjectContext cannot be added to an EntityCollection or EntityReference that is not associated with a source object.
RAdding a relationship with an entity which is in the Deleted state is not allowed.
The object could not be removed from the EntityCollection or EntityReference. An object that is attached to an ObjectContext cannot be removed from an EntityCollection or EntityReference that is not associated with a source object.
@The 'from' end of the relationship is ambiguous in this context.
The RelatedEnd cannot be returned by this RelationshipManager. A RelatedEnd can only be returned by a RelationshipManager for objects that are either tracked by the ObjectStateManager or that implement IEntityWithRelationships.
A circular relationship path has been detected while enforcing a referential integrity constraints. Referential integrity cannot be enforced on circular relationships.
6The EntityCollection has already been initialized. {0}
The InitializeRelatedCollection method should only be called to initialize a new EntityCollection during deserialization of an object graph.
The EntityCollection could not be initialized because the relationship manager for the object to which the EntityCollection belongs is already attached to an ObjectContext. {0}
A referential integrity constraint violation occurred: The property value(s) of '{0}' on one end of a relationship do not match the property value(s) of '{1}' on the other end.
~InitializeRelatedReference should only be used to initialize a new EntityReference during deserialization of an entity object.
The relationship manager supplied by the object implementing IEntityWithRelationships is not the expected relationship manager.
The relationship '{0}' does not contain the role '{1}'. Make sure that EdmRelationshipAttribute that defines this relationship has the correct role names. For more information, see the Entity Framework documentation.
9The specified navigation property {0} could not be found.
The relationship manager was defined with an owner of type '{0}', which is not compatible with the type '{1}' for the source role '{2}' in the specified relationship, '{3}'.
5The EntityReference has already been initialized. {0}
The EntityReference could not be initialized, because the relationship manager for object to which the entity reference belongs is already attached to an ObjectContext. {0}
Metadata information for the relationship '{0}' could not be retrieved. If mapping attributes are used, make sure that the EdmRelationshipAttribute for the relationship has been defined in the assembly. When using convention-based mapping, metadata information for relationships between detached entities cannot be determined.
A referential integrity constraints violation occurred: Not all of the property values that define referential integrity constraints could be retrieved from related entities.
The requested operation could not be completed because the object implementing IEntityWithRelationships returned a null value from the RelationshipManager property.
The operation could not be completed because the object to which the relationship manager belongs was attached to the ObjectContext before the relationship manager was instantiated.
EdmRelationshipNavigationPropertyAttribute on NavigationProperty '{0}' in EntityType '{1}' has a RelationshipName '{2}' that is not valid. Make sure the RelationshipName is valid.
$The target end '{0}' must be unique.
>The 'to' end of the relationship is ambiguous in this context.
5The specified type '{0}' must be a relationship type.
9Facet '{0}' must be specified for '{1}' typed properties.
A result binding for the property '{0}' was not found on the modification function '{1}'. Ensure that the property is database generated.
>The resulting expression of the query cannot be un-typed NULL.
\Parameters in the Parameters collection must not have mode set to ParameterMode.ReturnValue.
CThe right argument of the set expression must be of CollectionType.
The property for the relationship '{0}' contains a Role '{1}' has a type '{2}' that is not valid for a relationship End. Change the End Role to an EntityType.
6The ROW constructor cannot have un-typed NULL columns.
8RowType element must have at least one property element.
Both Ends on the EdmRelationshipAttribute for relationship '{0}' have the same Role name '{1}'. The ends of a relationship type must have different Role names.
In relationship '{0}', the Principal and Dependent Role of the referential constraint refers to the same Role in the relationship type.
RScaffolding create or alter procedure operations is not supported in down methods.
OScale '{0}' is not valid. Scale must be between '{1}' and '{2}' for '{3}' type.
PThe projection expression type must be equal-comparable when used with DISTINCT.
_Serializer can only serialize an EdmModel that has one EdmNamespace and one EdmEntityContainer.
An instance of '{0}' was set but this type was not discovered in the same assembly as the '{1}' context. Either put the DbConfiguration type in the same assembly as the DbContext type, use DbConfigurationTypeAttribute on the DbContext type to specify the DbConfiguration type, or set the DbConfiguration type in the config file. See http://go.microsoft.com/fwlink/?LinkId=260883 for more information.
Failed to set Database.DefaultConnectionFactory to an instance of the '{0}' type as specified in the application configuration. See inner exception for details.
In EntityContainer '{4}', Role '{0}' in '{1}' and '{2}' AssociationSet refers to the same EntitySet '{3}'. Make sure that if two or more AssociationSet refer to the same AssociationType, the ends must not refer to the same EntitySet.
The type '{0}' and the type '{1}' both have the same simple name of '{2}' and so cannot be used in the same model. All types in a given model must have unique simple names. Use 'NotMappedAttribute' or call Ignore in the Code First fluent API to explicitly exclude a property or type from the model.
SThe relationship source type '{0}' must be promotable to the 'from' end type '{1}'.
<File Unknown>
No usable spatial provider could be found. In order to use the 'DbGeography' or 'DbGeometry' spatial types the EF provider being used must support spatial types and all prerequisites for the provider must be installed. See http://go.microsoft.com/fwlink/?LinkId=287183 for details.
Currently, spatial types are only supported when used in CSDL files that have the UseStrongSpatialTypes annotation with a false value on their root Schema element.
\The specified DbGeography value is not compatible with this spatial services implementation.
[The specified DbGeometry value is not compatible with this spatial services implementation.
YThe specified provider value is not compatible with this spatial services implementation.
tThe WellKnownValue property is intended to support serialization and deserialization and should not be set directly.
The database name '{0}' is not supported because it is an MDF file name. A full connection string must be provided to attach an MDF file.
?INTERNAL ERROR: There was a stack overflow in the query parser.
WInvalid complex property mapping. The entity model property must be a complex property.
Storage EntityContainer name '{0}' specified in this mapping schema doesn't match with the storage EntityContainer name '{1}' specified in the previous mapping schema(s) for EntityContainer '{2}' in the conceptual model. Make sure that you specify exactly one mapping per EntityContainer, or if you want to specify partial mapping, make sure that they map to the same storage EntityContainer.
gInvalid scalar property mapping. Both entity model property and store column must be scalar properties.
OArgument '{0}' is not valid. A minimum of one .ssdl artifact must be supplied.
DThe store type '{0}' could not be found in the {1} provider manifest
The StringLengthAttribute on property '{0}' on type '{1}' is not valid. The maximum length must be greater than zero. Use MaxLength() without parameters to indicate that the string or array can have the maximum allowable length.
dStructural type mappings must not be null or empty for function imports returning non-scalar values.
The operation could not be suppressed because it has already been executed. 'SuppressExecution' can only be called from an interceptor that runs before the operation is executed.
mThe namespace '{0}' is a system namespace and cannot be used by other schemas. Choose another namespace name.
SAll properties of the row type returned by a store-defined function must be scalar.
The EntitySet '{0}' has both a Table or Schema attribute and a DefiningQuery element. The Table and Schema attributes on EntitySet are mutually exclusive with the DefiningQuery element. Use only the Table and Schema attributes or the DefiningQuery element.
nThe specified table '{0}' was not found in the model. Ensure that the table name has been correctly specified.
EdmRelationshipNavigationPropertyAttribute for RelationshipType '{3}' on NavigationProperty '{0}' in EntityType '{1}' has a TargetRole name '{2}' that is not valid. Make sure that TargetRole name is a valid name.
The member '{0}' has not been implemented on type '{1}' which inherits from '{2}'. Test doubles for '{2}' must provide implementations of methods and properties that are used.
[Conversion between generic and non-generic DbSet objects is not supported for test doubles.
7The current schema element does not support text ({0}).
QThe Association {0} is not valid. Associations may only contain two End elements.
Could not load assembly '{0}'. (If you are using Code First Migrations inside Visual Studio this can happen if the startUp project for your solution does not reference the project that contains your migrations. You can either change the startUp project for your solution or use the -StartUpProjectName parameter.)
SThe TOP and LIMIT sub-clauses cannot be used together in the same query expression.
lThe TOP and SKIP sub-clauses cannot be used together in the same query expression. Use LIMIT instead of TOP.
6Failed to commit transaction at {0} with error: {1}{2}
Committed transaction at {0}{1}
Disposed transaction at {0}{1}
AThis instance of TransactionHandler has already been initialized.
8Failed to rollback transaction at {0} with error: {1}{2}
!Rolled back transaction at {0}{1}
5Failed to start transaction at {0} with error: {1}{2}
Started transaction at {0}{1}
/'{0}' is less than the minimum supported value.
_The type specification has an incorrect number of arguments. The '{0}' type has {1} parameters.
2'{0}' is greater than the maximum supported value.
WThe type argument is not a valid constant literal, or is outside of the expected range.
;The type specification argument must be a constant literal.
EType must be declared through attribute or sub-element, but not both.
+'{0}' does not support '{1}' specification.
*'{0}' does not support type specification.
x{0} member '{1}' and {2} member '{3}' are not compatible for this operation, because they are not the same kind of type.
The types of all properties in the Dependent Role of a referential constraint must be the same as the corresponding property types in the Principal Role. The type of property '{0}' on entity '{1}' does not match the type of property '{2}' on entity '{3}' in the referential constraint '{4}'.
%Type declaration missing for element.
QThe '{0}' type argument must specify an EntityType. The passed type is {1} '{2}'.
EThe expression type must be EntityType, ComplexType, or ReferenceType
RThe '{0}' type argument must specify a nominal type, The passed type is {1} '{2}'.
OEach type name in a schema must be unique. Type name '{0}' was already defined.
}Type '{0}' could not be found. Make sure that the required schemas are loaded and that the namespaces are imported correctly.
pThe type '{0}' specified is not the declared type '{1}' or a derivation of the type of the AssociationSet '{2}'.
kThe type '{0}' specified is not the declared type '{1}' or a derivation of the type of the EntitySet '{2}'.
\Unable to determine application context. The ASP.NET application path could not be resolved.
Unable to determine the principal end of an association between the types '{0}' and '{1}'. The principal end of this association must be explicitly configured using either the relationship fluent API or data annotations.
eUnable to call public, instance method AddOrUpdate on derived IDbSet<T> type '{0}'. Method not found.
,Unable to find type '{0}' in assembly '{1}'.
;Unable to load embedded resource '{1}' from assembly '{0}'.
/Unable to load the specified metadata resource.
Automatic migrations that affect the location of the migrations history system table (such as default schema changes) are not supported. Please use code-based migrations for operations that affect the location of the migrations history system table.
!Unable to resolve assembly '{0}'.
An existing EF5 migrations history table was detected but could not be upgraded because a custom history context factory has been configured. To upgrade an existing EF5 database, ensure there is no custom history context factory configured.
CURI {0} is not acceptable. URIs must be absolute or specify a file.
The element {1} in namespace {0} was unexpected for the root element. The expected Schema in one of the following namespaces: {2}.
qThe element {1} was unexpected for the root element. The expected Schema in one of the following namespaces: {2}.
6Element of unexpected type {0} was found at index {1}.
#Unrecognized schema attribute: {0}.
!Unrecognized schema element: {0}.
Unexpected XmlNode type: {0}.
The context is being used in Code First mode with code that was generated from an EDMX file for either Database First or Model First development. This will not work correctly. To fix this problem do not remove the line of code that throws this exception. If you wish to use Database First or Model First, then make sure that the Entity Framework connection string is included in the app.config or web.config of the start-up project. If you are creating your own DbConnection, then make sure that it is an EntityConnection and not some other type of DbConnection, and that you pass it to one of the base DbContext constructors that take a DbConnection. To learn more about Code First, Database First, and Model First see the Entity Framework documentation here: http://go.microsoft.com/fwlink/?LinkId=394715
[INTERNAL ERROR: The abstract syntax tree expression is not a valid command expression type.
HINTERNAL ERROR: The abstract syntax tree expression has an unknown type.
XINTERNAL ERROR: The specified built-in abstract syntax tree expression type is unknown.
EINTERNAL ERROR: The expression resolution has an unknown class '{0}'.
The abstract type '{0}' has no mapped descendants and so cannot be mapped. Either remove '{0}' from the model or add one or more types deriving from '{0}' to the model.
The type '{0}' cannot be mapped as defined because it maps inherited properties from types that use entity splitting or another form of inheritance. Either choose a different inheritance mapping strategy so as to not map inherited properties, or change all types in the hierarchy to map inherited properties and to not use splitting.
The enum or spatial property '{1}' on type '{0}' cannot be mapped. Use DbModelBuilderVersion 'V5_0' or later to map enum or spatial properties.
wUnable to determine the principal end of the '{0}' relationship. Multiple added entities may have the same primary key.
A value shared across entities or associations is generated in more than one location. Check that mapping does not split an EntityKey to multiple store-generated columns.
GCircular relationships with referential integrity constraints detected.
Store update, insert, or delete statement affected an unexpected number of rows ({0}). Entities may have been modified or deleted since entities were loaded. See http://go.microsoft.com/fwlink/?LinkId=472540 for information on understanding and handling optimistic concurrency exceptions.
Unable to determine a valid ordering for dependent operations. Dependencies may exist due to foreign key constraints, model requirements, or store-generated values.
hConflicting changes detected. This may happen when trying to insert multiple entities with the same key.
OError retrieving values from ObjectStateEntry. See inner exception for details.
RAn error occurred while updating the entries. See the inner exception for details.
eA dependent property in a ReferentialConstraint is mapped to a store-generated column. Column: '{0}'.
dUnable to insert or update an entity because the principal end of the '{0}' relationship is deleted.
Invalid data encountered. A required relationship is missing. Examine StateEntries to determine the source of the constraint violation.
-Update Mapping not found for EntitySet '{0}'.
In order to update the AssociationSet '{0}', the corresponding entity from EntitySet '{1}' must be available in the ObjectStateManager.
ECannot find the {0}FunctionMapping for {1} '{2}' in the mapping file.
A relationship from the '{0}' AssociationSet is in the '{1}' state. Given multiplicity constraints, a corresponding '{2}' must also in the '{1}' state.
A function mapping for EntitySet '{0}' requires that corresponding Associations in AssociationSet '{1}' are loaded. Load the AssociationSet before saving changes to this EntitySet.
XA function mapping specifies a result column '{0}' that the result set does not contain.
XModifying a column with the '{0}' pattern is not supported. Column: '{1}'. Table: '{2}'.
Modifications to tables where a primary key column has property '{0}' set to '{1}' are not supported. Use '{2}' pattern instead. Key column: '{3}'. Table: '{4}'.
XA null store-generated value was returned for a non-nullable member '{0}' of type '{1}'.
2Null value for non-nullable member. Member: '{0}'.
kReferential integrity constraint violation. A Dependent Role has multiple principals with different values.
Entities in '{0}' participate in the '{1}' relationship. '{2}' related '{3}' were found. Between {4} and {5} '{3}' are expected.
mEntities in '{0}' participate in the '{1}' relationship. {2} related '{3}' were found. {4} '{3}' is expected.
At most, '{0}' relationships may be in the '{1}' state for the '{2}' relationship from End '{3}' to an instance of End '{4}'. '{5}' instances were found.
~A store-generated value of type '{0}' could not be converted to a value of type '{1}' required for member '{2}' of type '{3}'.
\Unable to determine rows affected. The value of parameter '{0}' is not convertible to '{1}'.
Internal error. An unsupported type ({0}) was used as an argument to cast an expression in the update mapping view. The argument must be a scalar.
mInternal error. An unsupported expression kind ({0}) encountered in update mapping view by the ({1}) visitor.
Internal error. EntitySet ({0}) has unsupported type ({1}). Only EntitySets and AssociationSets can be processed in the update pipeline.
~Internal error. An unsupported join type is in update mapping view ({0}). Only binary inner or left outer joins are supported.
Internal error. Unsupported projection expression type ({0}). Only DBNewInstanceExpression projections are supported in update mapping views.
aThe entity client's MetadataWorkspace differs from the workspace referenced by the state manager.
Upgrading history table.
DOne or more validation errors were detected during model generation:
{0}: {1}: {2}
;A member of the same name is already defined in a BaseType.
%CollectionType has a null type usage.
/CollectionType objects cannot have a base type.
Item has an empty identity.
The facet does not have a name.
QThe facet object has null for the FacetType. Null is not valid for this property.
NThe item property has null for TypeUsage. Null is not valid for this property.
The member does not have a name.
OThe member has null for the DeclaringType. Null is not valid for this property.
QThe member has null for the MemberTypeUsage. Null is not valid for this property.
+The metadata property does not have a name.
The type '{0}' doesn't have any key members. A RelationshipType or EntityType must either have key members or a BaseType with key members.
EntityKeyProperty and IsNullable cannot both be true in the EdmScalarPropertyAttribute for property '{0}' on type '{1}'. Properties that are part of the key cannot be nullable.
The property '{0}' on type '{1}' is attributed with EdmComplexPropertyAttribute but returns the type '{2}', which is not a recognized ComplexType.
The mapping of CLR type to EDM type is ambiguous because multiple CLR types match the EDM type '{0}'. Previously found CLR type '{1}', newly found CLR type '{2}'.
The types in the assembly '{0}' cannot be loaded because the assembly contains the EdmSchemaAttribute, and the closure of types is being loaded by name. Loading by both name and attribute is not allowed.
KThe base type '{0}' of type '{1}' does not match the model base type '{2}'.
KThe type '{0}' was not loaded because the base type '{1}' is not available.
PNo corresponding object layer type could be found for the conceptual type '{0}'.
=The required property '{0}' does not exist on the type '{1}'.
Multiple types with the name '{0}' exist in the EdmItemCollection in different namespaces. Convention based mapping requires unique names without regard to namespace in the EdmItemCollection.
gThe underlying type of CLR enumeration type does not match the underlying type of EDM enumeration type.
mThe property '{0}' on the type '{1}' has a property type of '{2}' which cannot be mapped to a primitive type.
NThe relationship '{0}' was not loaded because the type '{1}' is not available.
Type '{0}' defined in the object layer is not compatible with type '{1}' defined in the conceptual model. An enumeration type cannot be mapped to a non-enumeration type.
The property '{0}' of type '{1}' in the assembly '{2}' cannot be used as a scalar property because it does not have both a getter and setter.
The EntityType or ComplexType '{0}' cannot be mapped by convention to the value type '{1}'. Value types are not allowed to be mapped to EntityTypes or ComplexTypes.
The property '{0}' on type '{1}' has the return type '{2}', which is not a recognized EntityType or enumeration of instances of EntityType.
The property '{0}' on type '{1}' is attributed with EdmScalarPropertyAttribute but returns the type '{2}', which is not a primitive type or a recognized enumeration type.
IThe RefType has null for EntityType. Null is not valid for this property.
(Reference types cannot have a base type.
The type does not have a name.
#The type does not have a namespace.
PThe type usage object has null for EdmType. Null is not valid for this property.
HThe type '{0}' is not a supported underlying type for enumeration types.
#{1} value ({0}) was not understood.
Unable to generate views because no mapping was found between conceptual model container '{0}' and store model container '{1}'. Ensure that the names match those defined in the EDMX or Code First model.
Unable to generate views because the model contained more than one container. Choose the conceptual and store model containers to use by passing their names to the appropriate overload of the GenerateViews method.
Given the cardinality of Association End Member {0}, it should be mapped to key columns of the table {1}. Either fix the mapping or change the multiplicity of this end.
QMust specify mapping for all key properties ({0}) of End {1} in Relationship {2}.
- {0} plays Role '{1}' in AssociationSet '{2}'
5 {0} does NOT play Role '{1}' in AssociationSet '{2}'
Data loss is possible in {0}.
?Data loss or key constraint violation is possible in table {0}.
PInsufficient mapping: It is possible to have {0} within {1} that are not mapped.
3No mapping specified for properties {0} in {1} {2}.
.Must specify mapping for all types in {0} {1}.
YCannot define new concurrency token member {0} in the derived class {1} of EntitySet {2}.
FConcurrency token(s) [{0}] in EntitySet {1} must not have a condition.
\Each of the following columns in table {0} is mapped to multiple conceptual side properties:
{0} is mapped to <{1}>
entities
Entity
GMust specify mapping for all key properties ({0}) of the EntitySet {1}.
{0} is in '{1}' EntitySet
{0} is NOT in '{1}' EntitySet
2Problem in mapping fragments starting at line {0}:
3Problem in mapping fragments starting at lines {0}:
EForeign key constraint '{0}' from table {1} ({2}) to table {3} ({4}):
Incorrect mapping of composite key columns. {0} Columns ({1}) in table {2} are mapped to properties ({3}) in {4} and columns ({5}) in table {6} are mapped to properties ({7}) in {8}. The order of the columns through the mappings is not preserved.
} {0} is mapped to AssociationSet {1} - for this mapping to be correct, the lower multiplicity bound of end {2} needs to be 1.
{0}: Insufficient mapping: Foreign key must be mapped to some AssociationSet or EntitySets participating in a foreign key association on the conceptual side.
BMissing table mapping: {0} no mapping specified for the table {1}.
The foreign key '{0}' is not being enforced in the model. An Association or inheritance relationship needs to be created to enforce this constraint.
{0} The columns of table {1} are mapped to AssociationSet {2}'s End {3} but the key columns of table {4} are not mapped to the keys of the EntitySet {5} corresponding to this End.
~ {0} is mapped to AssociationSet {1} - for this mapping to be correct, the upper multiplicity bound of end {2} needs to be 1.
The current model no longer matches the model used to pre-generate the mapping views, as indicated by the {0}.MappingHashValue property. Pre-generated mapping views must be either regenerated using the current model or removed if mapping views generated at runtime should be used instead. See http://go.microsoft.com/fwlink/?LinkId=318050 for more information on Entity Framework mapping views.
DConditions specified on member {0} in this fragment are not allowed.
uAt least one of the key properties of AssociationSet {0} must be mapped to all the key properties ({1}) of table {2}.
nAll the key properties ({0}) of the EntitySet {1} must be mapped to all the key properties ({2}) of table {3}.
Potential runtime violation of table {0}'s keys ({2}): Columns ({1}) are mapped to EntitySet {3}'s properties ({4}) on the conceptual side but they do not form the EntitySet's key properties ({5}).
FNo mapping specified for the following EntitySet/AssociationSet - {0}.
bNo mapping specified for instances of the EntitySet and AssociationSet in the EntityContainer {0}.
3No mapping specified for the following types - {0}.
Values other than [{0}]
TColumn {1} in table {0} must be mapped: It has no default value and is not nullable.
eColumn {0} has no default value and is not nullable. A column value is required to store entity data.
[Column(s) [{0}] are being mapped in both fragments to different conceptual side properties.
NOT_NULL
:Property {0} with 'IsNull=false' condition must be mapped.
?Must specify mapping for all key properties ({0}) of table {1}.
\Insufficient or contradictory mapping. Cannot generate query views for entities in {0} when:
2An Entity with Key ({0}) will not round-trip when:
Condition member '{0}' with a condition other than 'IsNull=False' is mapped. Either remove the condition on {0} or remove it from the mapping.
6Condition members {0} have duplicate condition values.
Column {0} is used in a Not Null condition but it is mapped to a property {1} which is nullable. Consider making this property non-nullable.
An entity is mapped to different rows within the same table. Ensure these two mapping fragments do not map two groups of entities with identical keys to two distinct groups of rows.
An entity is mapped to different rows within the same table. Ensure these two mapping fragments do not map two groups of entities with overlapping keys to two distinct groups of rows.
Two entities with identical keys are mapped to different rows within the same table. Ensure these two mapping fragments do not map two groups of entities with overlapping keys to two distinct groups of rows.
Two entities with possibly identical keys are mapped to different rows within the same table. Ensure these two mapping fragments do not map two unrelated EntitySets to two distinct groups of rows.
Two entities with different keys are mapped to the same row. Ensure these two mapping fragments do not map two groups of entities with different keys to the same group of rows.
Two entities with different keys are mapped to the same row. Ensure these two mapping fragments do not map two groups of entities with overlapping keys to the same group of rows.
Two entities with different keys are mapped to the same row. Ensure these two mapping fragments do not map two EntitySets with overlapping keys to the same group of rows.
Two entities with possibly different keys are mapped to the same row. Ensure these two mapping fragments do not map two unrelated EntitySets to the same group of rows.
Two entities with possibly different keys are mapped to the same row. Ensure these two mapping fragments map both ends of the AssociationSet to the corresponding columns.
EntityTypes {0} are being mapped to the same rows in table {1}. Mapping conditions can be used to distinguish the rows that these types are mapped to.
Two entities with different keys are mapped to the same row. Ensure these two mapping fragments do not map two groups of entities with different keys to two overlapping groups of rows.
Two rows with different primary keys are mapped to the same entity. Ensure these two mapping fragments do not map two groups of entities with identical keys to two overlapping groups of rows.
Two rows with different primary keys are mapped to two entities that carry identical keys through a referential integrity constraint. Ensure these two mapping fragments do not map two EntitySets with identical keys to two overlapping groups of rows.
An entity from one EntitySet is mapped to a row that is also mapped to an entity from another EntitySet with possibly different key. Ensure these two mapping fragments do not map two unrelated EntitySets to two overlapping groups of rows.
ZEntitySets '{1}' and '{2}' are both mapped to table '{0}'. Their primary keys may collide.
When there is a mapping fragment between EntitySet '{0}' and Table '{1}' with MakeColumnsDistinct attribute marked to 'true', there can be no additional mapping fragments between '{0}' and '{1}'.
Mapping fragments cannot be joined. Ensure every mapping fragment maps a key on which it should be joined with one of the other mapping fragments.
MNon-nullable column {1} in table {0} is mapped to a nullable entity property.
Could not validate mapping for EntitySet {0}. Check that the mapping constraints are possible in the presence of store side constraints. Having an 'IsNull=True' condition in the mapping for a non-nullable column is an example of an impossible constraint.
Ensure that mapping fragments for EntitySet {0} do not map entities with the same primary key to different rows of the same table.
DbInExpression handling is not implemented. The functionality involving DbInExpression, new in Entity Framework 6, is turned off by default for compatibility with existing provider implementations. It can be enabled by overriding DbProviderManifest.SupportsInExpression and returning true, in which case any command tree expression visitor implemented by the provider must handle the new expression type.
8The wildcard assembly enumerator function returned null.
<?xml version="1.0" encoding="utf-8"?>
<xs:schema id="AnnotationSchema" targetNamespace="http://schemas.microsoft.com/ado/2009/02/edm/annotation" elementFormDefault="unqualified" xmlns="http://schemas.microsoft.com/ado/2009/02/edm/annotation" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:attribute name="StoreGeneratedPattern" type="TStoreGeneratedPattern" />
<xs:simpleType name="TStoreGeneratedPattern">
<xs:restriction base="xs:token">
<xs:enumeration value="None" />
<xs:enumeration value="Identity" />
<xs:enumeration value="Computed" />
</xs:restriction>
</xs:simpleType>
<xs:attribute name="LazyLoadingEnabled" type="xs:boolean" />
<!-- Allow future support of a strongly typed hierarchy of types for spatial values -->
<xs:attribute name="UseStrongSpatialTypes" type="xs:boolean" default="true" />
</xs:schema>
<?xml version="1.0" encoding="utf-8"?>
<xs:schema id="CodeGenerationSchema" targetNamespace="http://schemas.microsoft.com/ado/2006/04/codegeneration" elementFormDefault="unqualified" xmlns="http://schemas.microsoft.com/ado/2006/04/codegeneration" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:attribute name="SetterAccess" type="TAccess" />
<xs:attribute name="GetterAccess" type="TAccess" />
<xs:attribute name="TypeAccess" type="TPublicOrInternalAccess" />
<xs:attribute name="MethodAccess" type="TAccess" />
<xs:attribute name="ExternalTypeName" type="xs:string" />
<xs:simpleType name="TAccess">
<xs:restriction base="xs:string">
<xs:enumeration value="Public" />
<xs:enumeration value="Internal" />
<xs:enumeration value="Protected" />
<xs:enumeration value="Private" />
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="TPublicOrInternalAccess">
<xs:restriction base="TAccess">
<xs:enumeration value="Public" />
<xs:enumeration value="Internal" />
</xs:restriction>
</xs:simpleType>
</xs:schema>xW
<?xml version="1.0" encoding="utf-8"?>
<xs:schema elementFormDefault="qualified" attributeFormDefault="unqualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cg="http://schemas.microsoft.com/ado/2006/04/codegeneration" xmlns:edm="http://schemas.microsoft.com/ado/2006/04/edm" targetNamespace="http://schemas.microsoft.com/ado/2006/04/edm">
<xs:annotation>
<xs:documentation xml:lang="en">
Common Data Model Schema Definition Language.
</xs:documentation>
</xs:annotation>
<xs:import namespace="http://schemas.microsoft.com/ado/2006/04/codegeneration" schemaLocation="System.Data.Resources.CodeGenerationSchema.xsd" />
<xs:element name="Schema" type="edm:TSchema" />
<xs:complexType name="TSchema">
<xs:sequence>
<xs:group ref="edm:GSchemaBodyElements" minOccurs="0" maxOccurs="unbounded" />
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="Namespace" type="edm:TNamespaceName" use="required" />
<xs:attribute name="Alias" type="edm:TSimpleIdentifier" use="optional" />
<xs:anyAttribute namespace="##other" processContents="lax" />
</xs:complexType>
<xs:group name="GSchemaBodyElements">
<xs:choice>
<xs:element name="Using" type="edm:TUsing" minOccurs="0" maxOccurs="unbounded" />
<xs:element name="Association" type="edm:TAssociation" minOccurs="0" maxOccurs="unbounded" />
<xs:element name="ComplexType" type="edm:TComplexType" minOccurs="0" maxOccurs="unbounded" />
<xs:element name="EntityType" type="edm:TEntityType" minOccurs="0" maxOccurs="unbounded" />
<xs:element ref="edm:EntityContainer" minOccurs="1" maxOccurs="1" />
</xs:choice>
</xs:group>
<!-- EDM SimpleType instances for use by EDM Instance documents-->
<xs:simpleType name="EDMSimpleType">
<xs:restriction base="xs:string">
<xs:enumeration value="Binary" />
<xs:enumeration value="Boolean" />
<xs:enumeration value="Byte" />
<xs:enumeration value="DateTime" />
<xs:enumeration value="DateTimeOffset" />
<xs:enumeration value="Time" />
<xs:enumeration value="Decimal" />
<xs:enumeration value="Double" />
<xs:enumeration value="Single" />
<xs:enumeration value="Guid" />
<xs:enumeration value="Int16" />
<xs:enumeration value="Int32" />
<xs:enumeration value="Int64" />
<xs:enumeration value="String" />
<xs:enumeration value="SByte" />
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="TMax">
<xs:restriction base="xs:string">
<xs:enumeration value="Max" />
</xs:restriction>
</xs:simpleType>
<!-- Facets for Primitive types -->
<xs:simpleType name="TMaxLengthFacet">
<xs:union memberTypes="edm:TMax xs:nonNegativeInteger " />
</xs:simpleType>
<xs:simpleType name="TIsFixedLengthFacet">
<xs:restriction base="xs:boolean" />
</xs:simpleType>
<xs:simpleType name="TPrecisionFacet">
<xs:restriction base="xs:nonNegativeInteger" />
</xs:simpleType>
<xs:simpleType name="TScaleFacet">
<xs:restriction base="xs:nonNegativeInteger" />
</xs:simpleType>
<xs:simpleType name="TIsUnicodeFacet">
<xs:restriction base="xs:boolean" />
</xs:simpleType>
<xs:simpleType name="TCollationFacet">
<xs:restriction base="xs:string" />
</xs:simpleType>
<!--
types at all levels
-->
<xs:complexType name="TDocumentation">
<xs:annotation>
<xs:documentation>
The Documentation element is used to provide documentation of comments on the contents of the XML file.
It is valid
under Schema, Type, Index and Relationship elements.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Summary" type="edm:TText" minOccurs="0" maxOccurs="1" />
<xs:element name="LongDescription" type="edm:TText" minOccurs="0" maxOccurs="1" />
</xs:sequence>
<xs:anyAttribute processContents="lax" namespace="##other" />
</xs:complexType>
<xs:complexType name="TText" mixed="true">
<xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:anyAttribute processContents="lax" namespace="##other" />
</xs:complexType>
<xs:complexType name="TXmlOrText" mixed="true">
<xs:annotation>
<xs:documentation>
This type allows pretty much any content
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:any namespace="##any" processContents="skip" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:anyAttribute processContents="skip" namespace="##any" />
</xs:complexType>
<!--
types of the top level elements
-->
<xs:complexType name="TUsing">
<xs:sequence>
<xs:group ref="edm:GEmptyElementExtensibility" minOccurs="0" maxOccurs="1" />
</xs:sequence>
<xs:attribute name="Namespace" type="edm:TNamespaceName" use="required" />
<xs:attribute name="Alias" type="edm:TSimpleIdentifier" use="required" />
<xs:anyAttribute namespace="##other" processContents="lax" />
</xs:complexType>
<xs:complexType name="TAssociation">
<xs:sequence>
<xs:element name="Documentation" type="edm:TDocumentation" minOccurs="0" maxOccurs="1" />
<xs:element name="End" type="edm:TAssociationEnd" minOccurs="2" maxOccurs="2" />
<xs:element name="ReferentialConstraint" type="edm:TConstraint" minOccurs="0" maxOccurs="1" />
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="Name" type="edm:TSimpleIdentifier" use="required" />
<xs:anyAttribute namespace="##other" processContents="lax" />
</xs:complexType>
<xs:complexType name="TComplexType">
<xs:sequence>
<xs:element name="Documentation" type="edm:TDocumentation" minOccurs="0" maxOccurs="1" />
<xs:element name="Property" type="edm:TComplexTypeProperty" minOccurs="0" maxOccurs="unbounded" />