Hi Wim -
What I do is keep a single catalog name in the LLBLGen Designer, since I use a single database for development.
Then for testing and deployment I use catalog name overwriting using the Connection string. I've found this to be the most flexible for my needs. Because I have different web.configs for each environment, all I need is the correct connection string, and LLBLGen will be pointed to the correct database.
To do this, simply add this to your .config file:
<configSections>
<!--// LLBLGen Catalog Name Overwriting (Live, Test, Dev) // -->
<section name="sqlServerCatalogNameOverwrites" type="System.Configuration.NameValueFileSectionHandler, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
<sqlServerCatalogNameOverwrites>
<!--// LLBLGen Catalog Overwrite (Live, Test, Dev, DevLocal) //-->
<!--// Use ConnectionString for Database Name //-->
<add key="PUT-LLBLGen-DESIGNER-DATABASE-NAME-HERE" value="" />
</sqlServerCatalogNameOverwrites>
Hope this helps!
Ryan