DevForce Community Forum : Community Forum

Community Forum : Breeze moved to Stack Overflow

Tue, 20 Nov 2012 10:55:23 -700

Author: johnl
Subject: Breeze moved to Stack Overflow
Posted: 20-Nov-2012 at 10:55am

We've moved free communitysupport for Breeze to Stack Overflow. Bymoving to Stack Overflow, one of the largest communities of developers on theinternet will be able to benefit from your questions—and you from theiranswers.

You can still use all the greatcontent in this forum. If you don’t find your answer here then head on over to Stack Overflow to post your question using the Breezetag.

Edited by DF4IdeaBlade - 21-Nov-2012 at 11:07am

Community Forum : EFContextProvider dynamic connectionstring

Mon, 19 Nov 2012 07:08:10 -700

Author: Marcel
Subject: EFContextProvider dynamic connectionstring
Posted: 19-Nov-2012 at 7:08am

I downloaded the source and added a constructor to the EFContextProvider which accepts an instance of T to be able to use an existing ObjectContext/DbContext which works like a charm.

Community Forum : EFContextProvider dynamic connectionstring

Mon, 19 Nov 2012 05:20:38 -700

Author: Marcel
Subject: EFContextProvider dynamic connectionstring
Posted: 19-Nov-2012 at 5:20am

Hi,

At the moment i have an application (web/silverlight) where the connectionstring for my ObjectContext is dynamic.

It is based on how a user logs in because each of my customers have their own database. ie.. username@domain.

I'm trying to find a way to use the EFContextProvider which would be by either passing the ObjectContext through the constructor, or by overriding the GetConnectionString, which sadly both aren't supported.

Is there a way to accomplish this, or can i download the source for the EFContextProvider somewhere so i can implement it myself ?

Thanks in advance.

Community Forum : Security/Authentication

Sat, 17 Nov 2012 08:59:25 -700

Author: SirSmackalot
Subject: Security/Authentication
Posted: 17-Nov-2012 at 8:59am

Hi,

i have not tried it, will do so next week. Here ist something which might be useful:

http://stackoverflow.com/questions/11476883/web-api-and-validateantiforgerytoken
and
(followup of the previous link)
http://stackoverflow.com/questions/11725988/problems-implementing-validatingantiforgerytoken-attribute-for-web-api-with-mvc/11726560#11726560

This way the .NET AntiforgeryToken could be used. Maybe someone finds that useful.

With the plugable header this is possible :)

Greets

Community Forum : Database First

Sat, 17 Nov 2012 08:03:40 -700

Author: brian.shirley
Subject: Database First
Posted: 17-Nov-2012 at 8:03am

I just pulled down the latest from NuGet and it is working perfectly. Thanks again for the quick turnaround. Stellar.

Community Forum : Database First

Sat, 17 Nov 2012 03:09:58 -700

Author: jtraband
Subject: Database First
Posted: 17-Nov-2012 at 3:09am

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 .

Community Forum : Cross domain post

Fri, 16 Nov 2012 11:57:16 -700

Author: jtraband
Subject: Cross domain post
Posted: 16-Nov-2012 at 11:57am

Anything you have to share in this area would be greatly appreciated, as well as any recommendations to changes to "Breeze" to make this whole process easier.

Community Forum : Cross domain post

Fri, 16 Nov 2012 11:52:09 -700

Author: Nucleotic
Subject: Cross domain post
Posted: 16-Nov-2012 at 11:52am

Hi Marcel,

We also had various cross-domain posting issues where we separated our WebAPI service layer into a separate assembly and I used a mix of a C# delegating handler (to intercept the HTTP request/response pipeline - think HTTPModule-like) to implement the JSONP standard along with a JSONMediaTypeformatter to interpret the HTTP-headers format in our case.

Then we just extended the ajax request on the client side to override certain header properties before popping request off to the server via the EntityManager. This is did via a bug-fix in the Breeze.js scripts in the 3 SaveChanges functions (to enable OPTIONS / POST on JSONP).

I have this solution working like a charm now, with a complex entity set. I am happy to share and solution with you and the bug fixes with the Breeze team.

Therefore this requires minimal custom ajax calls and forms part of the core Breeze API (in our case) to minimize the need for further custom jQuery / XHttpRequest / html iframe hacks. BTW, I tried various CORS options via config in ASP.NET, but browser support seems lacking on the client side. JSONP is fully supported.

