2

Closed

On Migration or Run I get: IsSystem' attribute is not declared.

description

<File Unknown>(0,0) : error 2025: XML Schema validation failed for mapping schema. Schema Error Information : The 'http://schemas.microsoft.com/ado/2012/10/edm/migrations:IsSystem' attribute is not declared..

How do I fix this?

Thanks!
Closed May 16, 2013 at 11:49 PM by RoMiller
This is a result of some changes we have made to how migrations stores data. Because it's between nightly builds we don't handle a graceful upgrade.
We will put together some guidance when we release the next Alpha/Beta because this would affect migrations created with Alpha 3.
In the meantime you need to remove migrations created with previous builds and re-create them.

comments

moozzyk wrote May 9, 2013 at 7:53 PM

Geminiman wrote May 9, 2013 at 8:18 PM

Except this is .NET 4.5 under windows, just grabbed the nightlies from 5/2/13 to 5/9/13 and it blew up with this error.

Was there config file changes?

Ridermansb wrote May 18, 2013 at 1:03 AM

@RonMiler I removed the database and performed 'Update-Database'
Still the error occurs.

have to remove the table Migrations or classes??

Geminiman wrote May 18, 2013 at 3:51 AM

Delete the table, delete the migrations folder from the project, then reinit migrations with -force and works.

IDisposable wrote Jun 7, 2013 at 11:05 PM

How does this apply to unit-testing the EF framework itself? I can't run tests before submitting pulls.

IDisposable wrote Jun 7, 2013 at 11:38 PM

How do we get EF6 source unit tests to run in the face of this error before submitting pull requests?

moozzyk wrote Jun 8, 2013 at 1:48 AM

I believe you need to drop all databases created by the tests. There is this script: entityframework\test\EntityFramework\DropAllDatabases.sql but be careful - it drops all the databases.

luisrudge wrote Oct 9, 2013 at 2:35 AM

So, basically it's some breaking change and anyone using EF6 on production is hopeless? How can i fix this WITHOUT recreating everything?

lukew wrote Oct 9, 2013 at 5:08 PM

@luisrudge this is a breaking change that only affects the migration history table and the databases generated by the Entity Framework test suite. For your production code you only need to recreate your migrations and your migrations history table as @Geminiman said above.