title: ASP.NET mvc 4 built in membership creates databases with the wrong schema
body: <p>I'm trying to deploy my application to my host but when I attempt to log in I get the exception:</p>
  
  <p>System.Data.SqlClient.SqlException: Invalid object name 'dbo.UserProfile'.</p>
  
  <p>This worked fine when I did it on localhost.</p>
  
  <p>The reason seems to be that however the asp.net mvc 4 built in membership system creates it's database, it creates them with the schema "Username.databasename" instead of "dbo.databasename" as it did on localhost and it seems to be expecting.</p>
  
  <p>I'm wondering if there is a way to force it to create databases with the correct schema or tell mvc to look for a database with the other schema.</p>
  
  <p>Another possibly relevant detail is that all my other database tables I create with EF code first have the "dbo" schema.</p>
  
  <p>EDIT: All the names I referred to above are table names, the database it creates is called defaultconnection sorry about that.</p>