Regards,

Community Forum : Database First

Fri, 16 Nov 2012 11:30:54 -700

Author: brian.shirley
Subject: Database First
Posted: 16-Nov-2012 at 11:30am

I created a simple database first model that uses ObjectContext as a test and it worked as stated, so progress!!

Thank you very much for the quick responses on this and all of the hard work on Breeze.

Originally posted by jtraband

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

Community Forum : Database First

Fri, 16 Nov 2012 11:22:13 -700

Author: jtraband
Subject: Database First
Posted: 16-Nov-2012 at 11:22am

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

Community Forum : Database First

Fri, 16 Nov 2012 11:11:08 -700

Author: brian.shirley
Subject: Database First
Posted: 16-Nov-2012 at 11:11am

I switched to the [AcceptVerbs("GET")] annotation for good measure and still no luck.

I'm wondering if the conflict is due to the fact that my Database First EDMX model is generating a class derived from DbContext rather than ObjectContext due to the DbContext generator template I linked to above. I went this route in order to get true POCOs and DbSet with DbContext API.

I will try to do a traditional database first example that derives from ObjectContext to see if I still get issues.

Have you tried any examples this way?

For reference, Error:

Creating a DbModelBuilder or writing the EDMX from a DbContext created using Database First or Model First is not supported. EDMX can only be obtained from a Code First DbContext created without using an existing DbCompiledModel.

Community Forum : Database First

Fri, 16 Nov 2012 10:49:26 -700

Author: jtraband
Subject: Database First
Posted: 16-Nov-2012 at 10:49am

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

The EFContextProvider 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.

Community Forum : Database First

Fri, 16 Nov 2012 08:42:09 -700

Author: brian.shirley
Subject: Database First
Posted: 16-Nov-2012 at 8:42am

I am also encountering this exact same problem.

I created an EDMX file with one table from an existing database. I then used the DbContext generator template so that the model used DbContext rather than ObjectContext and generated a POCO.

When calling directly via a WebApi method such as below, I receive JSON data as expected.

BrokerCommContext DbContext = new BrokerCommContext();

return DbContext.CommissionDesignations.AsEnumerable();

However, when invoking the method from the EFContextProvider I receive the same error as identified by Mike in the original post.

readonly EFContextProvider _contextProvider =

new EFContextProvider();

[HttpGet]

public string Metadata()

{

return _contextProvider.Metadata();

}

I am really looking forward to getting Breeze out there with this project. Any help is greatly appreciated!

Code Generated from EDMX

public partial class BrokerCommContext : DbContext

{

public BrokerCommContext()

: base("name=BrokerCommContext")

{

this.Configuration.LazyLoadingEnabled = false;

}

protected override void OnModelCreating(DbModelBuilder modelBuilder)

{

throw new UnintentionalCodeFirstException();

}

public DbSet CommissionDesignations { get; set; }

Originally posted by mike963

Hi

I have tried Breeze with an existing EF implementation that was developed DB first.

I get an error _contextProvider.Metadata();

Originally I had the EDMX file in a separate Data Access Layer but have also tried it locally but still get same error

Any advice ?

Stack Trace

at System.Data.Entity.Infrastructure.EdmxWriter.WriteEdmx(DbContext context, XmlWriter writer)

at Breeze.WebApi.EFContextProvider`1.GetCsdlFromDbContext(DbContext dbContext)

at Breeze.WebApi.EFContextProvider`1.GetJsonMetadataFromDbContext(DbContext dbContext)

at Breeze.WebApi.EFContextProvider`1.Metadata()

at UsingBreeze.Controllers.BreezeSampleController.Metadata() in d:\ModuleChooser\UsingBreeze\Controllers\BreezeSampleController.cs:line 19

at lambda_method(Closure , Object , Object[] )

at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass13.b__c(Object instance, Object[] methodParameters)

at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.Execute(Object instance, Object[] arguments)

at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.<>c__DisplayClass5.b__4()

at System.Threading.Tasks.TaskHelpers.RunSynchronously[TResult](Func`1 func, CancellationToken cancellationToken)

Edited by brian.shirley - 16-Nov-2012 at 9:09am

Community Forum : Database First

Fri, 16 Nov 2012 07:58:57 -700

Author: mike963
Subject: Database First
Posted: 16-Nov-2012 at 7:58am

Hi

I have tried Breeze with an existing EF implementation that was developed DB first.

