VS2010 corrupts SQL Server 2012 DB --- Workarounds, or is this a feature?

I've found a bug where EF 4.0 in VS2010 corrupts a SServer 2012 Express DB by not using the .ldf file created for the DB in SQL Server, but instead creates a unique file.  After that point SQL Server whines about the primary file not matching the logfile and the DB is set in "Recovery Pending" state, forcing a restore of the DB from backup.
I'm trying to work through Julie Lerman's book Programming Entity Framework 2nd Edition.  I've raised the issue on her forum for her book at O'Reily, but she hasn't logged onto the site since April, so I'm not too confident she'll be responding any time soon.
Here is the directory after creating the DB, but before trying anything from VS:
E:\Program Files (x8 ...