I'm working on my first LLBLGen project that will be included into at VS 2010 WCF solution. I added the reference to the project to my web service. Then I tried to add the import statements to service and I'm able to do that but when I build the service. I get warning and error messages dealing with anything LLBLGen. The warning messages are telling me that the DLLs are not found. With that being said, I get a error message saying my object collection class is not available. Is there anything special I have to do to use the LLBLGen project?

For example: Imports NESL.Data.EntityClasses Imports NESL.Data.CollectionClasses

Thank you.

Please post exact compilation error texts. And the llblgen pro runtime library version (check the forum guidelines thread for more details).

Here is a screen shot of my errors within Visual Studio. The runtime library is v3.1.

Does the service reference the generated code project and the ORMSupportClasses?

Yes I added the reference to the project in the web service.

That's odd, but surely you are missing something, I don't know what but please double check the following:

• You are generating code for the appropriate .net version at LLBLGen version.
• The generated projects compile
• You are referencing the correct LLBLGen libraries. As far as I can see you are doing that but it might be that you are not doing that in the generated projects, just check that.
• Something there is an error that is the cause of all other ones. Try to find it on the errors list.
• Does it compile if the project is a console application?

I tried that and I got the same results. I did see something while looking at all the warning messages. I got these same messages in every solution I add the LLBLGen project. Maybe I didn't do something correctly while creating the new project within LLBLGen.

I noticed something else in "Configure the code generation process" screen. I had my template group set to self servicing. Should I have that set to Adapter? The reason I'm asking that is because the information under the selection reads " Template group which is focused on having persistence logic as a service." It was just a thought.

I think I found out why I was getting all these warning messages. I found that my target framework in my service was .NET Framework 4 Client Profile. I changed it to be .NET Framework 4 everything is working now.

yes, v3.1 isn't client profile compliant, v3.5 is though.