Article ID: 818452 - Last Review: May 12, 2007 - Revision: 2.2 BUG: The project dependencies in your Enterprise Template project are not saved in Visual Studio .NET 2003
On This PageSYMPTOMSIf you add project dependencies to an Enterprise Template
project by using Microsoft Visual Studio 2003, the project dependencies are not
saved when you close and then reopen the Enterprise Template
project. CAUSEThis problem occurs because the dependency information does
not persist correctly for Enterprise Template subprojects when you close and
then reopen the Enterprise Template project in Visual Studio .NET
2003. WORKAROUNDTo work around this problem, use a project
reference. If you create a project that depends on the file output of another project, and you want to set project dependencies to influence the build order of the projects, you can use a project reference. A project reference performs the following functions:
Add a project reference
STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed in the "Applies to"
section. Steps to reproduce the problem
REFERENCESFor more information, visit the following Microsoft
Developer Network (MSDN) Web sites: Enterprise Template
projects http://msdn2.microsoft.com/en-us/library/aa291957(VS.71).aspx (http://msdn2.microsoft.com/en-us/library/aa291957(VS.71).aspx) Project Dependencies, Common Properties, Solution Property Pages dialog box http://msdn2.microsoft.com/en-us/library/zk4ahe0t(vs.71).aspx (http://msdn2.microsoft.com/en-us/library/zk4ahe0t(vs.71).aspx) Project Dependencies dialog box http://msdn2.microsoft.com/en-us/library/cb8t5a6t(vs.71).aspx (http://msdn2.microsoft.com/en-us/library/cb8t5a6t(vs.71).aspx) | Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
