Hello!

Heres a new topic - structure of the solutions and generated code projects...

We have been following the microsoft recommendations for building solutions and working with sourcesafe, these are really good recommendations:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/tdlg_app.asp

The question is - how to fit LLBLGen projects into here. Because of the complexities of our system, we have to support 2 databases, so using the adaptor model we generate 3 projects: 1) The generic project with the entities 2) The Oracle DB Specific project 3) The SQL Server DB specific project

These are then 3 projects within the solution that contains all other assemblies.

Is this how others are working? Are people treating the gen'd code as external projects/asemblies?

Is this how others are working? Are people treating the gen'd code as external projects/asemblies?

I'm doing what you're doing, but I only need to support one database. So I have two projects, which I build with all my other projects.

Jeremy

MattWoberts wrote:

Is this how others are working? Are people treating the gen'd code as external projects/asemblies?

Hello. Well, maybe I am no the best person in talking about this, because I have not yet began to implement my first application with LLBLGEN. In any case, I am going to say what I think, how I am going to do the things the first time.

First I think that I am going to make my projects in incremental steps. I will have to generate the project several times, and I will have to substitute many classes. I don´t think it well be a good idea to check out, and check in all this classes. And because I don`t really want to work inside the generated code, I only need the compiled dlls. I am going to put only in source control the compiled dlls and even the llblegen project. That's all I will need.

Juanma :

I decided to generate the LLBL into an external DLL. Made it easier for source control and sharing - just post the dll on the server. Also I build the DLL using a command line script. Let me know if you want me to post it (I got most of it from Frans).

Tips:

1. Make sure to set all your satellite assemblies to Copy Local = False for their references to LLBL
2. Store the LLBLGen project (*.lgp) and the current runtimes/templates in source control and nothing else...maybe the build script.
3. Don't add the LLBL source files/project into your VS solution unless you have a small project. It slows up your project loads/compiles/etc and really gums up source control

Jeff...

jeffreygg wrote:

I build the DLL using a command line script. Let me know if you want me to post it (I got most of it from Frans).

Yes, please.

Juanma