title: Adding multiple oracle schemas in visual studio 2013 and EF
body: <p>I have a serious problem that needs to be resolved.</p>
  
  <p>In my server explorer in VS2013, I set up a connection to the database with valid user and password credentials.</p>
  
  <p>So I have a schema called: Connect1, and it needs to have access to another schema called Connect2, both under the same data source name: Dev1. The user I'm connecting with is called Connect1, so by default I'm connected to the schema Connect1. I was able to verify that I have access permissions for this user to connect to Connect2.</p>
  
  <p>Using ODP.NET Managed Driver, I was able to set this up. Putting all the connection details.</p>
  
  <p>Configurations are shown in this page:</p>
  
  <p><a href="http://docs.oracle.com/cd/E11882_01/appdev.112/e10767/building_odt.htm#TDPNG50010" rel="nofollow">Using Oracle Developer Tools for Visual Studio</a></p>
  
  <p>In order to allow the schemas to be viewed, I had to change the Filters tab, and add all the related schemas I'm using (adding Connect2). Then I click update, and I'm able to use the tables into my edmx file.</p>
  
  <p>However, the problem occurs when I close Visual Studios. My filter gets lost, and my connection is back to using only Connect1.</p>
  
  <p>This then destroys my table mapping in my edmx file with a series of</p>
  
  <p>Error 11007: Entity type 'Table1' is not mapped</p>
  
  <p>This is really frustrating as I'd have to keep on repeating the same procedure over and over again manually remapping all my tables.</p>
  
  <p>What's confusing is when I update the data connection from my Server Explorer to include the second schema.. EF works and detects the tables; but my app config and the connection string has not been changed. So this leads me to believe that if I was to promote my project to production or test, that it will break since there's nothing in my project to show that Connect2 is needed.</p>