I get an error _contextProvider.Metadata();

Originally I had the EDMX file in a separate Data Access Layer but have also tried it locally but still get same error

Any advice ?

Stack Trace

at System.Data.Entity.Infrastructure.EdmxWriter.WriteEdmx(DbContext context, XmlWriter writer)

at Breeze.WebApi.EFContextProvider`1.GetCsdlFromDbContext(DbContext dbContext)

at Breeze.WebApi.EFContextProvider`1.GetJsonMetadataFromDbContext(DbContext dbContext)

at Breeze.WebApi.EFContextProvider`1.Metadata()

at UsingBreeze.Controllers.BreezeSampleController.Metadata() in d:\ModuleChooser\UsingBreeze\Controllers\BreezeSampleController.cs:line 19

at lambda_method(Closure , Object , Object[] )

at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass13.b__c(Object instance, Object[] methodParameters)

at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.Execute(Object instance, Object[] arguments)

at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.<>c__DisplayClass5.b__4()

at System.Threading.Tasks.TaskHelpers.RunSynchronously[TResult](Func`1 func, CancellationToken cancellationToken)

Community Forum : Setting headers with request

Thu, 15 Nov 2012 20:30:20 -700

Author: sujesharukil
Subject: Setting headers with request
Posted: 15-Nov-2012 at 8:30pm

This works. Thank you. Keep em updates coming!

Community Forum : Cross domain post

Thu, 15 Nov 2012 01:18:11 -700

Author: Marcel
Subject: Cross domain post
Posted: 15-Nov-2012 at 1:18am

First of all thank you very much for the clear answer.

In the meantime i've done a lot of testing to get this working with jQuery, and eventually managed to get it working through jsonp.
Although jsonp can't be used to do a POST to a controller, a GET with the json as a parameter worked like a charm.

CORS can be enabled even through the web.config by adding the appropriate custom headers.

The only problem left is browser incompatibility to read request headers through jQuery.
So that makes it nearly impossible to maintain session state on the server, which i needed for a Captcha check.

Eventually i solved the problem by letting my customers embed our web-form through an iframe so i didn't have to worry about CORS.

The project i'm working on is at the moment still an MVC 3 project, but i will probably upgrade it to MVC 4 and use breeze.js (since the asp.net team abbandoned upshot.js and are a bit slow with alternatives).

Thanks again.

Community Forum : Breeze + Amplify

Wed, 14 Nov 2012 19:33:14 -700

Author: jtraband
Subject: Breeze + Amplify
Posted: 14-Nov-2012 at 7:33pm

Please take a look at the new pluggable ajax support in Breeze 0.70.1. Please let us know if this does or doesn't work to correct the issue.

Community Forum : Security/Authentication

Wed, 14 Nov 2012 19:29:34 -700

Author: jtraband
Subject: Security/Authentication
Posted: 14-Nov-2012 at 7:29pm

It been awhile since you posted this, but take a look at our new pluggable ajax support in v 0.70.1. Please let us know if this does or doesn't handle your issues.

Community Forum : Setting headers with request

Tue, 13 Nov 2012 10:34:04 -700

Author: jtraband
Subject: Setting headers with request
Posted: 13-Nov-2012 at 10:34am

As of Breeze 0.70.1 we now support for the ability to completely customize or replace any ajax communication between the breeze client and the web service on the server.

The Breeze documentation on our Ajax support is still in progress, but hopefully the following will get you started.

To control the headers on every ajax request that breeze makes you can execute the following code when your app first starts up.

   var ajaxImpl = breeze.core.config.getAdapterInstance("ajax");
   ajaxImpl.defaultSettings = {
     headers: {
               // any CORS or other headers that you want to specify.
               "X-Test-Header": "foo2"
           },
};

Alternatively, you can intercept the individual ajax calls and add your headers selectively based on the request.

   var ajaxImpl = breeze.core.config.getAdapterInstance("ajax");
   ajaxImpl.defaultSettings = {
       beforeSend: function(jqXHR, settings) {
                  // examine the jqXHR or settings and customize the headers accordingly.
                  jqXHR.setRequestHeader("X-Test-Before-Send-Header", "foo2");
           }
     };

Community Forum : Cross domain post

Tue, 13 Nov 2012 10:32:29 -700

Author: jtraband
Subject: Cross domain post
Posted: 13-Nov-2012 at 10:32am

