ASP.NET Schema Tables Causing Issues in VSTS

Question

After installing the VSTS Database GDR and importing a SQL Server 2005 database that includes the ASP.NET provider schema tables, I get the following warnings:

TSD04151: Procedure: [dbo].[aspnet_Users_DeleteUser] has an unresolved reference to object [dbo].[sysobjects].[name].

TSD04151: Procedure: [dbo].[aspnet_Users_DeleteUser] has an unresolved reference to object [dbo].[sysobjects].

TSD04151: Procedure: [dbo].[aspnet_AnyDataInTables] has an unresolved reference to object [dbo].[sysobjects].[type].

TSD04151: Procedure: [dbo].[aspnet_Users_DeleteUser] has an unresolved reference to object [dbo].[sysobjects].[type].

TSD04151: Procedure: [dbo].[aspnet_AnyDataInTables] has an unresolved reference to object [dbo].[sysobjects].

TSD04151: Procedure: [dbo].[aspnet_AnyDataInTables] has an unresolved reference to object [dbo].[sysobjects].[name].

Does anyone know how to get rid of these warnings?

Euro Micelli · Accepted Answer · 2009-07-10 17:49:44Z

18

I'm not sure, but a quick look seems to reveal the following. The offending line in the script seems to be:

Line 42 in procedure [dbo].[aspnet_Users_DeleteUser] ~~(how do you do underscores here?)~~ (like this: \_ )

(EXISTS (SELECT name FROM sysobjects WHERE (name = N'vw_aspnet_MembershipUsers') AND (type = 'V'))))

the system view sysobjects belongs to the built in system schema 'sys' which is not included in the database project. As a result the database project parser thinks (wrongly) that the reference is unresolved.

I don't think there is anything you can do but select to ignore the warning from the project settings. (Be aware that that will hide real errors from you as well.) I would probably just ignore the warnings.

Update: Try to add a reference to:

C:\Program Files\Microsoft Visual Studio 9.0\VSTSDB\Extensions\SqlServer\2008\DBSchemas\master.dbschema

edited Jul 10, 2009 at 17:49

Euro Micelli

34.2k8 gold badges54 silver badges75 bronze badges

answered Dec 18, 2008 at 14:37

Kim Major

3,7511 gold badge25 silver badges20 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Chad Green Over a year ago

Adding the reference did the trick. One thing to note, since I'm targeting a SQL 2005 database, I referenced the following: C:\Program Files\Microsoft Visual Studio 9.0\VSTSDB\Extensions\SqlServer\2005\DBSchemas\master.dbschema

Wiebe Tijsma Over a year ago

Thanks! It also works for VS2010 and SQL2008. The right folder there is (for x64 systems): C:\Program Files (x86)\Microsoft Visual Studio 10.0\VSTSDB\Extensions\SqlServer\2008

bloparod Over a year ago

What kind of reference should I add for this file? The only one that I could add is to an XSD file, without effect (no reference was added to database project). Thanks!

bloparod Over a year ago

Ignore my question, it was a Database reference =D.

Chad Green · Accepted Answer · 2009-01-27 18:30:14Z

3

Kim's answer above works perfectly for the situation I asked for. But, I also found out that you can filter the build warnings per file. Look at http://blogs.msdn.com/gertd/archive/2009/01/11/file-level-build-warning-suppression-in-the-gdr.aspx

answered Jan 27, 2009 at 18:30

Chad Green

4874 silver badges16 bronze badges

1 Comment

Jonathan Wood Over a year ago

Yes, but this is a helpful warning. Suppressing it is not an ideal solution.

Collectives™ on Stack Overflow

ASP.NET Schema Tables Causing Issues in VSTS

2 Answers 2

4 Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related