LinqPad is proving to be a very useful tool for learning LINQ and also proofing a LINQ query before using it in code.

I was wondering if anyone has tried (or knows how) to add support for LLBL's Linq provider to LinqPad?

At the moment we don't think it will be an easy thing to do, as the LinqToLLBLGenPro code needs to be generated by LLBLGen before it can be used.

It may be worth contacting the maintainer of LinqPad to see what he thinks ?

Matt

omar wrote:

LinqPad is proving to be a very useful tool for learning LINQ and also proofing a LINQ query before using it in code.

I was wondering if anyone has tried (or knows how) to add support for LLBL's Linq provider to LinqPad?

I started a similar project a while ago. Due to time restrictions it is in a half-done state http://cs.rthand.com/blogs/blog_with_righthand/archive/2008/10/20/Providing-syntax-editor-within-a-.net-application.aspx If there is enough interest I might consider finishing it.

Looks very promising. Count me in as an early tester

I've started using LINQPad with LLBL; works well though I had to jump through a few hoops, see this thread that I assume you started Omar: http://forums.oreilly.com/content/C-3-0-in-a-Nutshell/996/Linqpad-Support-For-Llbl/

Of course LINQPad is handy for a lot of more than just LINQ.

It's a pity mihies 'Righthand's LLBLGenPro Query Studio' never got released.

Thanks for the update.

Matt

Wow..that was a pain, BUT I finally have it WORKING complete with intellisense. Very, very cool...

TomDog wrote:

I've started using LINQPad with LLBL; works well though I had to jump through a few hoops, see this thread that I assume you started Omar: http://forums.oreilly.com/content/C-3-0-in-a-Nutshell/996/Linqpad-Support-For-Llbl/

Of course LINQPad is handy for a lot of more than just LINQ.

It's a pity mihies 'Righthand's LLBLGenPro Query Studio' never got released.

Yep, time is not on my side lately nor is public interest. It isn't scratched though.

mihies wrote:

Yep, time is not on my side lately nor is public interest. It isn't scratched though.

Strange the lack of interest, I find LINQPad really handy, so much so I've created a LINQPad DataEditor and thanks to this new enhancement: LINQPad Data Context Extensibility Model there will be first-class support in LINQPad for LLBL as soon as someone writes a driver. Which I might have a go at... unless someone else is already going to - Frans???

It's on my list to do this month, but v3 stuff has top priority at the moment so it's left for spare time coding. It shouldn't be too hard to fill in the blanks, I already had some discussions with Joe about this.

If you have some spare time and want to have a go at it, by all means do , though don't feel obligated to do this in any way, we'll get to it as soon as time permits.

If you need info from me, please let me know either in this thread or through email to support AT llblgen DOT com.

