I meant to mention this in my last blog post (An excerpt from my book about eSqlBlast) which is that with the new Entity Framework bits, the schema files that are generated when you build your EDM project are embedded into the assembly by default. Yet eSqlBlast depends on files that are accesible via the file directory.
What I’ve been doing is temporarily changing the MetaData Artifact Processing property of the model to Copy to Output Directory, building the project, then copying the newly created files (csdl, msl and ssdl) to a separate folder. Then I can point eSqlBlast to those files and set the model back to Embed in Output Assembly so that the other projects depending on the model can access the schema files.
Sign up for my newsletter so you don't miss my conference & Pluralsight course announcements!