| | All business logic can be kept in your classes, and hence no more updating multiple layers to modify or apply any new logic. |
| | All classes that build on top of our framework provide built in and robust concurrency management. Our approach lends you the complete flexibility and control on how you want to handle different scenarios associated with disconnected data. |
| | Quick Objects - Business Logic Framework has been built with consistency in mind. All classes and their relationships with each other work consistently throughout. Once you become familar with one class, the same rules and behaviour applies to the rest of them making it super easy to concentrate on the most important aspects of your application i.e. Business Logic and User Interface. |
| | You can use partial classes to customize the business objects. We have included samples that show how to create a centralized logic library and leverage such logic across multiple interfaces and also how to customize the business objects using partial classes.
|
| | Quick Objects - Business Logic Framework was built in such a way that you can create application code that is database independent and can run against any of the databases supported by the Quick Objects Business Logic Framework. |
| | Now it is easier than ever to work with data and objects in disconnected mode and syncronize the changes with the database at a later stage. The disconnect / offline mode of the business objects allow developers to very easily create applications that modify the data and retain the changes locally. The changes held locally can be either syncronized directly with the database or sent to a remote machine via remoting or web services to be syncronized. The disconnected model introduced in Quick Objects is very flexible and multiple related objects can continue to perform their Insert, Update, and Delete commands without a connection to the database.
The API for the business objects is exactly the same as it is in the connected mode, making it super easy for the same code to work in disconnected or connected mode by just setting one property. |
| | All business objects that extend the power of Business Logic Framework have a complete event model that can be used to further control various stages and operations of the business objects. |
| | By extending and building on top of the Quick Objects framework, the developers are able to selectively choose the data they need to retreive or modify. Since the slowest process usually is the disk IO, getting and updating unnecessary data results in loss of performance. Quick Objects however provides the flexibility needed by the developers to be able to handle a large number of situations without having to code for every single one of them. |
| | Each class provides great amount of control over how you retreive your data i.e. what columns, joined tables etc are included in the results or what columns and joined tables are going to be included in the search. Since, most modren IDE's provide intelli sense or other similar ways to help complete your code faster without having to remember the columns, relationships or table names. |
| | Quick Objects business logic framework is designed with high performance and flexibility in mind, the developers using this framework are able to re-use and benefit from already implemented optimization and performance improvement techniques. |
| | Our Business Logic Framework is designed to provide efficient access to data, and incorporates innovative techniques to return and access only a limited set of data as needed. More data can easily be retreived on demand. This technique can reduce processor, disk I/O and bandwidth needed to transfer data. |
| | Large Text, Binary and Xml Fields are fully supported. Binary/blog fields are available in the business objects as a binary array allowing you to directly load any document or image from the raw binary data. Xml fields (SQL 2005 or Oracle 9i or later) directly map to a XmlDocument in the business object. |
| | Starting version 4.0 a new feature has been introduced that allows you to specify your queries using LINQ. Quick Objects implementation of LINQ offers the flexibility and features not seen anywhere else. For example, you can specify a projection (visible columns) using LINQ and then instead of using the anonymous type created by LINQ, use the original business object instance instead. You always remain in control!!
|
| | Our framework offers the most comprehensive, consistent approach on handling null values from and to the database. Unlike the standard types introduced in .NET Framework and Nullable types introduced in .NET 2.0, our framework provides consistent behavior throughout, irresepective of what .NET Framework version you are writing code for. |
| | Clean and Robust Object Relational Mapping where your tables are mapped to classes and provide easy and quick way to perform Select/Add/Modify/Delete any data from your database. |
| | Complete mapping of all relationships and ability to create joins with parent or child objects to any level. |
| | All tables, columns and relationships between tables are represented in Classes and Properties. |
| | Classes built on the Business Logic Framework provide very powerful and complex searches on the database. This can be acheived without writing any database specific code and still maintaining full support for paged record sets.
|
| | Business Logic Framework is built with security in mind and applications relying on Business Logic Layer can take advantage of the built in techniques that protect your application and data from attacks such as sql injection attacks. |
| | XmlSerialization, Web Services and Serialization Support: Business Logic classes that are based on the Quick Objects framework can utilize the power of Serialization or XmlSerialization to create powerful distributed applications or objects that have capability to persist over time and across networks. |
| | The classes that build on top of our framework provide a solid layer of strongly typed objects that can be used in your application. Anytime the underlying database schema is modified, the business logic base layer can be updated with just a few clicks and hence we can rely on the compiler to find all the references to the tables, columns and relationships that may be outdated or modified. The best part is all this happens at design time, so you don't have to run your application to find out that you forgot to remove/modify a reference to a column or a relationship that was removed/renamed in the database. |