|
DevForce is not a Web Framework. It is a data access framework. DevForce is designed to access data from a rich client application over a network connection such as the Internet using standard protocols. Such rich client applications are written in WinForms, WPF or Silverlight and soon Javascript/HTML5. What all these applications have in common is that they are or can be delivered over the Web, but run on the client giving the user a desktop-like application experience. This is not your traditional ASP.NET experience where most of the code runs on the server and HTML with a sprinkle of Javascript is delivered to a browser on the client.
DevForce provides things like a fully queryable client side cache to avoid redundant expensive roundtrips to the server among other features. You can use DevForce server-side in an ASP.NET application, but we are probably the first once telling you that's not really what the product is designed for.
What DevForce provides is the ability to compose queries on the client, send them to the server and execute against EntityFramework and then package up the resulting entities and send them to the client, where they get cached. That's not what you do in a traditional ASP.NET app. In a traditional ASP.NET app you query the data on the server and then emit HTML with the data values embedded and send the HTML to the browser where it gets rendered.
DevForce can work in the ASP.NET architecture, but the feature set is really designed to be used by rich client applications.
|