I have found Linqer (http://www.sqltolinq.com/) extremely useful. It converts my SQL queries into LinqToSQL or LinqToEntitites (depending on my choice of data link mapping files I generate from VS.NET).

Imagine writing your SQL query and then asking Linqer (or some other software) to covert it to LinqToLLBL. Now thats a true time saver.

This is something I am currently experiencing first-hand in the current project. Writing complex LINQ queries is a breeze as I write my SQL queries and convert them to LinqToSQL and they would mostly work with no change for LinqToLLBL.

Good tip! Never heard of the tool but it seems useful

Otis wrote:

It's on my list to do this month, but v3 stuff has top priority at the moment so it's left for spare time coding. If you have some spare time and want to have a go at it, by all means do , though don't feel obligated to do this in any way, we'll get to it as soon as time permits.

Good to here it’s on its way I’m not back at work from my Christmas break till the 11th so I guess I can wait till then. Having said that I have made a small start on a static LLBL Data Context Driver if anyone wants to try it out. It populates the tree with what I want – though crashes LINQPad when using one of the context menu’s. If I spend anytime coding I might put my efforts into making my DataEditor pageable instead.

I saw Linqer but our LLBL project mappings are to different from what it would generate for it to be much use I think, Shame, though I think in LINQ now there are others in my team who still think SQL first so might find it handy.

Anyway Merry Xmas all.

Otis wrote:

It's on my list to do this month, but v3 stuff has top priority at the moment so it's left for spare time coding. It shouldn't be too hard to fill in the blanks, I already had some discussions with Joe about this.

If you have some spare time and want to have a go at it, by all means do , though don't feel obligated to do this in any way, we'll get to it as soon as time permits.

I take it time hasn't been permitting for you but it has for me - I've just released Version 1.0 of a Static LLBLGen Pro Data Context Driver for LINQPad. Give it a whirl.

Awesome!! I'll give it a try first thing on monday! great work!

Just a quick question here - do you still get the sql output for the query - as Linqpad usually does?

My current practice is to create a Linqpad.config file that turns on llblgen tracing, and then I set the connection information in the code block itself. Then I can test out my llblgen queries using the adapter I just created.

But this method sounds way better.

JRR wrote:

Just a quick question here - do you still get the sql output for the query - as Linqpad usually does?

Just to answer my own question, you have to turn tracing on in your .config file specified to linqpad in order to see the sql generated by your linq query.

The llblgen trace sql will appear in the output pane, and there is no sql in the specific 'sql' pane.

(unless I missed something, that is)

Great work nonetheless!

I tried it with adapter, but I keep getting the No DataAccessAdapter instance set on LLBLGenProProvider2 instance. Can't execute query error. The 'browse' on the dataaccessadapter assembly in the connection dialog says 'no public types found' error. I tried with v2.x and v3.0 assemblies. I think I miss a setting, e.g. where to specify the ormsupportclasses/linq assembly ref.

When I use selfservicing, I get 'connection string not initialized'... I feel like an uber n00b

Otis wrote:

I tried it with adapter, but I keep getting the No DataAccessAdapter instance set on LLBLGenProProvider2 instance. Can't execute query error. The 'browse' on the dataaccessadapter assembly in the connection dialog says 'no public types found' error. I tried with v2.x and v3.0 assemblies. I think I miss a setting, e.g. where to specify the ormsupportclasses/linq assembly ref.

When I use selfservicing, I get 'connection string not initialized'... I feel like an uber n00b

Ha- shoe is on the other foot Bummer looks like I will need to test it on more machines - I did find a lot of intermittant failure with assembly references.

I got the 'public types found' error on one or two occasions - then it went away without me doing very much at all.

Things to try: Try it with both LINQPad 2 and 4 - sometimes that was enough to sort things out. If that doesn't work you'll have to use the source and run AW.LLBLGen.DataContextDriver.csproj with C:\Program Files\LINQPad\LINQPad.exe(or whereever) as a start action.

The 2.6 assemblies are included in the driver.

Otis wrote:

I tried it with adapter, but I keep getting the No DataAccessAdapter instance set on LLBLGenProProvider2 instance. Can't execute query error. The 'browse' on the dataaccessadapter assembly in the connection dialog says 'no public types found' error. When I use selfservicing, I get 'connection string not initialized'.

Ok I think I've fixed those problems in version 1.0.0.3 of my Static LLBLGen Pro Data Context Drivers for LINQPad - now there is a driver for version 3.0 as well as v2.6.

Awesome! We're in the final stages of pushing for RTM, so it will be next week till we have time to look at it, but nevertheless great work

Im new to linq pad, but i added the LLBL driver and I can see the results when executing a linq expression, but how do i see the sql generated from behind the scenes?

Hi Marco,

I was able to get that working by turning on the LLBLGen DQE tracing in the app.config file linqpad uses.

Hmm, I just tried adding the config section to linqpad.exe.config but no luck. can you paste in what you are specifying?

Here's what worked for me:

1) Set app.config on the "Query Properties" form:

Then, just make sure your app.config file includes the diagnostic switch like this:

<?xml version="1.0"?>
<configuration>
    <appSettings>
        <add key="DBConn" value="data source=(local)\sqlexpress;initial catalog=xx;integrated security=SSPI;persist security info=False;packet size=4096"/>
    </appSettings>
    <system.diagnostics>
    <switches>
        <add name="SqlServerDQE" value="4" />
    </switches>
</system.diagnostics>
</configuration>

Now you should get the trace output above the actual query resuts. The sql does not show up in the sql tab, but if you are ok with that, this should do the trick.