Hi, I am a former subscriber (from 2007) looking to re-subscribe. I downloaded the trial of the new version and installed. I am having a problem with ES that I think can be easily solved by someone knowledgable.
I previously had entityspaces working against two different databases in a web site and could create and save ES objects associated with each database. In my VS.NET solution, the ES objects are defined as seperate projects, say, ProjectForDatabase1 and ProjectforDatabase2. The Web site references both of those projects.
I can now only make one set of ES data objects work at a time -- that "one" being the single database defined in the <connections> section of web.config for my web site, e.g.
<connectionInfo default="SQL">
<connections>
<add name="SQL" providerMetadataKey="esDefault" sqlAccessType="DynamicSQL" provider="EntitySpaces.SqlClientProvider" providerClass="DataProvider" connectionString="Data Source=servername;Initial Catalog=database1;UID=whatever;PWD=whatever;" databaseVersion="2005"/>
</connections>
</connectionInfo>
</EntitySpaces>
If I change the database name from database1 to database 2 then I can use the second set of objects associated with database 2. If I try to call objects from database 2 while database 1 is defined in webconfig as above, I get errors to the effect of "Invalid object name 'MyTableObject'.
I know there are explicit ways of defining connections in code. I don't want to do this if possible -- this worked fine previously. Somehow I messed something up trying to upgrade. A few possibilities:
- There's a limit in the trial I don't know about
- I somehow swapped from Loader to LoaderMT
- There's something I can say in my web.config for my web site that will fix this that I don't know about
- Somehow I am not referencing the things I'm supposed to be referencing.
?
Obviously this is a show-stopper for my work and deployment. It would be great if someone could help resolve this: it's the only sticking point for renewing my sub and upgrading my version of ES.
Thanks,
-KF