I've never had this one before and I've been using LLBLGen for years. This has me stuck!

Created a new LLBLGen (v2.6) project added the Access Database, created the models and generated the model code.

Blank solution in VS2010 SP1 - added the generated project and build. - OK

Added a new console project to solution and built and ran - OK

To test the generated code - From the console project I added a reference to the model project. Modified the console application code by adding "using Owl.Model", VS2010 intellisense sees the namespace OK.

Try to build the solution and I get the standard "The type or namespace name 'Owl' could not be found (are you missing a using directive or an assembly reference?)"

Answer: No I'm not missing any references!!!

Any thoughts why the model assembly can't be found?

Thanks Mark

Figured it out

I sometimes wish these forums had a "remove post" option so the whole userbase doesn't have to watch me being stupid In my defence - it's been a long day!

Anyway - it's that the Console or any other added project uses the .NET 4 Client profile by default not the full one, which the generated model classes use (need). Setting the other projects to target the full framework solves the issue.

Mark

Take it easy