Multiple Datasources

Found the solution - as I should have guessed not an Ideablade issue. Seems one has to add a raft of Entityframework options to the configuration file.

Right....well it does not work unfortunately.

{"Key 'ForecastEntities': The model's metadata artifact files (csdl, msl, ssdl) are either invalid or could not be found, either as resources in an assembly or loose in the output directory. Perhaps you have multiple assemblies containing the same metadata. Check the connection string for key 'ForecastEntities', which says the artifact filenames are Forecast.csdl, Forecast.ssdl, and Forecast.msl. Do these names match the actual artifact filenames? All three root names (e.g., 'Forecast') should be the same and match the edmx filename unless you changed them deliberately."}

In the edmx designer I have changed EntityManagerName to 'MyEntities' and left the rest as ForecastEntities (DatasourceKey and EntityContainerName).

Any ideas?

I think I might have confused you there. Yes I shall maintain two models, the DataSourceKeyName for the SQL datasource is set in the designer and that takes care of that. However for the POCO entities I now need to set a DataSourceKeyName for those in order to differentiate them from the SQL entities. So my question is whether I can set the DataSourceKeyName on the POCO base class and thus not have to go through each POCO entity and copy paste it.

Ok... my poco entities have a base class 'public abstract class BaseClass : IKnownType, IHasPocoEntityAspect, INotifyPropertyChanged'

If I put the attribute [IbEm.DataSourceKeyName(@"HistorianPOCOEntities")] on that I will not need to go through and assign it to each individual derived poco entity?

Hi Denis

I did read that, but I must be missing some details. Here is were I am confused. I have followed the POCO guide to obtain data from a Historian (this uses a custom API hence the need for custom POCO classes and providers). I followed (http://drc.ideablade.com/devforce-2012/bin/view/Documentation/poco-service-provider-class) in order to create the 'Provider' (lets call it MyProvider) and associated EntityManager (lets call it MyEntityManager).

So now I have MyProivider that contains very specific methods to get data out of the Historian via its API. Within my client application I am using MyEntityManager to gain access to those entities.

Now I want to access data from a SQL Server, in my client application I do not want to have another EntityManager, I want to stick with MyEntityManager and have it sort out where the datasource is. At this point nothing has been auto generated - I have had to type in every line myself.

So... I don't know what my first step is now. Do I mark all the existing classes with 'IbEm.DataSourceKeyName(@"Historian")]' first and see whether everything still works before attempting to add the SQL connection?

After that then what? If I create a new 'ADO.NET Entity Data Model' will it add everything to the existing MyEntityManager and MyProvider? Is it as simple as that?

Perhaps I should just give it a go and see what happens, but I thought it best to check first.

Thanks

Hi

I have a custom POCO EntityManager and associated provider for accessing a third party non-sql datasource. This works well, now I wish to add to this EntityManager the ability to access tables from an unrelated SQL Server database (hence a totally different datasource that now can use normal ORM tools)... how do I go about doing this? Are there any articles? Do I have to create a new EntityManager and use both through my application now?

Thanks
Mark