Error with connection string (dll.config) in third party app
Posted: Tue 13 Jun 2017 20:21
Hello!
I wonder if anyone else had this problem. I set up a db first console app project to, hooked up to the oracle db just fine. Everything works perfect, I create ObjectContext objext and update the DB from code no problem.
However if I create a simple class library and pop this dll into another app (Wealth Lab) where I want to access this connection and create an object the same way as I did on a console app I get en error.
"The specified named YZDEVELOPEREntitiesonnection is either not found in the configuration, not intended to be used with the EntityClient provider, or not valid."
I do the same procedures as with the Console App where everything worked perfectly but it crashed if I run this under another app and I think the problem might be somehow with the projectname.dll.config that is somehow ignored by the third party app... Can anyone suggest a workaround or at least a hint on how to debug the matter a litter further? Thank you!
I wonder if anyone else had this problem. I set up a db first console app project to, hooked up to the oracle db just fine. Everything works perfect, I create ObjectContext objext and update the DB from code no problem.
However if I create a simple class library and pop this dll into another app (Wealth Lab) where I want to access this connection and create an object the same way as I did on a console app I get en error.
"The specified named YZDEVELOPEREntitiesonnection is either not found in the configuration, not intended to be used with the EntityClient provider, or not valid."
I do the same procedures as with the Console App where everything worked perfectly but it crashed if I run this under another app and I think the problem might be somehow with the projectname.dll.config that is somehow ignored by the third party app... Can anyone suggest a workaround or at least a hint on how to debug the matter a litter further? Thank you!