Hi!
Ihave project with imported schema, but on open project I give follow MessageBox:
---------------------------
Microsoft Visual Studio
---------------------------
Exception of type 'Microsoft.VisualStudio.TeamSystem.Data.Schema.InvalidIdentifierCriteriaException' was thrown.
---------------------------
OK
---------------------------
And after this message Project marked as unavailable.
Project - SQL 2000 Project
Database - SQL 2000

Reopen existing schema project
guzarva16
Thanks for looking into this :) I am having the exact same issue. SQL 2000 project, import the schema (which works great by the way).
Save the project and close the solution. Re-open the solution and the database project can no longer be opened. On opening I get a pop-up error message of "Object reference not set to an instance of an object" and the database project is disabled. No matter how I try to re-open it, I get the same error.
Lorna
ThackerRobin
It sounds like you may have stumbled across a product bug. Can you provide us more details about the schema you imported, whether you did any work with the database project after importing but before saving the project, and any other details you can recall
If you'd prefer to submit a bug report via Connect, here are the instructions:
The advantage of the Connect site is that other customers can search for similar issues if they encounter a problem, and it's a little easier to track what happens to the issue. But we'll work with you in either case :).
The more information you can provide, the easier it will be for us to track down and resolve the issue for our next CTP.
thanks,
Steven
Craig Laurin
Thank you for answer!
I already posted feedback in connect http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx FeedbackID=139819
I have installed SQL Server 2000 SP4, Windows Server 2003, VSTS. Also I have SQL 2005 SP1, SQLExpress (without SP1)
I may imported any schema with same results - project no more loaded.
I simple created Database Project SQL 2000, after imported schema from any databases, close solution and on opening get Message Box with information about exception.
Steve R
Agos,
Thanks again for the feedback - we'll take a look at the problem in the product team. Please, let us know if you come across other issues or have suggestions.
Best Regards,