Hi,

We are using Adapter Version 2.6. We use llbl to generate our business manager classes.

We are a small shop. We have a development Data Base but our llbl generation points to our production data base. So far (last 6 years) we have not had an issue with this and it has made our testing and deployment easy.

So, what's the best practice on using our development data base as the bases for the llbl generation?

Do we have to have a complete development environment including separate llbl solutions (which contain dbgeneric, dbspecific and our generated/custom business manager projects) for both development and production data bases?

Do we need separate production and development solutions for our other programs?

How is all this coordinated when we need to make a bug fix to our production program?

Thanks for any guidance on this.

Dave

Hi Dave,

This is more like an architectural decision. At the end of the day LLBLGen generated code is just another piece of code in your entire code base.

You have a production server, with your DB and your production assemblies. Then you have a working copy or various forks where you apply bug-fixes, enhancements, etc., eventually you will have a development or testing server (db and code base) where you release your betas. When the code is ready, you pass those bits to the production server.

For the generated code it just take to change your connection string so the code points to your production server instead of the dev one.

Thanks David, I appreciate your take on this.