question about meta.Catalog in the generated classes

Hi,

I am using EntitySpaces for a project I am working on.  I have a Test database and a production database.  Both are on the same server.  In order to switch enviornments, I would like to be able to just change the web.config.  However, when I do this, the generated classes throw exceptions because of the meta.Catalog property which is set to the wrong database name (Whichever one I used to generate). How can I get around this?

Thanks,

Joe

Hi. It's Joe again.

I commented out meta.Catalog in all the generated classes, and it seems to be fine. Is this recommened or not? Or is there a better way?

Thanks,

Joe

Any manual changes you make to generated code will, of course, get wiped out with the next regen. On the Advanced tab there are a couple of CheckBoxes to Ignore Schema and Catalog that should accomplish what you want during generation.

Suh-weet. Thank you.

I think, it will be better to have "Metadata Class Should Ignore Catalog." ticked by default. It will allow to control Catalog name from config file, which is usually preferred option instead of hard-coded.