http://www.screencast.com/users/chris.m/folders/Jing/media/b9b14a20-88fd-433a-b026-570da3c897ed

Let your references like you did at the beginning of the screen cast. You just need to add this line on your file:

using AppBreeder.Linq;

As you can see, the LinqMetaData resides on the generated code of your project, not in the genral assemblies of LLBLGenPro.

You are very close. Don't frustrate yourself. It's just a "using" clause.

It's also in the docs that LinqMetaData is in the generated code: http://www.llblgen.com/documentation/2.6/hh_goto.htm#Using%20the%20generated%20code/Linq/gencode_linq_gettingstarted.htm%23Preface

and the sourcecode provided with the installation contains a lot of our unittests, which should have given you a good start. Sorry for the confusion and the frustrating moments. I hope you now will record a video with less frustrating comments

Please understand that we aren't perfect and your comments showed that the docs miss an important note, we'll add that to the docs so the imports/using statements are not overlooked by new users.

What I wonder though is: didn't vs.net suggest you to add the using statement using a smarttag? It should have, which is also why we didn't add the remark about the using statement in the first place, it's suggested by vs.net

Hi Guys, Thanks for the help! That is working now.

Don't get me wrong...LLBLGen is allowing me to produce a much better system than I would be able to otherwise.

In fact, I am almost a one-man-army with LLBLGen! - producing better code that most of the coders I hire.

LLBLGEN is also allowing me to feel assured that the 'Core' of my system is consitent & free of any one developers aproach to design.

LLBLGen empowers someone with less developer experienced, like myself - to get further into the development process.

My only comment would be that your documentation tends to be very specific, very early which may be helpfull for devs, but is less helpfull for my level(system level). Perhaps you could consider a few more 'overview', 'getting started' pages in future releases. (Or those Video Walkthroughs are fast & easy with JingProject.com )

Your promt responces on the support forums - allways fix the problems.

Thanks again. CM

(By the way - VS just suggests 'Missing ORM NET3.5 dll' - which just causes collitions with ORM NET2.0 dll - looping)

cmprogrock wrote:

Hi Guys, Thanks for the help! That is working now. Don't get me wrong...LLBLGen is allowing me to produce a much better system than I would be able to otherwise. In fact, I am almost a one-man-army with LLBLGen! - producing better code that most of the coders I hire. LLBLGEN is also allowing me to feel assured that the 'Core' of my system is consitent & free of any one developers aproach to design. LLBLGen empowers someone with less developer experienced, like myself - to get further into the development process.

That's more like it

My only comment would be that your documentation tends to be very specific, very early which may be helpfull for devs, but is less helpfull for my level(system level). Perhaps you could consider a few more 'overview', 'getting started' pages in future releases. (Or those Video Walkthroughs are fast & easy with JingProject.com ) Your promt responces on the support forums - allways fix the problems. Thanks again. CM

Documentation is always a gamble: if the docs don't fit what the reader expects to find (e.g. the format is too verbose, too detailed etc.) it won't work.

I'd suggest you look at the examples we have on our website to get started and for linq at the unittests we ship with the installer so you can get an idea how to do various things with the linq provider.