CATIDs for Objects That Are Typically Used to Extend Projects
Note
This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
The following table lists CATIDs that are used to extend Project and ProjectItem automation objects for Visual Basic, Visual C#, and Visual C++ projects. These CATIDs are defined in VSLangProj.olb.
Listing of CATIDs
| Name | GUID |
|---|---|
| prjCATIDProject | {610D4614-D0D5-11D2-8599-006097C68E81} |
| prjCATIDProjectItem | {610D4615-D0D5-11D2-8599-006097C68E81} |
Visual Basic CATIDs
The following table lists CATIDs that are used to extend Visual Basic browse objects. They are all defined in VSLangProj.olb.
| Name | GUID |
|---|---|
| prjCATIDVBProjectBrowseObject | {E0FDC879-C32A-4751-A3D3-0B3824BD575F} |
| prjCATIDVBProjectConfigBrowseObject | {67F8DD11-14EB-489b-87F0-F01C52AF3870} |
| prjCATIDVBFileBrowseObject | {EA5BD05D-3C72-40A5-95A0-28A2773311CA} |
| prjCATIDVBFolderBrowseObject | {932DC619-2EAA-4192-B7E6-3D15AD31DF49} |
| prjCATIDVBReferenceBrowseObject | {2289B812-8191-4e81-B7B3-174045AB0CB5} |
Visual C# CATIDs
The following CATIDs can be used to extend Visual C# browse objects. They are all defined in VSLangProj.olb.
| Name | GUID |
|---|---|
| prjCATIDCSharpProjectBrowseObject | {4EF9F003-DE95-4d60-96B0-212979F2A857} |
| prjCATIDCSharpProjectConfigBrowseObject | {A12CE10A-227F-4963-ADB6-3A43388513CA} |
| prjCATIDCSharpFileBrowseObject | {8D58E6AF-ED4E-48B0-8C7B-C74EF0735451} |
| prjCATIDCSharpFolderBrowseObject | {914FE278-054A-45DB-BF9E-5F22484CC84C} |
| prjCATIDCSharpReferenceBrowseObject | {2F0FA3B8-C855-4a4e-95A5-CB45C67D6C27} |
C++ CATIDs
The following Visual C++ project system CATIDs are not exposed in type libraries in Visual Studio .NET 2003 and have to be included in your code whenever you want to extend these project objects. These CATIDs will be included in the type libraries in later releases of Visual Studio.
| Name | GUID |
|---|---|
CVCProjectNode |
{EE8299CB-19B6-4f20-ABEA-E1FD9A33B683} |
CVCFolderNode |
{EE8299CA-19B6-4f20-ABEA-E1FD9A33B683} |
CVCFileNode |
{EE8299C9-19B6-4f20-ABEA-E1FD9A33B683} |
The following code example demonstrates how to program these CATIDs in your code.
const LPOLESTR CVCProjectNode::s_wszCATID = L"{EE8299CB-19B6-4f20-ABEA-E1FD9A33B683}";
const LPOLESTR CVCFolderNode::s_wszCATID = L"{EE8299CA-19B6-4f20-ABEA-E1FD9A33B683}";
const LPOLESTR CVCFileNode::s_wszCATID = L"{EE8299C9-19B6-4f20-ABEA-E1FD9A33B683}";
The following Visual C++ project system CATIDs are also not exposed in the type libraries in Visual Studio .NET 2003 and have to be included in your code whenever you want to extend these project objects. These CATIDs are available only in Visual Studio .NET 2003 and will not be available in the later releases of Visual Studio.
| Name | GUID |
|---|---|
CVCAssemblyReferenceNode : |
{FE8299C9-19B6-4f20-ABEA-E1FD9A33B683} |
CVCProjectReferenceNode |
{593DCFCE-20A7-48e4-ACA1-49ADE9049887} |
CVCActiveXReferenceNode |
{9E8182D3-C60A-44f4-A74B-14C90EF9CACE} |
CVCReferences |
{FE8299CA-19B6-4f20-ABEA-E1FD9A33B683} |
The following code example demonstrates how to program these CATIDs in your code:
const LPOLESTR CVCAssemblyReferenceNode::s_wszCATID = L"{FE8299C9-19B6-4f20-ABEA-E1FD9A33B683}";
const LPOLESTR CVCProjectReferenceNode::s_wszCATID = L"{593DCFCE-20A7-48e4-ACA1-49ADE9049887}";
const LPOLESTR CVCActiveXReferenceNode::s_wszCATID = L"{9E8182D3-C60A-44f4-A74B-14C90EF9CACE}";
const LPOLESTR CVCReferences::s_wszCATID = L"{FE8299CA-19B6-4f20-ABEA-E1FD9A33B683}";
The GUIDs for the Visual C# and Visual Basic project types are shown in the following table.
| Project type | GUID |
|---|---|
| Visual C# | {FAE04EC0-301F-11D3-BF4B-00C04F79EFBC} |
| Visual Basic | {F184B08F-C81C-45F6-A57F-5ABD9991F28F} |
See Also
Adding Project and Project Item Templates
Registering Project and Item Templates