Visual Studio 2010 Database Project does not understand Schema Names anymore?

Posted by Xenan on Stack Overflow See other posts from Stack Overflow or by Xenan
Published on 2010-04-23T14:12:31Z Indexed on 2010/04/23 14:13 UTC
Read the original article Hit count: 197

I just tried to upgrade a Visual Studio 2008 Database project to VS2010 and actually it is quite a mess. Hundreds of warnings, all unsolved references. It seems to boil down to Visual Studio not to understand Schema Names (aka Ownership) anymore. For example, the standard dbo schema:

[$(MyDataBase)].dbo.MyTable

is fine but:

[$(MyDataBase)].myschema.MyTable

gives an unsolved reference. It did work in VS2008.

Also the abbreviation for dbo, the double dot:

[$(MyDataBase)]..MyTable

Doesn't work anymore.

In the project property windows I restored the references to the correct servers (which were lost after the conversion) but that didn't help.

This seems pretty basic but I don't have a clue how to solve this. Any help is appreciated.

© Stack Overflow or respective owner

Related posts about VS2010

Related posts about database-project