Database First

Hi

Hm,  we have several test cases that use Database first models.

The EFContextProvider<T> generic argument "T" can be either a DbContext or an ObjectContext. 

So with EF "Database first",  you should have an EFContext class that looks something like.

    public partial class NorthwindIBContext : ObjectContext {
    ...

    }

The Breeze EFContextProvider can then be used like this


    public class NorthwindIBContextProvider: EFContextProvider<NorthwindIBContext>  {
        public NorthwindContextProvider() : base() { }
   
        // any public override here like BeforeSaveEntity or BeforeSaveEntities...
     
    }

And then your api controller might look something like this

    public class NorthwindIBModelController : ApiController {

        private  NorthwindContextProvider _contextProvider = new NorthwindContextProvider();

        [AcceptVerbs("GET")]
        public String Metadata() {
          return _contextProvider.Metadata();
        }
        ...
    }

Also, note that the example above uses an [AcceptVerbs("Get")] attribute instead of an [HttpGet] attribute.  I'm not really clear on the distinction between these two, but just to be safe ...

If this doesn't work, let me know and I'll try to post an entire working example with an DataBase first model.

Ok, I think I understand what is happening. 

Our internal tests are all built against "Database first" models built several years ago with an "ObjectContext".  With the advent of EF 4.1, EF "Database first" now defaults to creating a context that derives from DbContext and uses POCO entity classes.  We need to add tests for this, because evidently the DbContext that EF4.1 creates for "Database first" models is subtly different from that created for CodeFirst models, where we have a number of tests.

We will try to have this cleared up and a patch put together by this evening.  But until then, you can still use an "old" ObjectContext by following the instructions in this link.

msdn.microsoft.com/en-us/data/jj556581.aspx

There is a new Breeze version 0.71.3 available now that should fix this issue.

With this version, you should be able to create an EFContextProvider with a "Database First" DbContext .