Known Issues

Below is a list of known issues with the Entity Framework code base and infrastructure. This list will be kept up to date as new issues arise and existing issues are fixed.

  • Test failures can arise from test databases with stale metadata. The solution is to drop the test databases. (This can be done by running DropAllDatabases.sql under test\EntityFramework.)
  • Some tests may fail if your git repository is nested under your user folder, because the SQL service is unable to create database files in that location. One workaround is to give the service SID "NT SERVICE\MSSQL$SQLEXPRESS" full access to the test's "bin" folder and subfolders. You can also try moving the repository elsewhere.
  • Loading assemblies may fail with "Strong name signature could not be verified." If this is the case, download and run the latest version of SkipStrongNames. New assemblies get added to this utility over time.

If you are experiencing an issue please start a discussion.

Last edited Feb 1, 2013 at 9:25 PM by BriceLambson, version 13

Comments

BriceLambson Jan 29 at 8:27 PM 
@BrandonDahler That issue should be fixed in Git for Windows versions 1.8.4 and newer. https://github.com/msysgit/git/issues/57

BrandonDahler Jan 29 at 1:03 AM 
Another cause of failing tests is your git client not applying CR+LF line endings to your files (can happen specifically if you use cygwin).

Fix by running "git config --global core.autocrlf true"

jjwilliams Jul 12, 2013 at 2:45 AM 
Another tip: If when running build /t:RestorePackages you get a bunch of errors, go to Tools > Options > Package Manager > General > Clear Package Cache.