Visual Studio 2010 Database Project no longer understands schema names?
I just tried to upgrade my Visual Studio 2008 database project to VS2010 and it is actually quite a mess. Hundreds of warnings, all unresolved links. It looks like Visual Studio doesn't understand Schema names (aka Ownership). For example, the default dbo schema is:
[$(MyDataBase)].dbo.MyTable
great, but:
[$(MyDataBase)].myschema.MyTable
gives an unresolved link. He worked in VS2008.
Also an abbreviation for dbo, double dot:
[$(MyDataBase)]..MyTable
does not work any more.
In the project properties window, I restored the links to the correct servers (which were lost after the conversion), but that didn't help.
It seems pretty simple, but I don't know how to solve it. Any help is appreciated.
a source to share
There were the same major changes between the 2008 and 2010 version of the database design on a structural perspective in a solution, for example. The Schemas folder contains subfolders for each schema, including dbo.
Updating the solution makes a terrible mess of the solution, maybe SP1 will fix this issue.
I suggest creating a new DB project and using Schema Compare to add the existing structure to the project.
a source to share