BUG: You receive a "'Microsoft.VisualStudio.VCProjectEngine.VCConfiguration' does not contain a definition for 'Project'" error message when you try to build a project in Visual Studio .NET 2003 (836131)
The information in this article applies to:
- Microsoft Visual Studio .NET (2003), Professional Edition
- Microsoft Visual Studio .NET (2003), Enterprise Architect Edition
- Microsoft Visual Studio .NET (2003), Enterprise Developer Edition
- Microsoft Visual Studio .NET (2003), Academic Edition
SYMPTOMSIn Microsoft Visual Studio .NET 2002, you may create a
project that contains a class that uses the Project property of the
Microsoft.VisualStudio.VCProjectEngine.VCConfiguration class. When you try to
build such a project in Microsoft Visual Studio .NET 2003, you may receive the
following error message: 'Microsoft.VisualStudio.VCProjectEngine.VCConfiguration' does not
contain a definition for 'Project' CAUSEIn Visual Studio .NET 2002, the
Microsoft.VisualStudio.VCProjectEngine.VCConfiguration class contains a
property that is named Project. However, in Visual Studio .NET 2003, the corresponding property
is named the project property (with a lowercase "p"). Therefore, because Visual Studio .NET 2003
does not contain the property that you used in your Visual Studio .NET 2002
project, the behavior that is mentioned in the "Symptoms" section of this
article occurs.RESOLUTIONTo resolve this behavior, in Visual Studio .NET 2003, replace
all occurrences of the incorrectly named Project property with the correctly named project property.STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section of this article.
Modification Type: | Minor | Last Reviewed: | 3/6/2006 |
---|
Keywords: | kbvs2005swept kbvs2005doesnotapply kbpending kbIDEProject kbProperties kbbug KB836131 kbAudDeveloper |
---|
|