RapidDevBookCode Wiki & Documentation Rss Feed

Updated Wiki: LLBL4linqpad

JezzaT — Fri, 19 Apr 2013 09:50:28 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

I have written a LLBLGen Pro Typed Data Context Driver for LINQPad which provides first-class support for LLBLGen Pro ILinqMetaData to enable, amongst other things, the generated entities to be shown in the Schema Explorer.

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad drivers for LLBLGen Pro v3.5 and 4.0, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support selection of Additional assemblies and namespaces
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2 now out of date)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1(V2.2.1), 3.5 and 4.0 (V2.3.1) Data Context Driver, version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV4.0.DataContextDriver.lpx, AW.LLBLGenV3.5.DataContextDriver.lpx, AW.LLBLGenV3.1.DataContextDriver.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

Exclude EntityBase Properties
Default Linqpad behaviour
Use the Editable Data Grid included with the driver rather than the read-only LinqPad one
Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

This allows you to have custom code executed when the adapter is created and maybe select the appropriate adapter based on the connection string (or whatever data the string parameter has). The assembly, type and method name must be supplied.

Default connection properties

If you want to have a lot of connections with similar properties you can specify defaults to populate new connections. These can set by either the 'save as default' button in the first tab of the connection dialog or by editing them directly in the third tab shown below. This allows you to easily clone a connection say if you want to have the same code connected to multiple databases. This is redundant now that LINQPad has the ‘Create Similar Connection…’ feature.

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

If you want to have additional assemblies and namespaces used in the queries against your typed data context (ILinqMetaData) these can be specified in ‘Driver’ tab of the connection dialog shown above or in the ‘Additional Assemblies and Namespaces’ tab shown below.

The ‘Driver’ tab assemblies and namespaces are global to the AW.LLBLGen.DataContextDriver, while the ‘Additional Assemblies and Namespaces’ (version 2.3 and later only) are per connection. The additional assemblies can have relative or absolute paths. This an alternative to specifying them in each query. The ‘Add namespaces from selected assemblies’ button adds all the namespaces from any selected assemblies in the ‘Additional Assemblies’ grid plus all the assemblies defined in the driver.

SQL Translation Tab

The LLBL version 3.5 driver will show a non-executable SQL log in the SQL Translation Tab when a query is run using the TraceHelper.QueryExecutionSwitch. In earlier versions or to view executable SQL you must define an event called SQLTraceEvent in your data adapters or, if using LLBL 3.x selfservicing, a static event of that name in the CommonDaoBase class, e.g

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
public IQuery Query { get; private set; }
public SQLTraceEventArgs(IQuery query)
{
if (query == null) throw new ArgumentNullException("query");
Query = query;
}
}

See SQLTraceEventArgs.cs and CommonDaoBase.Extended.cs in the LLBL Pro v3.1 branch for an example of how to do this.
For selfservicing the SQL trace only works for entity queries but not projections.

For Adapter you could add references to AW.Helper.dll and AW.Helper.LLBL.dll and then put this in your DataAccessAdapter:

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse)
{
var qf = new Northwind.DAL.FactoryClasses.QueryFactory();
var q = qf.Customer
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId)
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId)
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId))
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

adapter.FetchQuery(q).Dump();
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: EnumerableDebugVisualizer

JezzaT — Fri, 12 Apr 2013 10:44:25 GMT

I have created an enumerable Debugger Visualizer for Visual Studio that displays any registered IEnumerable object in a datagridview.

Installation

Binary

Download AW.EnumerableVisualizer.dll(VS2008) or AW.EnumerableVisualizer.dll(VS2010) or AW.EnumerableVisualizer.dll(VS2012) then copy it to either of the debugger visualizers directories: How to: Install a Visualizer

Source code

Repository code is downloadable from the source code tab though I recommend using TortoiseSVN for the getting the source from the repository.
Build the solution AW.DebugVisualizers.sln
If you have ILMerge installed run MergeAndDeploy.Bat after doing a Release build
If not run DebugDeploy.bat which copies AW.DebugVisualizers.dll, AW.Helper.dll, AW.Winforms.Helpers.dll, Dynamic.dll and ObjectListView.dll to %userprofile%\My Documents\Visual Studio 2008(or 2010)\Visualizers