We haven't spent much time looking at Cross-Origin Resource Sharing (CORS) with Breeze yet but with the recent release of Breeze 0.70.1 we now support for the ability to completely customize or replace any ajax communication between the breeze client and the web service on the server. This obviously includes the ability to specify CORS headers in any Ajax request. So assuming that you are going thru the ASP.NET Web API provider and that your service is configured to support CORS, breeze should be able to talk to it.

Unfortunately, we haven't seen much from Microsoft regarding how to configure ASP.NET Web Api to support CORS, but we assume that it is possible.

Again, we have not yet gotten around to testing this, so please let us know of your progress in this direction.

The Breeze documentation on our Ajax support is still in progress, but hopefully the following will get you started.

To control the headers on every ajax request that breeze makes you can execute the following code when your app first starts up.

   var ajaxImpl = breeze.core.config.getAdapterInstance("ajax");
   ajaxImpl.defaultSettings = {
     headers: {
               // any CORS or other headers that you want to specify.
               "X-Test-Header": "foo2"
           },
};

Alternatively, you can intercept the individual ajax calls and add your headers selectively based on the request.

   var ajaxImpl = breeze.core.config.getAdapterInstance("ajax");
   ajaxImpl.defaultSettings = {
       beforeSend: function(jqXHR, settings) {
                  // examine the jqXHR or settings and customize the headers accordingly.
                  jqXHR.setRequestHeader("X-Test-Before-Send-Header", "foo2");
           }
     };

Community Forum : Validation

Tue, 13 Nov 2012 09:57:15 -700

Author: jtraband
Subject: Validation
Posted: 13-Nov-2012 at 9:57am

As you've probably noticed, Breeze already performs validations based on metadata. Basic "validation" rules such as whether a property is required, it's datatype and it's length if a string are automatically generated on the server and sent down to the client. These validation rules can also be extended by directly modifying the "validation" metadata on the client.

More information on this topic is available both within the API documentation: http://www.breezejs.com/sites/all/apidocs/classes/Validator.html as well as within the "DocCode" sample directory in the Breeze Samples download.

We are also planning on providing examples of how to "connect" breeze validation to various third party libraries, such as jQuery and Knockout. Unfortunately, these examples are not currently a high priority because of work on other highly requested features. You might want to vote for work on these examples on our Breeze User Voice https://breezejs.uservoice.com/forums/173093-breeze-feature-suggestions. We take that venue seriously in making decisions about what to do next.

Community Forum : oData samples without Web API or EF

Tue, 13 Nov 2012 09:37:10 -700

Author: jtraband
Subject: oData samples without Web API or EF
Posted: 13-Nov-2012 at 9:37am

Absolutely, to switch to using an OData service simply initialize breeze with the correct adapter. For OData this would look like

breeze.core.config.initializeAdapterInstance("dataService", "OData");

Make sure you make this call before creating your first EntityManager and remember to use an OData uri as the service name.

This provides full OData query support. OData saves have not yet been implemented although they are on the near term roadmap. If you really need OData save functionality, you might want to vote for it on our Breeze User Voice https://breezejs.uservoice.com/forums/173093-breeze-feature-suggestions. We take that venue seriously in making decisions about what to do next.

Note: we changed the "plugin/adapter" model with v 0.70 of Breeze. Older versions use a now obsolete method

breeze.core.config.setProperties( {
remoteAccessImplementation: breeze.entityModel.remoteAccess_odata
});

Community Forum : oData samples without Web API or EF

Tue, 13 Nov 2012 06:23:54 -700

Author: jpirok
Subject: oData samples without Web API or EF
Posted: 13-Nov-2012 at 6:23am

I haven't seen any examples of using this framework that don't use Web API.

How would I use breeze against an odata service using only the server's metadata to define the model?
Will the context still be able to handle crud operations to a non web api service?

I have seen

    // service name is route to the Web API controller
    var serviceName = 'api/CarBones';

    /*** dataservice proper ***/

    // manager (aka context) is the service gateway and cache holder
    var manager = new entityModel.EntityManager(serviceName);

Can I do something like replacing the serviceName with an oData uri and then continue using breeze as usual?

    var serviceName = "http://localhost:1234/Northwind.svc"

Thanks for your help!

Community Forum : Cross domain post

Sat, 10 Nov 2012 01:37:26 -700

Author: Marcel
Subject: Cross domain post
Posted: 10-Nov-2012 at 1:37am

