This project is read-only.

LinqExtender 2.1

Rating:        Based on 1 rating
Reviewed:  0 reviews
Downloads: 4115
Released: Jun 2, 2009
Updated: Nov 26, 2010 by mehfuzh
Dev status: Beta Help Icon

Recommended Download

Documentation GettingStarted.doc
documentation, 84K, uploaded Jun 6, 2009 - 1986 downloads

Other Available Downloads

application, 97K, uploaded Jun 9, 2009 - 1143 downloads
Source Code
source code, 823K, uploaded Jun 9, 2009 - 986 downloads

Release Notes

Try the latest from (LinqExtender 3.0 bits)

This is a patch release over LinqExtender 2.0. it contains following additions that will be useful while building custom provider.
  1. No need to Implement IQueryObject for your entity objects, it will be internally implemented.
  2. Full coverage of xml documentation and 0 warning state.
  3. Visual Basic error fix for AndAlso query condition.
  4. Added further test for MSSQL CE for OpenLinqToSql sample ORM
  5. Renamed Query<T>.PRocess to Query<T>.SelectItem that makes for sense for select expresions.
  6. Removed confusing OnError event, rather extender should throw exception.
  7. For select query, Bucket now contains readonly properties.
  8. Medium trust support for auto implemenation and settings injection.
  9. Removed static mappings for Bucket rather added IBucket parameter in Query<T> overrrides. For creating fluent Bucket use the following :

     FluentBucket fluentBucket = FluentBucket.As(bucket);

  1. Both auto and manual Entity mapping via attribute and inheriting IQueryObject supported for medium trust enviroment.
  2. Define Extender settings via Fluent interface. Let's consider the following example taken from OpenLinqToSql sample ORM that comes with it.

            .Property(x => x.Id).MarkAsUnique
            .Property(x => x.Id).MapToAttribute("Bk_Id")
            .Property(x => x.ShelveId).MapToAttribute("Shelve_Id")
            .Property(x => x.Title).MapToAttribute("Bk_Title")
            .Property(x => x.BookInfo).MarkToIgnore()
    .InstantiateIn(this); // This is where the settings will be created.    

Add these lines in your Query<T> containter's constructor. You can use this interface along with fixed attributes in entity object; in that case settings will be super posed. Extender will still support attribute based mappings for backward comptability.

Updated on June 9, 2009
Fix : For property hiding using new keyword, extender should consider the lastest one not both.

Again thanks for all your reviews and support

Reviews for this release