Note

Unfortunately you can't register a debugger visualizer for interfaces so every IEnumerable class must registered individually. The list of classes that are currently registered can be seen in the file VisualizerRegistrations.cs, you can easily add more.

Updated Wiki: LLBL4linqpad

JezzaT — Sun, 17 Feb 2013 10:39:01 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support selection of Additional assemblies and namespaces
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2 now out of date)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1(V2.2.1) and 3.5 (V2.3.1) Data Context Driver, version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriver.lpx, AW.LLBLGenV3.1.DataContextDriver.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

Exclude EntityBase Properties
Default Linqpad behaviour
Use the Editable Data Grid included with the driver rather than the read-only LinqPad one
Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sun, 17 Feb 2013 10:23:38 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2 now out of date)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

Exclude EntityBase Properties
Default Linqpad behaviour
Use the Editable Data Grid included with the driver rather than the read-only LinqPad one
Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sun, 17 Feb 2013 10:20:50 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2 now out of date)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

Exclude EntityBase Properties
Default Linqpad behaviour
Use the Editable Data Grid included with the driver rather than the read-only LinqPad one
Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sun, 17 Feb 2013 10:18:14 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2 now out of date)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

Exclude EntityBase Properties
Default Linqpad behaviour
Use the Editable Data Grid included with the driver rather than the read-only LinqPad one
Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sun, 17 Feb 2013 10:02:29 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2 now out of date)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

Exclude EntityBase Properties
Default Linqpad behaviour
Use the Editable Data Grid included with the driver rather than the read-only LinqPad one
Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

The ‘Driver’ tab assemblies and namespaces are global to the AW.LLBLGen.DataContextDriver, while the ‘Additional Assemblies and Namespaces’ (version 2.3 and later only) are per connection. The additional assemblies can have relative or absolute paths. This an alternative to specifying them in each query. The ‘Add namespaces from selected assemblies’ buttons adds all the namespaces from any selected assemblies in the ‘Additional Assemblies’ grid plus all the assemblies defined in the driver.

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
  public IQuery Query { get; private set; }
  public SQLTraceEventArgs(IQuery query)
  {
    if (query == null) throw new ArgumentNullException("query");
    Query = query;
  }
}

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sun, 17 Feb 2013 09:04:31 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2 now out of date)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

Exclude EntityBase Properties
Default Linqpad behaviour
Use the Editable Data Grid included with the driver rather than the read-only LinqPad one
Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

If you want to have additional assemblies and namespaces used in the queries against your typed data context (ILinqMetaData) these can be specified in third tab of the connection dialog shown above.
Unfortunately these assemblies and namespaces are global to the AW.LLBLGen.DataContextDriver, I investigated having them per connection but the additional assemblies and namespaces for the driver are set before the connection is loaded into the driver.
The additional assemblies can have relative or absolute paths. This an alternative to specifying them in each query.

SQL Translation Tab

To view the SQL generated when a query is run in the SQL Translation Tab you must define an event called SQLTraceEvent in your data adapters or, if using LLBL 3.x selfservicing, a static event of that name in the CommonDaoBase class, e.g

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
  public IQuery Query { get; private set; }
  public SQLTraceEventArgs(IQuery query)
  {
    if (query == null) throw new ArgumentNullException("query");
    Query = query;
  }
}

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sat, 01 Dec 2012 08:56:21 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

Exclude EntityBase Properties
Default Linqpad behaviour
Use the Editable Data Grid included with the driver rather than the read-only LinqPad one
Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
  public IQuery Query { get; private set; }
  public SQLTraceEventArgs(IQuery query)
  {
    if (query == null) throw new ArgumentNullException("query");
    Query = query;
  }
}

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sat, 01 Dec 2012 08:55:31 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

Exclude EntityBase Properties

Default Linqpad behaviour

Use the Editable Data Grid included with the driver rather than the read-only LinqPad one

Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
  public IQuery Query { get; private set; }
  public SQLTraceEventArgs(IQuery query)
  {
    if (query == null) throw new ArgumentNullException("query");
    Query = query;
  }
}

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sat, 01 Dec 2012 08:52:50 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

Exclude EntityBase Properties

Default Linqpad behaviour

