I dont quite get why the database name is hardcoded (Sql server)? e.g. dnname.dbo.table

This caused me a problem as I use this solution on a shared server. We have a live site and a test site on there. We load to test before going live. As the SQL servers are on the same machine we have to call them something different. Therefore this doesnt work with LLBL as the database name has to be the same as in the solution.

Is there any way of achieving this now (without having to make 2 copeis of the database offline and 2 copies of the LLBL solution)? If not would you consider making the database name a configurable variable in the future?

Thanks

John wrote:

I dont quite get why the database name is hardcoded (Sql server)? e.g. dnname.dbo.table

This caused me a problem as I use this solution on a shared server. We have a live site and a test site on there. We load to test before going live. As the SQL servers are on the same machine we have to call them something different. Therefore this doesnt work with LLBL as the database name has to be the same as in the solution.

Is there any way of achieving this now (without having to make 2 copeis of the database offline and 2 copies of the LLBL solution)? If not would you consider making the database name a configurable variable in the future?

Thanks

See the documentation at Using the generated code->Application configuration through .config files

Jeff...

To elaborate why the name is in the persistence info: if you have 2 catalogs in your project, the name is required.