Camlex.NET

Created Unassigned: No option to include Query tag in client xml [14001]

syoungPB — Sun, 16 Jun 2013 10:38:08 GMT

When using Camlex.Client the Query.ToString method has one overload which gives the option of including the View xml tag. If the option is set to false I would expect both the Query and Where tags to be output but only the Where tag is output.

New Post: "In" operator

sadomovalex — Sat, 15 Jun 2013 21:00:44 GMT

IN operation is now supported: Support for IN CAML operation: Camlex 3.5 and Camlex.Client 1.3 are released.

Updated Release: Camlex.Client 1.3 (Jun 15, 2013)

sadomovalex — Sat, 15 Jun 2013 19:02:49 GMT

Camlex.Client 1.3 release:

Support for In CAML operation

Camlex.Client 1.2 release:

Join several string conditions into single condition for query
Support for double (in CAML Number) native data type

Camlex.Client 1.1 release:
New features

Support for RowLimit

Camlex for client object model v.1.0:

References are changed to Microsoft.SharePoint.Client
Use ListItem instead of SPListItem
Remove guid and int indexers support (they don't exist in ListItem)
Modify .ToCaml() to only output XML with a surrounding View and Query elements

Released: Camlex.Client 1.3 (Jun 15, 2013)

Sat, 15 Jun 2013 19:02:49 GMT

Camlex.Client 1.3 release:

Support for In CAML operation

Camlex.Client 1.2 release:

Join several string conditions into single condition for query
Support for double (in CAML Number) native data type

Camlex.Client 1.1 release:
New features

Support for RowLimit

Camlex for client object model v.1.0:

References are changed to Microsoft.SharePoint.Client
Use ListItem instead of SPListItem
Remove guid and int indexers support (they don't exist in ListItem)
Modify .ToCaml() to only output XML with a surrounding View and Query elements

Updated Release: Camlex.NET 3.5 (Jun 15, 2013)

sadomovalex — Sat, 15 Jun 2013 18:52:17 GMT

Camlex.NET 3.5 release

New features

Support for In CAML operation

Camlex.NET 3.4 release

New features

Join several string conditions into single condition for query
Support for double (in CAML Number) native data type

Camlex.NET 3.3 release

New features

Add ToSPQuery() method to IQuery interface

Camlex.NET 3.2 release

New features

Add conditions to existing string queries

Camlex.NET 3.1 release

New features

Dynamic ViewFields

Camlex.NET 3.0 release

New features

Reverse engineering (CAML to C#)
Camlex Online http://camlex-online.org powered by Camlex.NET v.3.0

Camlex.NET 2.4 release

New features

Support for queries by user id (DataTypes.UserID)
Support for queries by current user id <UserID />

Camlex.NET 2.3 release

New features

Dynamic OrderBy statements

Camlex.NET 2.2 release

New features

Support for ViewFields

Camlex.NET 2.1 release

New features

Possibility to easily combine different independent expressions

Camlex.NET 2.0 release

New features

Search by field id
Support for native System.Guid type for values
Search by lookup id and lookup value
Dynamic filtering conditions

Camlex.NET 2.0 contains breaking changes:

SPListItem is used instead of SPItem
DataTypes.Lookup type is made internal. DataTypes.LookupValue and DataTypes.LookupId are introduced instead of DataTypes.Lookup

There is NO backward compatibility with 1.0 version.

For detailed description of new features see http://sadomovalex.blogspot.com/2010/04/camlexnet-20-for-sharepoint-released.html

Released: Camlex.NET 3.5 (Jun 15, 2013)

Sat, 15 Jun 2013 18:52:17 GMT

Camlex.NET 3.5 release

New features

Support for In CAML operation

Camlex.NET 3.4 release

New features

Join several string conditions into single condition for query
Support for double (in CAML Number) native data type

Camlex.NET 3.3 release

New features

Add ToSPQuery() method to IQuery interface

Camlex.NET 3.2 release

New features

Add conditions to existing string queries

Camlex.NET 3.1 release

New features

Dynamic ViewFields

Camlex.NET 3.0 release

New features

Reverse engineering (CAML to C#)
Camlex Online http://camlex-online.org powered by Camlex.NET v.3.0

Camlex.NET 2.4 release

New features

Support for queries by user id (DataTypes.UserID)
Support for queries by current user id <UserID />

Camlex.NET 2.3 release

New features

Dynamic OrderBy statements

Camlex.NET 2.2 release

New features

Support for ViewFields

Camlex.NET 2.1 release

New features

Possibility to easily combine different independent expressions

Camlex.NET 2.0 release

New features

Search by field id
Support for native System.Guid type for values
Search by lookup id and lookup value
Dynamic filtering conditions

Camlex.NET 2.0 contains breaking changes:

SPListItem is used instead of SPItem
DataTypes.Lookup type is made internal. DataTypes.LookupValue and DataTypes.LookupId are introduced instead of DataTypes.Lookup

There is NO backward compatibility with 1.0 version.

For detailed description of new features see http://sadomovalex.blogspot.com/2010/04/camlexnet-20-for-sharepoint-released.html

Updated Release: Camlex.Client 1.3 (Jun 15, 2013)

sadomovalex — Sat, 15 Jun 2013 18:49:14 GMT

Camlex.Client 1.3 release:

Support of In CAML operation

Camlex.Client 1.2 release:

Join several string conditions into single condition for query
Support for double (in CAML Number) native data type

Camlex.Client 1.1 release:
New features

Support for RowLimit

Camlex for client object model v.1.0:

References are changed to Microsoft.SharePoint.Client
Use ListItem instead of SPListItem
Remove guid and int indexers support (they don't exist in ListItem)
Modify .ToCaml() to only output XML with a surrounding View and Query elements

Updated Wiki: Home

sadomovalex — Sat, 15 Jun 2013 18:43:53 GMT

Project Description
Camlex.NET simplifies creating of CAML queries for Windows SharePoint Services by using expression trees.

If you find Camlex.NET useful, you may support its development via button on the online version http://camlex-online.org.

Client object model
Version for Client object model is also available. It can be downloaded from here: Camlex.Client.

Online version
You can convert your existing CAML queries to C# code for Camlex.NET using online service powered by Camlex: http://camlex-online.org.

Installation Instructions
In order to start working with Camlex.NET, please download and reference Camlex.NET.dll assembly in your project. After that you can create CAML queries using lambda expressions.
Starting from version 3.0 you can install NuGet package for Camlex from online packages gallery:

Install-Package Camlex.NET.dll

or Client version:

Install-Package Camlex.Client.dll

Quick Start
Camlex.NET is a new technique in Sharepoint development. It abstracts developers from syntax of CAML queries and helps them to concentrate on business tasks. With Camlex.NET developers could think about WHAT they need to do, instead of HOW to do it. It also brings the following advantages for Sharepoint developers:

Compile time checking of expressions
Natural and intuitive syntax using lambda expressions and fluent interfaces
Support for native .Net types (int, strings, bool, DateTime, Guid) and operations (==, !=, >, <, etc)
Support for Sharepoint-specific data types
Ability to specify non-constant expressions inside filtering conditions (variables, method calls, etc)
Fully customizable resulting query object
Ability to build dynamic filtering conditions and join them using And/Or logical joins
Search by lookup fields using LookupValue or LookupId

Now let's consider some basic scenarios:

Scenario 1. Simple query
Suppose that you need to select all items which have Status field set to Completed (following is the standard syntax of CAML):

<Where>
  <Eq>
    <FieldRef Name="Status" />
    <Value Type="Text">Completed</Value>
  </Eq>
</Where>

This query can be made with Camlex using the following syntax:

string caml =
    Camlex.Query()
        .Where(x => (string)x["Status"] == "Completed").ToString();

Notice, other comparison operations like “<”, “<=”, “>”, “>=” are supported as well.

Scenario 2. Query with “and”/”or” conditions
Suppose that you need to select items which have ProductID = 1000 and IsCompleted set to false or null. Syntax of appropriate standard CAML query follows:

<Where>
  <And>
    <Eq>
      <FieldRef Name="ProductID" />
      <Value Type="Integer">1000</Value>
    </Eq>
    <Or>
      <Eq>
        <FieldRef Name="IsCompleted" />
        <Value Type="Boolean">0</Value>
      </Eq>
      <IsNull>
        <FieldRef Name="IsCompleted" />
      </IsNull>
    </Or>
  </And>
</Where>

With help of Camlex it could be converted using following natural syntax:

var caml =
    Camlex.Query()
        .Where(x => (int)x["ProductID"] == 1000 && ((bool)x["IsCompleted"] == false || x["IsCompleted"] == null))
            .ToString();

Scenario 3. Query with DateTime
Lets suppose that you need to retrieve items which were modified on 01-Jan-2010:

<Where>
  <Eq>
    <FieldRef Name="Modified" />
    <Value Type="DateTime">2010-01-01T12:00:00Z</Value>
  </Eq>
</Where>

Using Camlex you can simply write:

var caml =
    Camlex.Query()
        .Where(x => (DateTime)x["Modified"] == new DateTime(2010, 01, 01)).ToString();

Scenario 4. Query with BeginsWith and Contains operations
Consider the query that should return items which Title field starts with “Task” and Project field contains “Camlex”:

<Where>
  <And>
    <BeginsWith>
      <FieldRef Name="Title" />
      <Value Type="Text">Task</Value>
    </BeginsWith>
    <Contains>
      <FieldRef Name="Project" />
      <Value Type="Text">Camlex</Value>
    </Contains>
  </And>
</Where>

You can achieve result using the following natural syntax:

var caml =
    Camlex.Query()
        .Where(x => ((string)x["Title"]).StartsWith("Task") && ((string)x["Project"]).Contains("Camlex"))
            .ToString();

Scenario 5. Query with none C# native data types
Suppose that you need to retrieve all items modified by Administrator:

<Where>
  <Eq>
    <FieldRef Name="Editor" />
    <Value Type="User">Administrator</Value>
  </Eq>
</Where>

Notice that value is of Sharepoint-specific User data type. You can easily achieve the result with alternative string-based syntax:

var caml =
    Camlex.Query()
        .Where(x => x["Editor"] == (DataTypes.User)"Administrator")
                .ToString();

Scenario 6. Query with sorting (OrderBy)
Suppose that you need to select all items which have ID >= 5 and the result should be sorted by Modified field:

<Where>
  <Geq>
    <FieldRef Name="ID" />
    <Value Type="Integer">5</Value>
  </Geq>
</Where>
<OrderBy>
  <FieldRef Name="Modified" />
</OrderBy>

You need to write the following Camlex expression in order to construct this query:

var caml =
    Camlex.Query()
        .Where(x => (int)x["ID"] >= 5)
        .OrderBy(x => x["Modified"]).ToString();

Scenario 7. Query with grouping (GroupBy)
Suppose that we need to select items having not-null Status field and result set should be grouped by Author field:

<Where>
  <IsNotNull>
    <FieldRef Name="Status" />
  </IsNotNull>
</Where>
<GroupBy>
  <FieldRef Name="Author" />
</GroupBy>

With Camlex you could simply rewrite it as:

var caml =
    Camlex.Query()
        .Where(x => x["Status"] != null)
        .GroupBy(x => x["Author"]).ToString();

Scenario 8. Query with non-constant expressions in lvalue and rvalue
Non-constant expression gives you more control over CAML. Suppose that you need to select items depending on current locale: for English locale you need to select items which have TitleEng field set to “eng”; for non-English locale you need to select items which have Title field set to “non-eng”. I.e.:
Query for English locale:

<Where>
  <Eq>
    <FieldRef Name="TitleEng" />
    <Value Type="Text">eng</Value>
  </Eq>
</Where>

Query for non-English locale:

<Where>
  <Eq>
    <FieldRef Name="Title" />
    <Value Type="Text">non-eng</Value>
  </Eq>
</Where>

It is not so hard with Camlex:

bool isEng = true; // or false depending on Thread.CurrentThread.CurrentUICulture

var caml =
    Camlex.Query()
        .Where(x => (string)x[isEng ? "TitleEng" : "Title"] == (isEng ? "eng" : "non-eng")).ToString();

Scenario 9. Dynamic filtering conditions
Starting with 2.0 version you can build dynamic filtering conditions and join them using WhereAll/WhereAny methods which use And/Or logical joins respectively.
Suppose that we need to retrieve all items which contain at least one of the values {“hello”, “greeting”, “hi”} in Title field. I.e. we need to use the following CAML query:

<Where>
  <Or>
    <Or>
      <Contains>
        <FieldRef Name="Title" />
        <Value Type="Text">hello</Value>
      </Contains>
      <Contains>
        <FieldRef Name="Title" />
        <Value Type="Text">greeting</Value>
      </Contains>
    </Or>
    <Contains>
      <FieldRef Name="Title" />
      <Value Type="Text">hi</Value>
    </Contains>
  </Or>
</Where>

With Camlex.NET 2.0 we can create lambda expression for each condition and pass them into new WhereAny method:

// list of tokens
var tokens = new List<string> { "hello", "greeting", "hi" };
var expressions = new List<Expression<Func<SPListItem, bool>>>();

// create lambda expression for each token in list
foreach (string t in tokens)
{
    string token = t;
   expressions.Add(x => ((string)x["Title"]).Contains(token));
}

// prepare query
var caml = Camlex.Query().WhereAny(expressions).ToString();

Updated Wiki: Home

sadomovalex — Sat, 15 Jun 2013 18:43:32 GMT

Install-Package Camlex.NET.dll

or Client version:

Install-Package Camlex.Client.dll

Compile time checking of expressions
Natural and intuitive syntax using lambda expressions and fluent interfaces
Support for native .Net types (int, strings, bool, DateTime, Guid) and operations (==, !=, >, <, etc)
Support for Sharepoint-specific data types
Ability to specify non-constant expressions inside filtering conditions (variables, method calls, etc)
Fully customizable resulting query object
Ability to build dynamic filtering conditions and join them using And/Or logical joins
Search by lookup fields using LookupValue or LookupId

Now let's consider some basic scenarios:

Scenario 1. Simple query
Suppose that you need to select all items which have Status field set to Completed (following is the standard syntax of CAML):

<Where>
  <Eq>
    <FieldRef Name="Status" />
    <Value Type="Text">Completed</Value>
  </Eq>
</Where>

This query can be made with Camlex using the following syntax:

string caml =
    Camlex.Query()
        .Where(x => (string)x["Status"] == "Completed").ToString();

<Where>
  <And>
    <Eq>
      <FieldRef Name="ProductID" />
      <Value Type="Integer">1000</Value>
    </Eq>
    <Or>
      <Eq>
        <FieldRef Name="IsCompleted" />
        <Value Type="Boolean">0</Value>
      </Eq>
      <IsNull>
        <FieldRef Name="IsCompleted" />
      </IsNull>
    </Or>
  </And>
</Where>

With help of Camlex it could be converted using following natural syntax:

var caml =
    Camlex.Query()
        .Where(x => (int)x["ProductID"] == 1000 && ((bool)x["IsCompleted"] == false || x["IsCompleted"] == null))
            .ToString();

Scenario 3. Query with DateTime
Lets suppose that you need to retrieve items which were modified on 01-Jan-2010:

<Where>
  <Eq>
    <FieldRef Name="Modified" />
    <Value Type="DateTime">2010-01-01T12:00:00Z</Value>
  </Eq>
</Where>

Using Camlex you can simply write:

var caml =
    Camlex.Query()
        .Where(x => (DateTime)x["Modified"] == new DateTime(2010, 01, 01)).ToString();

Scenario 4. Query with BeginsWith and Contains operations
Consider the query that should return items which Title field starts with “Task” and Project field contains “Camlex”:

<Where>
  <And>
    <BeginsWith>
      <FieldRef Name="Title" />
      <Value Type="Text">Task</Value>
    </BeginsWith>
    <Contains>
      <FieldRef Name="Project" />
      <Value Type="Text">Camlex</Value>
    </Contains>
  </And>
</Where>

You can achieve result using the following natural syntax:

var caml =
    Camlex.Query()
        .Where(x => ((string)x["Title"]).StartsWith("Task") && ((string)x["Project"]).Contains("Camlex"))
            .ToString();

Scenario 5. Query with none C# native data types
Suppose that you need to retrieve all items modified by Administrator:

<Where>
  <Eq>
    <FieldRef Name="Editor" />
    <Value Type="User">Administrator</Value>
  </Eq>
</Where>

Notice that value is of Sharepoint-specific User data type. You can easily achieve the result with alternative string-based syntax:

var caml =
    Camlex.Query()
        .Where(x => x["Editor"] == (DataTypes.User)"Administrator")
                .ToString();

Scenario 6. Query with sorting (OrderBy)
Suppose that you need to select all items which have ID >= 5 and the result should be sorted by Modified field:

<Where>
  <Geq>
    <FieldRef Name="ID" />
    <Value Type="Integer">5</Value>
  </Geq>
</Where>
<OrderBy>
  <FieldRef Name="Modified" />
</OrderBy>

You need to write the following Camlex expression in order to construct this query:

var caml =
    Camlex.Query()
        .Where(x => (int)x["ID"] >= 5)
        .OrderBy(x => x["Modified"]).ToString();

Scenario 7. Query with grouping (GroupBy)
Suppose that we need to select items having not-null Status field and result set should be grouped by Author field:

<Where>
  <IsNotNull>
    <FieldRef Name="Status" />
  </IsNotNull>
</Where>
<GroupBy>
  <FieldRef Name="Author" />
</GroupBy>

With Camlex you could simply rewrite it as:

var caml =
    Camlex.Query()
        .Where(x => x["Status"] != null)
        .GroupBy(x => x["Author"]).ToString();

<Where>
  <Eq>
    <FieldRef Name="TitleEng" />
    <Value Type="Text">eng</Value>
  </Eq>
</Where>

Query for non-English locale:

<Where>
  <Eq>
    <FieldRef Name="Title" />
    <Value Type="Text">non-eng</Value>
  </Eq>
</Where>

It is not so hard with Camlex:

bool isEng = true; // or false depending on Thread.CurrentThread.CurrentUICulture

var caml =
    Camlex.Query()
        .Where(x => (string)x[isEng ? "TitleEng" : "Title"] == (isEng ? "eng" : "non-eng")).ToString();

<Where>
  <Or>
    <Or>
      <Contains>
        <FieldRef Name="Title" />
        <Value Type="Text">hello</Value>
      </Contains>
      <Contains>
        <FieldRef Name="Title" />
        <Value Type="Text">greeting</Value>
      </Contains>
    </Or>
    <Contains>
      <FieldRef Name="Title" />
      <Value Type="Text">hi</Value>
    </Contains>
  </Or>
</Where>

With Camlex.NET 2.0 we can create lambda expression for each condition and pass them into new WhereAny method:

// list of tokens
var tokens = new List<string> { "hello", "greeting", "hi" };
var expressions = new List<Expression<Func<SPListItem, bool>>>();

// create lambda expression for each token in list
foreach (string t in tokens)
{
    string token = t;
   expressions.Add(x => ((string)x["Title"]).Contains(token));
}

// prepare query
var caml = Camlex.Query().WhereAny(expressions).ToString();

Updated Wiki: Home

sadomovalex — Sat, 15 Jun 2013 18:42:57 GMT

Install-Package Camlex.NET.dll

or Client version:

Install-Package Camlex.Client.dll

Compile time checking of expressions
Natural and intuitive syntax using lambda expressions and fluent interfaces
Support for native .Net types (int, strings, bool, DateTime, Guid) and operations (==, !=, >, <, etc)
Support for Sharepoint-specific data types
Ability to specify non-constant expressions inside filtering conditions (variables, method calls, etc)
Fully customizable resulting query object
Ability to build dynamic filtering conditions and join them using And/Or logical joins
Search by lookup fields using LookupValue or LookupId

Now let's consider some basic scenarios:

Scenario 1. Simple query
Suppose that you need to select all items which have Status field set to Completed (following is the standard syntax of CAML):

<Where>
  <Eq>
    <FieldRef Name="Status" />
    <Value Type="Text">Completed</Value>
  </Eq>
</Where>

This query can be made with Camlex using the following syntax:

string caml =
    Camlex.Query()
        .Where(x => (string)x["Status"] == "Completed").ToString();

<Where>
  <And>
    <Eq>
      <FieldRef Name="ProductID" />
      <Value Type="Integer">1000</Value>
    </Eq>
    <Or>
      <Eq>
        <FieldRef Name="IsCompleted" />
        <Value Type="Boolean">0</Value>
      </Eq>
      <IsNull>
        <FieldRef Name="IsCompleted" />
      </IsNull>
    </Or>
  </And>
</Where>

With help of Camlex it could be converted using following natural syntax:

var caml =
    Camlex.Query()
        .Where(x => (int)x["ProductID"] == 1000 && ((bool)x["IsCompleted"] == false || x["IsCompleted"] == null))
            .ToString();

Scenario 3. Query with DateTime
Lets suppose that you need to retrieve items which were modified on 01-Jan-2010:

<Where>
  <Eq>
    <FieldRef Name="Modified" />
    <Value Type="DateTime">2010-01-01T12:00:00Z</Value>
  </Eq>
</Where>

Using Camlex you can simply write:

var caml =
    Camlex.Query()
        .Where(x => (DateTime)x["Modified"] == new DateTime(2010, 01, 01)).ToString();

Scenario 4. Query with BeginsWith and Contains operations
Consider the query that should return items which Title field starts with “Task” and Project field contains “Camlex”:

<Where>
  <And>
    <BeginsWith>
      <FieldRef Name="Title" />
      <Value Type="Text">Task</Value>
    </BeginsWith>
    <Contains>
      <FieldRef Name="Project" />
      <Value Type="Text">Camlex</Value>
    </Contains>
  </And>
</Where>

You can achieve result using the following natural syntax:

var caml =
    Camlex.Query()
        .Where(x => ((string)x["Title"]).StartsWith("Task") && ((string)x["Project"]).Contains("Camlex"))
            .ToString();

Scenario 5. Query with none C# native data types
Suppose that you need to retrieve all items modified by Administrator:

<Where>
  <Eq>
    <FieldRef Name="Editor" />
    <Value Type="User">Administrator</Value>
  </Eq>
</Where>

Notice that value is of Sharepoint-specific User data type. You can easily achieve the result with alternative string-based syntax:

var caml =
    Camlex.Query()
        .Where(x => x["Editor"] == (DataTypes.User)"Administrator")
                .ToString();

Scenario 6. Query with sorting (OrderBy)
Suppose that you need to select all items which have ID >= 5 and the result should be sorted by Modified field:

<Where>
  <Geq>
    <FieldRef Name="ID" />
    <Value Type="Integer">5</Value>
  </Geq>
</Where>
<OrderBy>
  <FieldRef Name="Modified" />
</OrderBy>

You need to write the following Camlex expression in order to construct this query:

var caml =
    Camlex.Query()
        .Where(x => (int)x["ID"] >= 5)
        .OrderBy(x => x["Modified"]).ToString();

Scenario 7. Query with grouping (GroupBy)
Suppose that we need to select items having not-null Status field and result set should be grouped by Author field:

<Where>
  <IsNotNull>
    <FieldRef Name="Status" />
  </IsNotNull>
</Where>
<GroupBy>
  <FieldRef Name="Author" />
</GroupBy>

With Camlex you could simply rewrite it as:

var caml =
    Camlex.Query()
        .Where(x => x["Status"] != null)
        .GroupBy(x => x["Author"]).ToString();

<Where>
  <Eq>
    <FieldRef Name="TitleEng" />
    <Value Type="Text">eng</Value>
  </Eq>
</Where>

Query for non-English locale:

<Where>
  <Eq>
    <FieldRef Name="Title" />
    <Value Type="Text">non-eng</Value>
  </Eq>
</Where>

It is not so hard with Camlex:

bool isEng = true; // or false depending on Thread.CurrentThread.CurrentUICulture

var caml =
    Camlex.Query()
        .Where(x => (string)x[isEng ? "TitleEng" : "Title"] == (isEng ? "eng" : "non-eng")).ToString();

<Where>
  <Or>
    <Or>
      <Contains>
        <FieldRef Name="Title" />
        <Value Type="Text">hello</Value>
      </Contains>
      <Contains>
        <FieldRef Name="Title" />
        <Value Type="Text">greeting</Value>
      </Contains>
    </Or>
    <Contains>
      <FieldRef Name="Title" />
      <Value Type="Text">hi</Value>
    </Contains>
  </Or>
</Where>

With Camlex.NET 2.0 we can create lambda expression for each condition and pass them into new WhereAny method:

// list of tokens
var tokens = new List<string> { "hello", "greeting", "hi" };
var expressions = new List<Expression<Func<SPListItem, bool>>>();

// create lambda expression for each token in list
foreach (string t in tokens)
{
    string token = t;
   expressions.Add(x => ((string)x["Title"]).Contains(token));
}

// prepare query
var caml = Camlex.Query().WhereAny(expressions).ToString();

Source code checked in, #5f17044ef6b1

sadomovalex — Sat, 15 Jun 2013 18:36:29 GMT

Change assembly version

Source code checked in, #6e677dc3ba38

sadomovalex — Sat, 15 Jun 2013 18:31:32 GMT

Fix tests

Source code checked in, #ff76997f3d47

sadomovalex — Sat, 15 Jun 2013 18:23:09 GMT

Merge default -> client

Source code checked in, #f856ac843614

sadomovalex — Sat, 15 Jun 2013 18:02:59 GMT

Change assembly version

Source code checked in, #8ff82d2573c9

sadomovalex — Sat, 15 Jun 2013 17:53:45 GMT

Merge sp2010_operators -> default

Source code checked in, #fbf09f0bb1a6

sadomovalex — Sat, 15 Jun 2013 09:49:54 GMT

More tests

Source code checked in, #21ad8c7e418b

sadomovalex — Sat, 15 Jun 2013 09:42:08 GMT

Reverse for In operation

Source code checked in, #cebea2f3c36f

sadomovalex — Sat, 15 Jun 2013 09:07:12 GMT

Reverse for In operation

Source code checked in, #e48246bab776

sadomovalex — Sat, 15 Jun 2013 08:12:44 GMT

Reverse for In operation

Source code checked in, #3a573a4cfb60

sadomovalex — Fri, 14 Jun 2013 22:20:32 GMT

* Work over In operator support * More tests