Use the Editable Data Grid included with the driver rather than the read-only LinqPad one

Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
  public IQuery Query { get; private set; }
  public SQLTraceEventArgs(IQuery query)
  {
    if (query == null) throw new ArgumentNullException("query");
    Query = query;
  }
}

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sat, 01 Dec 2012 08:51:34 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

There are 4 options for display the results of a query in a grid

```
Exclude EntityBase Properties
```
```
Default Linqpad behaviour
```

Use the Editable Data Grid included with the driver rather than the read-only LinqPad one

Use the Editable Data Grid with a page size of 10

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
  public IQuery Query { get; private set; }
  public SQLTraceEventArgs(IQuery query)
  {
    if (query == null) throw new ArgumentNullException("query");
    Query = query;
  }
}

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sat, 01 Dec 2012 08:44:56 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

  public enum DisplayInGrid
  {
    [Description("Exclude EntityBase Properties")]
    ExcludeEntityBaseProperties,
    [Description("Default Linqpad behaviour")]
    AllProperties,
    [Description("Use the Editable Data Grid included with the driver rather than the LinqPad one")]
    UseEditableGrid,
    [Description("Use the Editable Data Grid with a page size of 10")]
    UseEditableGridPaged
  }

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
  public IQuery Query { get; private set; }
  public SQLTraceEventArgs(IQuery query)
  {
    if (query == null) throw new ArgumentNullException("query");
    Query = query;
  }
}

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Sat, 01 Dec 2012 08:40:46 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

  public enum DisplayInGrid
  {
    [Description("Exclude EntityBase Properties")]
    ExcludeEntityBaseProperties,
    [Description("Default Linqpad behaviour")]
    AllProperties,
    [Description("Use the Editable Data Grid included with the driver rather than the LinqPad one")]
    UseEditableGrid,
    [Description("Use the Editable Data Grid with a page size of 10")]
    UseEditableGridPaged
  }

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
  public IQuery Query { get; private set; }
  public SQLTraceEventArgs(IQuery query)
  {
    if (query == null) throw new ArgumentNullException("query");
    Query = query;
  }
}

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: LLBL4linqpad

JezzaT — Wed, 22 Aug 2012 11:21:09 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work I expect

Installation

Binary via LINQPad drivers gallery (currently v2.2)

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

Options

  public enum DisplayInGrid
  {
    [Description("Exclude EntityBase Properties")]
    ExcludeEntityBaseProperties,
    [Description("Default Linqpad behaviour")]
    AllProperties,
    [Description("Use the Editable Data Grid included with the driver rather than the LinqPad one")]
    UseEditableGrid,
    [Description("Use the Editable Data Grid with a page size of 10")]
    UseEditableGridPaged
  }

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
  public IQuery Query { get; private set; }
  public SQLTraceEventArgs(IQuery query)
  {
    if (query == null) throw new ArgumentNullException("query");
    Query = query;
  }
}

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

Updated Wiki: BookSourceCode

JezzaT — Wed, 08 Aug 2012 09:05:18 GMT

There are six versions of the source code:

Original source code that came with the book
Source code updated to LLBL Pro version 2.6
VS2008 branch in the repository (Visual Studio 2008/LLBL v2.6)
VS2010 branch in the repository (Visual Studio 2010/LLBL v3.0)
LLBL Pro v3.1 branch in the repository (Visual Studio 2010/LLBL v3.1)
LLBL Pro v3.5 branch in the repository (Visual Studio 2010/LLBL v3.5)

The repository code is downloadable from the source code tab in a zip file but I recommend using TortoiseSVN to get it, for instance use https://rapiddevbookcode.svn.codeplex.com/svn/LLBL Pro v3.1 to get the LLBL Pro v3.1 branch only.

Solutions files in LLBL Pro v3.1 branch	Contains projects needed for
AW.sln	Joseph Chancellor’s worked example with tests
AW-NoTests.sln	Joseph Chancellor’s worked example
AW.LINQPad.sln	The LINQPad driver and Custom Visualizer with tests
AW.DebugVisualizers.sln	Enumerable Debugger Visualizer
AW.DebugVisualizersWithTests.sln	Enumerable Debugger Visualizer with tests
AW with Everything.sln	Contains all the projects

How to use the book code

Obtain a version of the source code
Install the Adventure Works(2005) DB (if you don't already have it see the related project).
Edit the app.config to point to your Adventure Works DB.
Build AW.sln or AW-NoTests.sln (if using Visual studio you might get errors about solution bindings - ignore them).
Run.
Optionally install the Llblgen Pro demo to modify the entity classes or to see the Llblgen project file

Differences between the current code and the original

Upgrade to LLBLGen Pro 2.6, 3.0, 3.1 and 3.5
Validation has been completely reworked and is now specified using System.ComponentModel.DataAnnotations.
Most of the queries have been moved to a query folder in AW.Data.
Some disabled code has been enabled.
Some refactoring.
Added inheritance to the LLBL project and hence the domain model (VS2010, LLBL Pro v3.1 and LLBL Pro v3.5 Branches).

Additions to the original

LINQ versions of the queries added.
A second order search form has been added which doesn't use any fields from CustomerViewRelated.
A form to edit the employee organization structure using a Databound TreeView control (FrmOrganizationStructure).
A query runner (poor man's version of LINQPad) using the C# Script Engine (AW.Winforms.Helpers - FrmQueryRunner).
A trace window to view the generated SQL (FrmTrace).
Added all the other Adventure Works tables to the domain model(VS2010, LLBL Pro v3.1 and LLBL Pro v3.5 Branches only).

Background

Links
http://www.lulu.com/josephchancellor
http://josephchancellor.wordpress.com
https://tfs.codeplex.com/tfs/services/v1.0/ServerStatus.asmx?op=CheckAuthentication

Thanks to Joseph Chancellor for writing the book and making the code available for this project

Updated Wiki: Documentation

JezzaT — Wed, 08 Aug 2012 08:59:13 GMT

Project Description

The worked example in Joseph Chancellor’s book Rapid C# Windows Development which uses LLBLGen Pro to connect to the Adventure Works sample database.
It also contains an Enumerable Debugger Visualizer, some LINQPad Extensions and Tools and a few Controls.

The book, published in February 2006 about 'Quickly Build Robust, Database-Driven Applications', along with the code is a great introduction into performing common tasks in Database-Driven Applications, however it was written with version 1.X of LLBLGen Pro so I have updated it to work with the later versions (2.6, 3.0 and 3.1). At the same time I wanted to use this code as a starting point for evaluating LINQ To LLBLGen so I have converted all of the queries to use LINQ (but kept the originals for comparison).

Book source code details

Additional controls and tools contained in this project

LINQPad Extensions and Tools

- Custom Visualizer for editing and persisting the results of a LINQ query or any other Enumerable.
- Enumerable DataEditor for editing and persisting the results of a LINQ query or any Enumerable.
- HierarchyEditor for displaying and editing Adjacency List(self referencing) data.
- Static LLBLGen Pro Data Context Driver to show LLBLGen Pro generated entities in the Schema Explorer.
- Entity Data Browser to browse, view and edit LLBLGen Pro entities from a database.

Enumerable Debugger Visualizer.
Object Inspector for browsing the properties of an object and any objects it references.

Controls
- DataTreeView. An enhanced version of a Databound TreeView control.
- GridDataEditor. A paged DataGridView is a user control containing a DataGridView and two BindingNavigator’s, one for the data and one for the pages.
- QueryRunner. A query runner user control (poor man's version of LINQPad).

To do

Finish the employee organization structure editor (FrmOrganizationStructure).
Improve the paging in the LINQPad DataEditor.

Background
Acknowledgements, credits and attributions

Links

http://www.lulu.com/josephchancellor
http://josephchancellor.wordpress.com
http://www.llblgen.com
http://www.linqpad.net

Thanks to Joseph Chancellor for writing the book and making the code available for this project

Updated Wiki: Documentation

JezzaT — Wed, 08 Aug 2012 08:58:17 GMT

Project Description

Additional controls and tools contained in this project

LINQPad Extensions and Tools

- Custom Visualizer for editing and persisting the results of a LINQ query or any other Enumerable.
- Enumerable DataEditor for editing and persisting the results of a LINQ query or any Enumerable.
- HierarchyEditor for displaying and editing Adjacency List(self referencing) data.
- Static LLBLGen Pro Data Context Driver to show LLBLGen Pro generated entities in the Schema Explorer.
- Entity Data Browser to browse, view and edit LLBLGen Pro entities from a database.

Enumerable Debugger Visualizer.
Object Inspector for browsing the properties of an object and any objects it references.
Controls

Controls
- DataTreeView. An enhanced version of a Databound TreeView control.
- GridDataEditor. A paged DataGridView is a user control containing a DataGridView and two BindingNavigator’s, one for the data and one for the pages.
- QueryRunner. A query runner user control (poor man's version of LINQPad).

To do

Finish the employee organization structure editor (FrmOrganizationStructure).
Improve the paging in the LINQPad DataEditor.

Background
Acknowledgements, credits and attributions

Updated Wiki: Documentation

JezzaT — Wed, 08 Aug 2012 08:57:46 GMT

Project Description

Additional controls and tools contained in this project

LINQPad Extensions and Tools

- Custom Visualizer for editing and persisting the results of a LINQ query or any other Enumerable.
- Enumerable DataEditor for editing and persisting the results of a LINQ query or any Enumerable.
- HierarchyEditor for displaying and editing Adjacency List(self referencing) data.
- Static LLBLGen Pro Data Context Driver to show LLBLGen Pro generated entities in the Schema Explorer.
- Entity Data Browser to browse, view and edit LLBLGen Pro entities from a database.

Enumerable Debugger Visualizer.
Object Inspector for browsing the properties of an object and any objects it references.
Controls

- DataTreeView. An enhanced version of a Databound TreeView control.
- GridDataEditor. A paged DataGridView is a user control containing a DataGridView and two BindingNavigator’s, one for the data and one for the pages.
- QueryRunner. A query runner user control (poor man's version of LINQPad).

To do

Finish the employee organization structure editor (FrmOrganizationStructure).
Improve the paging in the LINQPad DataEditor.

Background
Acknowledgements, credits and attributions

Updated Wiki: LLBL4linqpad

JezzaT — Mon, 30 Apr 2012 23:29:42 GMT

LLBLGen Pro Typed Data Context Driver for LINQPad

Even if you are not using Linq you can still use LINQPad to run classic LLBL API or the newer QuerySpec queries by specifying the an IElementCreator rather than an ILinqMetaData type. (v2.x only).

Solutions Design have produced the Official LINQPad driver for LLBLGen Pro v3.5, some of the differences are: it

Has a simpler connection dialog
Doesn't have the schema explorer tooltips mine has nor displays SQL column names
Doesn't fully support SQL execution
Doesn't require changes to the source code to show a SQL trace
SQL trace is not executable
Doesn't support DataAccessAdapter factories
Doesn't support Additional assemblies and namespaces via driver
Is a single Assembly (mine is about 5)
Is more likely to work

Installation

Binary via LINQPad drivers gallery

Run LINQPad
Click 'Add connection'
Click 'View more drivers'
In the 'LINQPad Supplementary Data Context Drivers' page select either:
Download Alternative Driver for LLBLGen 3.5+
Download Alternative Driver for LLBLGen 3.1

Binary from file

Download the LLBLGen Pro version 3.1 and 3.5 Data Context Driver(V2.1), version 3.0 and 3.1 Data Context Driver(V2.0) or version 2.6 Data Context Driver(V1.1)
Do steps 2-4 above
Browse to and select one of: AW.LLBLGenV3.5.DataContextDriverV2.1.lpx, AW.LLBLGenV3.1.DataContextDriverV2.1.lpx,
AW.LLBLGenV3.1.DataContextDriverV2.0.lpx, AW.LLBLGenV3.0.DataContextDriverV2.0.lpx or AW.LLBLGenV2.6.DataContextDriver.lpx

Source

Get the source
Compile AW.LINQPad.sln or 'AW with Everything.sln' (you will probably need to fix the reference to LINQPad.exe)
Run AW.LLBLGen.DataContextDriver\bin\Debug\DevDeploy.bat (or DevDeploy4.bat)
Then in LINQPad:
1. Click add connection
2. Select AW LLBL Driver, click next

Example usage

In the connection dialog put in:

AW.Data.dll (with full path)
AW.Data.Linq.LinqMetaData (type or click choose)
Either AW.Win.exe.config or data source=(local)\sqlexpress;initial catalog=AdventureWorks;integrated security=SSPI

DataAccessAdapter factory

There is an alternative way of creating the adapter and that is to have a static DataAccessAdapter factory method with this signature:

Func<string, IDataAccessAdapter> 
e.g. public static DataAccessAdapterBase CreateDataAccessAdapter(string connectionString)

Default connection properties

Additional assemblies and namespaces

The driver adds these namespaces and assemblies to the ones LINQPad provides

"SD.LLBLGen.Pro.ORMSupportClasses", "SD.LLBLGen.Pro.LinqSupportClasses", "AW.Helper", 
"AW.Helper.LLBL", "AW.Winforms.Helpers.DataEditor", "AW.Winforms.Helpers.LLBL", "AW.LinqPadExtensions", 
"AW.LLBLGen.DataContextDriver", "AW.LLBLGen.DataContextDriver.Static"

"SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll", "SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll",
"AW.Helper.dll", "AW.Helper.LLBL.dll", "System.Windows.Forms.dll","AW.Winforms.Helpers.dll", 
"AW.Winforms.Helpers.LLBL.dll", "AW.LinqPadExtensions.dll"

SQL Translation Tab

public static event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

where SQLTraceEventArgs is a descendent of EventArgs and has a public SD.LLBLGen.Pro.ORMSupportClasses.IQuery property Query. For example:

public class SQLTraceEventArgs : EventArgs
{
  public IQuery Query { get; private set; }
  public SQLTraceEventArgs(IQuery query)
  {
    if (query == null) throw new ArgumentNullException("query");
    Query = query;
  }
}

// __LLBLGENPRO_USER_CODE_REGION_START CustomDataAccessAdapterCode

/// <summary>
/// Event which is raised whenever a query is executed. Use this event to perform SQL tracing. 
/// </summary>
public event EventHandler<SQLTraceEventArgs> SQLTraceEvent;

/// <summary>
/// Called whenever a query is executed.
/// </summary>
/// <param name="query">The query.</param>
protected void OnExecuteQuery(IQuery query)
{
  if (SQLTraceEvent != null) 
    SQLTraceEvent(this, new SQLTraceEventArgs(query));
}

/// <summary>
/// 	Executes the passed in action query and, if not null, runs it inside the passed in transaction.
/// </summary>
/// <param name = "queryToExecute">ActionQuery to execute.</param>
/// <returns>execution result, which is the amount of rows affected (if applicable)</returns>
public override int ExecuteActionQuery(IActionQuery queryToExecute)
{
  OnExecuteQuery(queryToExecute);
  return base.ExecuteActionQuery(queryToExecute);
}

/// <summary>
/// 	Creates a new Select DQ for the fields passed in using the parameters specified.
/// </summary>
/// <param name = "fieldsToFetch">fields to fetch using the select</param>
/// <param name = "persistenceInfoObjects">persistence info objects for the fields</param>
/// <param name = "filter">filter to use for the where clause</param>
/// <param name = "maxNumberOfItemsToReturn">max. amount of rows to return</param>
/// <param name = "sortClauses">sort clause specifications to use</param>
/// <param name = "relationsToWalk">relations to walk to build the FROM clause</param>
/// <param name = "allowDuplicates">flag to specify if duplicates should be returned</param>
/// <param name = "groupByClause">group by clause to embed in the query</param>
/// <param name = "pageNumber">The page number to retrieve</param>
/// <param name = "pageSize">the page size to retrieve</param>
/// <returns>ready to use query to use.</returns>
protected override IRetrievalQuery CreateSelectDQ(IEntityFields2 fieldsToFetch, IFieldPersistenceInfo[] persistenceInfoObjects,
	IPredicateExpression filter, long maxNumberOfItemsToReturn, ISortExpression sortClauses, IRelationCollection relationsToWalk,
	bool allowDuplicates, IGroupByCollection groupByClause, int pageNumber, int pageSize)
{
  var query = base.CreateSelectDQ(fieldsToFetch, persistenceInfoObjects, filter, maxNumberOfItemsToReturn, sortClauses, relationsToWalk,
  allowDuplicates, groupByClause, pageNumber, pageSize);
  OnExecuteQuery(query);
  return query;
}

// __LLBLGENPRO_USER_CODE_REGION_END

Extras

The driver also includes this DataEditor, this HierarchyEditor and this Entity Data Browser., the appropriate assemblies and namespaces are automatically included.

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

var qf = new AW.Data.FactoryClasses.QueryFactory(); 
var q = qf.Address.Where(AddressFields.AddressID == 3); 
var addresses = new AddressCollection(); 
addresses.GetMulti(q); 
addresses.Dump();

LLBL Classic Query API

var soh = new AW.Data.EntityClasses.SalesOrderHeaderEntity (43659);
soh.GetMultiSalesOrderDetails(false).Dump();

Northwind (adapter)

QuerySpec

using (var adapter = this.AdapterToUse) 
{ 
  var qf = new Northwind.DAL.FactoryClasses.QueryFactory(); 
  var q = qf.Customer 
            .From(QueryTarget.InnerJoin(CustomerEntity.Relations.OrderEntityUsingCustomerId) 
                             .InnerJoin(OrderEntity.Relations.OrderDetailEntityUsingOrderId) 
                             .InnerJoin(OrderDetailEntity.Relations.ProductEntityUsingProductId)) 
            .Where(Northwind.DAL.HelperClasses.ProductFields.ProductId == 1);

  adapter.FetchQuery(q).Dump(); 
}

LLBL Classic Query API

var product = new Northwind.DAL.EntityClasses.ProductEntity(10);
this.AdapterToUse.FetchEntityCollection(product.OrderDetails, product.GetRelationInfoOrderDetails()); 
product.OrderDetails.Dump();

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

SD.LLBLGen.Pro.Examples.Authorization.Identity.LoginHelper.Login("cr1","cr1");
var order = new SD.LLBLGen.Pro.Examples.Authorization.EntityClasses.OrdersEntity(10248);
LLBLGenStaticDriver.GetAdapter(this).FetchEntityCollection(order.OrderDetails, order.GetRelationInfoOrderDetails());
order.OrderDetails.Dump();

Note: For IElementCreator LLBLGenStaticDriver.GetAdapter(this) has to be used instead of this.AdapterToUse

RapidDevBookCode Wiki & Documentation Rss Feed

Updated Wiki: LLBL4linqpad

LLBLGen Pro Typed Data Context Driver for LINQPad

Installation

Example usage

Options

DataAccessAdapter factory

Default connection properties

Additional assemblies and namespaces

SQL Translation Tab

Extras

Related links:

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

LLBL Classic Query API

Northwind (adapter)

QuerySpec

LLBL Classic Query API

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

Updated Wiki: EnumerableDebugVisualizer

Installation

Binary

Source code

Note

Lists of other Debugger Visualizers

Similar Debugger Visualizers

Objects that can have debugger visualizers:

Updated Wiki: LLBL4linqpad

LLBLGen Pro Typed Data Context Driver for LINQPad

Installation

Example usage

Options

DataAccessAdapter factory

Default connection properties

Additional assemblies and namespaces

SQL Translation Tab

Extras

Related links:

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

LLBL Classic Query API

Northwind (adapter)

QuerySpec

LLBL Classic Query API

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

Updated Wiki: LLBL4linqpad

LLBLGen Pro Typed Data Context Driver for LINQPad

Installation

Example usage

Options

DataAccessAdapter factory

Default connection properties

Additional assemblies and namespaces

SQL Translation Tab

Extras

Related links:

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

QuerySpec

LLBL Classic Query API

Northwind (adapter)

QuerySpec

LLBL Classic Query API

Authorization example where 'this' is an IElementCreator rather than an ILinqMetaData

Updated Wiki: LLBL4linqpad

LLBLGen Pro Typed Data Context Driver for LINQPad

Installation

Example usage

Options

DataAccessAdapter factory

Default connection properties

Additional assemblies and namespaces

SQL Translation Tab

Related links:

Example Non Linq LLBL queries (Language C# Statement):

AdventureWorks (selfservicing)

LLBL Classic Query API

QuerySpec