Hello,

quick explanation:

I have a small mvc project with a controller where (atm) i post json data to, which is hosted on my own domain.

Now i wanted to create the possibility for my customers to post data from their website (other domain) to my controller,

but after trying and trying to get this done with jquery (ajax) i came to the conclusion it's such a pain due to
cross-domain posting. IE 8 for example is the biggest problem here.

My customers would link in a javascript file (and neccesary dependencies) from my website, initialize my javascript objects and implement a form by given specs.

Now i have been playing with breeze a lot and ofcourse i could check it myself eventually, but a quick question here
would save me the time.

So the question:

Does breezejs support cross-domain crud operations (or even only get and post) ?

Thanks in advance.

Community Forum : Validation

Fri, 09 Nov 2012 06:56:56 -700

Author: johnvarney
Subject: Validation
Posted: 09-Nov-2012 at 6:56am

I've recently added Breeze to a project using Knockout and ASP.NET MVC4. I really like Breeze and it saves a lot of coding.

I have used Knockout validation and like how it validates a property field text box on data entry and the way the error message is displayed.

I would like to use a combination where the validation requirements are defined in the back-end with C# attributes on the object properties, the validation requirements are received in the metadata and then Knockout validation can be used.

I think I can work around it by defining the properties in the front end and applying Knockout validation eg

classProperty.extend({ required: true })
.extend({ minLength: 3 });

Is there a way to use Knockout validation without having to apply the validation requirements in the front-end? If not, are you considering doing this?

Thanks,

John

Community Forum : Breeze without EF

Thu, 08 Nov 2012 04:41:27 -700

Author: munissor
Subject: Breeze without EF
Posted: 08-Nov-2012 at 4:41am

I'm in the same situation, I'm trying to use breeze in a project where a DbContext is not there.

The approach is was following was to try to create the metadata on the client side, attaching it to the metadataStore.

However, after all the configuration the MetadataStore appears to be empty, and is still calling the Metadata endpoint.
This is the code I used for configuring an entity type.


var breeze = root.breeze;
var serviceName = 'http://.../api';
var metadataStore = new breeze.entityModel.MetadataStore();

// create a UserEntity
var userEntityType = new breeze.entityModel.EntityType({
    metadataStore: metadataStore,
    serviceName: serviceName,
    shortName: "User",
});
userEntityType.addProperty(new breeze.entityModel.DataProperty({ name: "Id", isPartOfKey:true }));
userEntityType.addProperty(new breeze.entityModel.DataProperty({ name: "Name" }));

breeze.core.config.setProperties({
    trackingImplementation: breeze.entityModel.entityTracking_ko,
    remoteAccessImplementation: breeze.entityModel.remoteAccess_webApi
});

// NOTE: at this point metadataStore.isEmpty() returns true
// but metadataStore.getEntityTypes() return the configured entity

// make the breeze manager available to the page as a property of the root object
root.ConfiguredEntityManager = new breeze.entityModel.EntityManager({
    serviceName: serviceName,
    metadataStore: metadataStore,
});

There is something that we are doing wrong?

Community Forum : Entity manager cache not working

Wed, 07 Nov 2012 20:22:28 -700

Author: WardBell
Subject: Entity manager cache not working
Posted: 07-Nov-2012 at 8:22pm

Perhaps you are wondering

(a) Why did the query return results but no entities in cache?

(b) Why did Breeze allow the model type and DbContext namespaces to be mismatched? Why didn't it protest?

Let me assure you that Breeze behaved exactly as intended ... if not in the way you expected.

In this example, the client query was routed to the Web API controller's "Items" method. The server responded with JSON data for a type 'Item" belonging to the namespace 'Model'. Breeze on the client doesn't know about an 'Item' type in the namespace 'Model'; it knows about an 'Item' type in the namespace 'Data'. But that's not the same type at all. Breeze simply doesn't know what type of data it received. Therefore, it cannot turn that data into 'Item' entities ... which is why there are no Items in cache.

But the server did return data and Breeze dutifully provides those data as JavaScript objects in the 'data.results' array of the query promise. In the post which started this thread, we know the server returned 45 'somethings'. They weren't entities - Breeze didn't know what they were. But you, the developer, asked for them and here they are.

Breeze does not demand that a query return entities. If the service returns data that it recognizes as entities - if the data are identified in metadata as entity types - Breeze will turn those data into entities and will put them in cache. Otherwise it forwards them to the caller via the promise.

