New Posts New Posts RSS Feed: Concerning an API
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Concerning an API

 Post Reply Post Reply
kjohnson View Drop Down

Joined: 19-Nov-2008
Posts: 19
Post Options Post Options   Quote kjohnson Quote  Post ReplyReply Direct Link To This Post Topic: Concerning an API
    Posted: 19-Mar-2012 at 10:12am
We've been working on an n-tier project using DevForce for sometime now. Recently, we have gotten inquires about end-users wanting an API so that they can access data for reporting use and integrating with other systems (such as Oracle).

What we are wanting to do is create an API that uses IdeaBlade to access our database, and to validate new records (such as adding new customers). But what the end-user works with are generic Visual Studio tools. For instance, our database has an entity type called 'Customer'. If the end-user requests a list of all customer, then each 'Customer' is converted to a more generic 'cCustomer' type that is defined in the API and not part of the IdeaBlade persistencemanager. It is then this 'cCustomer' class that the end-user works with. This is to provide a level of isolation from our database and keep the end-user from even needing to know about the IdeaBlade tools.

We would like to package the needed IdeaBlade dll's inside the Model.dll so that all the end-user sees is the model.dll and the apphelper.dll that they would include in their interface project. Unfortunately, we have not found a way to do this. Is there a way to accomplish this, or is there another option for doing something similar?
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down