A data abstraction layer for .net applications. Write your application code to be database neutral. Swap out the type of database your application uses without updating or even recompiling your business components.
Be the first to post a text review of XQuiSoft data abstraction layer. Rate and review a project by clicking thumbs up or thumbs down in the right column.
** 2.2 + demo project finally updated to utilize latest features. + documentation (word document) updated recommending latest features (in 2.0) with recommended design shown in updated demo project. ** 2.1 + more robust handling of null on return parameter values. + new Oracle client implementation (separate project - dll output) ** 2.0 + Added method overloads to Procedure that take parameter constructor values, including Value for the case when db 'maps' are not being used. + Added DbContext.ExecuteReader, DataProvider.ExecuteReader, and the same for the SqlClient versions. This feature was made possible by the DbContext concept (added in v1.5.5000.0). It would have been difficult to manage beforehand. + Aded DbContext.Execute overload tht takes a method delegate in place of an IDataFactory instance. Same overload was added to DataProvider and SqlDbContext. ** 1.6.5000.0 + removed DataProvider.Name overload and call base.Initialize from Initialize + fixed bug - DataProviderCollection constructor now passes correct type to base class. ** 1.5.5000.0 +number sychronized with rest of this XQuiSoft core release +References the updated Provider pattern implementation in XQuiSoft.Provider v 1.5.5000.0 +Added DbContext class. This class is used when multiple data operations need to be wrapped into a single transaction. It contains the implementations of all the Execute commands from DataProvider. +DataProvider adds abstract method GetContext(). +DataProvider delegates Exectute method calls to a new instance returned from GetContext(). Essentially these are useful when only a single db call needs to be made that is not part of a transaction. This also provides backward compatibility for code that used these before. +DataProvider.BeginTransaction was removed. Instead create a new DbContext and BeginTransaction on it. +DataProvider.CommitTransaction was removed. Use a DbContext instead. +DataProvider.RollbackTransaction was removed. Use a DbContext instead. ** 1.3.5000.0 +Added DataProvider abstract method CheckConnectability(...), also added to SqlDataProvider. +use ProviderHelper to read configuration values **1.2.5000.0 Updated to use the new object pooling feature of the provider component. **1.1.5000.0 Added a Default property to DataManager.Providers. This allows access to the default provider as defined in the configuration. This is not necassarily the connection with a name of 'Default'. Now any other classes that use the DataManager do not have to explicitely define which connectionName they wish to use. -no new bugs found/fixed dependency: XQuiSoft.Provider 1.0.5000.2 **1.0.5000.2 added more license details to AssemblyInfo -no new bugs found/fixed -no new features dependency: XQuiSoft.Provider 1.0.5000.2 **1.0.5000.1 fix bug where output parameters were not being populated -no new features dependency: XQuiSoft.Provider 1.0.5000.1
** 2.2 + demo project finally updated to utilize latest features. + documentation (word document) updated recommending latest features (in 2.0) with recommended design shown in updated demo project. ** 2.1 + more robust handling of null on return parameter values. + new Oracle client implementation (separate project - dll output) ** 2.0 + Added method overloads to Procedure that take parameter constructor values, including Value for the case when db 'maps' are not being used. + Added DbContext.ExecuteReader, DataProvider.ExecuteReader, and the same for the SqlClient versions. This feature was made possible by the DbContext concept (added in v1.5.5000.0). It would have been difficult to manage beforehand. + Aded DbContext.Execute overload tht takes a method delegate in place of an IDataFactory instance. Same overload was added to DataProvider and SqlDbContext. ** 1.6.5000.0 + removed DataProvider.Name overload and call base.Initialize from Initialize + fixed bug - DataProviderCollection constructor now passes correct type to base class. ** 1.5.5000.0 +number sychronized with rest of this XQuiSoft core release +References the updated Provider pattern implementation in XQuiSoft.Provider v 1.5.5000.0 +Added DbContext class. This class is used when multiple data operations need to be wrapped into a single transaction. It contains the implementations of all the Execute commands from DataProvider. +DataProvider adds abstract method GetContext(). +DataProvider delegates Exectute method calls to a new instance returned from GetContext(). Essentially these are useful when only a single db call needs to be made that is not part of a transaction. This also provides backward compatibility for code that used these before. +DataProvider.BeginTransaction was removed. Instead create a new DbContext and BeginTransaction on it. +DataProvider.CommitTransaction was removed. Use a DbContext instead. +DataProvider.RollbackTransaction was removed. Use a DbContext instead. ** 1.3.5000.0 +Added DataProvider abstract method CheckConnectability(...), also added to SqlDataProvider. +use ProviderHelper to read configuration values **1.2.5000.0 Updated to use the new object pooling feature of the provider component. **1.1.5000.0 Added a Default property to DataManager.Providers. This allows access to the default provider as defined in the configuration. This is not necassarily the connection with a name of 'Default'. Now any other classes that use the DataManager do not have to explicitely define which connectionName they wish to use. -no new bugs found/fixed dependency: XQuiSoft.Provider 1.0.5000.2 **1.0.5000.2 added more license details to AssemblyInfo -no new bugs found/fixed -no new features dependency: XQuiSoft.Provider 1.0.5000.2 **1.0.5000.1 fix bug where output parameters were not being populated -no new features dependency: XQuiSoft.Provider 1.0.5000.1
** 2.1 + more robust handling of null on return parameter values. + new Oracle client implementation (separate project - dll output) ** 2.0 + Added method overloads to Procedure that take parameter constructor values, including Value for the case when db 'maps' are not being used. + Added DbContext.ExecuteReader, DataProvider.ExecuteReader, and the same for the SqlClient versions. This feature was made possible by the DbContext concept (added in v1.5.5000.0). It would have been difficult to manage beforehand. + Aded DbContext.Execute overload tht takes a method delegate in place of an IDataFactory instance. Same overload was added to DataProvider and SqlDbContext.
** 2.1 + more robust handling of null on return parameter values. + new Oracle client implementation (separate project - dll output) ** 2.0 + Added method overloads to Procedure that take parameter constructor values, including Value for the case when db 'maps' are not being used. + Added DbContext.ExecuteReader, DataProvider.ExecuteReader, and the same for the SqlClient versions. This feature was made possible by the DbContext concept (added in v1.5.5000.0). It would have been difficult to manage beforehand. + Aded DbContext.Execute overload tht takes a method delegate in place of an IDataFactory instance. Same overload was added to DataProvider and SqlDbContext.
Be the first person to add a text review.
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?
Thanks for your review!
Get credit for your review by logging in via OpenID. Click your account provider: