Is there a LINQPad equivalent to a DataContext class?
As it was mentioned before, you don't need to create a DataContext as LINQPad creates one by default.
But just in case, you need a second DataContext (for the same database) you could use
var secondDataContext = new UserQuery();
This will create a second datacontext just like the automatically created one.
I know this already has an answer and I agree with Lucas but wanted to add a couple of things that might help readers of this question.
You can load your own DataContext from the assembly if you want to. Regardless of whether you load your own Context or let LinqPad build one for you, you are running in the Context of a "UserQuery" class that is generated by LinqPad.
The following C# statment shows this:
this.GetType().Name.Dump(); // Shows UserQuery
This UserQuery class derives from a DataContext. In the this example I let Linqpad build a datacontext for the AdventureWorks database:
this.GetType().BaseType.Dump(); // Shows TypedDataContext
If I load my own DataContext called MyDataContext:
this.GetType().BaseType.Dump(); // Shows MyDataContext
Short answer: You do not need to create the DataContext yourself. LINQPad comes with lots of samples, take a look at them.
When you connect LINQPad to a database, it creates the DataContext for you. The DataContext's tables (Table<T>
) and SubmitChanges()
are available as local members.
For example, LINQPad's default "C# Expression" mode you can just write:
from p in Person
where p.Name == "Joe"
select p.Address
In LINQPad's "C# Statement" mode:
var query = from p in Person
where p.Name == "Joe"
select p.Address;
query.Dump(); // Dump() shows results below
Person joe = query.First();
joe.Name = "Peter";
SubmitChanges();
joe.Dump(); // shows joe's values under the previous query results
LINQPad's Dump()
extension method is very useful can be called on any object or collection (in LINQPad's statement mode) to show the results below.
Note that you don't even need to connect to a database to use LINQPad. You can work with in-memory collections:
int[] numbers = new[] { 1, 2, 3, 4, 5 };
numbers.Where(n => n > 3).Select(n => n * 2).Dump();
In fact, you don't even need to use LINQ to use LINQPad. It also works great as a snippet compiler.
Building on the reply from jaraics, I found that the UserQuery constructor requires a connection string. At least it does for LINQPad version 4.37.11. Therefore, I retrieved the connection string from the UserQuery instance created by LINQPad and used that to create my own instance.
var connectionString = this.Connection.ConnectionString;
var secondDataContext = new UserQuery(connectionString);
When I used the above code, it gave me a second DataContext.