DevForce 2009: non db entity handling

non db entity handling

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2009
Forum Discription: For .NET 3.5
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=1330
Printed Date: 29-Apr-2025 at 12:24pm

Topic: non db entity handling

Posted By: heyyou
Subject: non db entity handling
Date Posted: 16-Jun-2009 at 6:18pm

Whilst we are using Ideablade for our database entity CRUD operations, we also have some file based objects that need to be managed. What is the suggested method for accessing these types of elements when using Ideablade? Should we be adding a standard silverlight WCF service to our web app (which currently seems to break ideablade although I havent investigated fully yet as to the why or wherefore of this), or is there a way to integrate these kinds of operations with the Ideablad EntityManager?

Regards

Stuart

Replies:

Posted By: heyyou
Date Posted: 16-Jun-2009 at 7:17pm

Further to my exploration of this I notice that if I do add a Silverlight WCF service to the web app, the client definitely cannot find the Ideablade service (error returned is "The remote server returned an error: Not Found")

unless I remove the

config line. Once removed, Ideablade is back on line.

However, I would still like to know whether this is the appropriate architecture for accessing non entity based objects.

Regards

Stuart

Posted By: kimj
Date Posted: 17-Jun-2009 at 8:26pm

Regarding the problem with aspNetCompatibilityEnabled, this has been fixed as of version 5.1.1, available tomorrow. In prior versions the DevForce services would not work when this flag was enabled.

We have no recommendation about non-database entities. You could write a web/WCF service and consume them directly, or consume them as an addition to your domain model (although web service backed objects in DevForce Universal/SL have some limitations). Version 5.1.1 has also introduced support for POCO objects - so you could also write your own very simple provider and then consume these objects via the DevForce EntityManager. The release notes will have more information on this.