There is nothing wrong with the server sending arbitrary data to the client. That's actually a useful feature. For example, suppose you have a Person entity and Person has 100 columns/properties including an image property that could be 100KB. We want to present a list of Persons, just their first and last names. We can't afford to download every property of every Person in the list.

Well, in Breeze we can make a "projection query" - a query for selected properties - and transmit only the properties we need. Clearly the data objects that satisfy our query are not whole Person entities. They are something else, something unnamed and un-typed. But something useful nonetheless.

Breeze doesn't judge. It doesn't insist that the query return whole Person entities. It simply examines the incoming data. If they are Persons, they become entities in cache. If not, fine, pass them along to the caller.

Therefore, Breeze shouldn't protest when it receives a data object of an unrecognized type. It was prepared to recognize 'Data.Item' data; it received 'Model.Item" data; no big deal ... and no entities in cache either.

---

This isn't the entire story. Actually, Breeze examines the incoming data objects looking for entities. If the incoming data are object graphs, Breeze traverses the graphs, looking for objects which it recognizes as entities. If it finds entities within the object graphs, it puts them in cache.

This is a super valuable feature. I use it to query and cache all of my pick-lists in a single shot. For example, I might create a service method called "Lookups" that returns a single object whose properties are arrays of Color, Status, Size, ProductType, ... you get the idea. That object is essentially a bag of lists that I'll use to populate comboboxes.

Then I make a single query to "Lookups" ... which returns this bag of lists. Now breeze doesn't recognize the bag at all. But each of the bag's properties is a a collection of objects that are described in metadata: Color is an entity type, Status is a type, Size is a type, ProductType is a type. Breeze recognizes that these nested objects are entities and puts them in cache.

So in a single request, in a single payload, I'm able to populate the EntityManager cache with all of the little pick-lists.

That's pretty cool.

Edited by WardBell - 07-Nov-2012 at 8:29pm

Community Forum : Entity manager cache not working

Wed, 07 Nov 2012 17:59:20 -700

Author: WardBell
Subject: Entity manager cache not working
Posted: 07-Nov-2012 at 5:59pm

Just so we're clear: classes in different projects can share the same namespace. This happens all the time; many Microsoft classes in different assemblies share the same namespace.

You may not want to do that but you certainly can.

If you don't want to do that, the Entity Framework DbContext documentation shows a simple workaround: create a subclass of the DbContext that is in the model's namespace. The DbContext subclass doesn't have to do anything other than inherit from your base DbContext ... and shift the namespace. This, I think, is a small price to pay to trick the metadata generation tooling.

I agree with separating the projects as you have done. That can be wise as models grow. Breeze will not interfere with that separation. You just need to spit on it a little bit to get the namespaces aligned.

-- The above is in reply to CCPony who wrote the following ... which somehow has disappeared (maybe I deleted by accident?) --

Placing the data components and the model files intoseparate projects and referencing those projects in the main web project causesthe error.

For example, if you have the following three projects:

BreezeTest.Model - contains item.cs

BreezeTest.Data - contains BreezeTestDatabaseInitializer.cs andBreezeTestDbContext.cs. This projects references BreezeTest.Model

BreezeTest.Web references both BreezeTest.Model and BreezeTest.Data

When you run BreezeTest.Web in this configuration you get: "3 items inquery" and "0 entities in cache".

As per Ward's attached sample, however, when all the files in the one project,you get "3 items in query" and "3 entities in cache".

So, the problem seems to be limited when using separate projects. By the way, Iused the RequireJs attachment.

Let me know if you have any other questions.

Edited by WardBell - 07-Nov-2012 at 6:08pm

Community Forum : Entity manager cache not working

Wed, 07 Nov 2012 17:52:44 -700

Author: svk
Subject: Entity manager cache not working
Posted: 07-Nov-2012 at 5:52pm

Sorry for the oversight... I previously read through all of the documentation and I must have overlooked this. It probably wasn't relevant at the time I read it. This is not a show stopper for me so I am happy to move on. thanks again.

Community Forum : Entity manager cache not working

Wed, 07 Nov 2012 17:44:17 -700

Author: CCPony
Subject: Entity manager cache not working
Posted: 07-Nov-2012 at 5:44pm

I did some testing just came to the same conclusion. Thanks for handling so quickly.

Edited by CCPony - 07-Nov-2012 at 6:04pm