Catalog name overwriting (SqlServer)

For generated code by llblgen Tool, it can sometimes be necessary to use the generated code with a catalog with a different name than the catalog the project was created with. As LLBLGen Tool generates the catalog name into the code, it might be necessary to specify a way to rename the catalog name in the generated code at runtime with a given name. LLBLGen Pro supports multiple catalogs per project, so you can specify more than one rename definition.LLBLGen Tool offers a way to rename multiple catalogs in one go. The renamed data is stored in static hashtables which assure that the Dynamic Query Engines (DQE) for SqlServer and Sybase ASE use the right catalog names without losing any performance.

To setup the renaming of catalogs, follow these steps.

1: In the configuration tag in the .config file has to be the configSections tag. In there, place a section definition tag as shown in the example below:

ionHandler" />

2: Set New Catalog Name

Note :

For ASP.NET applications, the section declaration has to contain in the type attribute the full type with version and culture, otherwise you'll get an exception at runtime. The specific type declaration is specific for the .NET version you're using and you can find examples how to specify it from the

machine.config file in %WINDIR%\Microsoft.NET\Framework\version \CONFIG.

For example for .NET 1.1, SqlServer specific:

FileSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a

5c561934e089" />