Hi,

We are developing a new project type for VisualStudio 2003 in c#.
The main part seems to be working, but there are some small, but annoying
thinks that are not working well. These problems are:
- The Build/ReBuild context menu command is not handled automatically.
- The project properties window cannot display cunfiguration-dependent
property pages.
- The information about the selected node in the project is not visible in
the "properties" window.

My hope is that all of these problems based on some stupid bug in our
implementation, so I have targetted now this last problem, with the
properties window. I have created a simplified version of the project by
cutting off all the irrelevant things (I can send you it over e-mail if it
makes sense.). Now the project uses the following comonents:
- an abstract base node class, implements IVsHierarchy and IVsUIHierarchy
- an abstract project node, that inherits from the base node and implements
IVsProject3
- a concrete project class inherits from the base project

The project factory creates an instance from the concrete project without
any child nodes. In the solution explorer I have only one node per project.

The sympthom is that if the project node is selected in the solution
explorer, the properties window does not display the project node
properties, although the project node has several displayable of these. It
keeps showing the proerties of the last selected node from another project
type (e.g. c#).
But sometimes when I add a new project of my project type to the solution,
it displays the properties correctly. But if I change the selecttion to the
c# project and back, than again does not work.

I have read in one of the previous posts, that there were problems in the
VS2003 with the objects returned for the VSHPROPID_BrowseObject, and I have
played a lot with the GetProperty results, but I didn't found the problem.
The funny thing is that the properties window in the Basic Project sample
works even if I comment out the borowseobject responses, than my project why
not? :(

Also might be interesting, that if I set in VS to stop for all exceptions, I
see a lot (6-8) of InvalidCast exceptions, with message
       "QueryInterface for interface
Microsoft.VisualStudio.Interop.IVsHierarchy failed."
coming from either from
"microsoft.visualstudio.dll!Microsoft.VisualStudio.PropertyBrowser.PropertyBrowser.VsSelectionEventSink.ctor"
or from the mystic "Unknown Module". These exceptions are handled inside VS,
but maybe still related to my problem.

Do you have any idea what the problem could be?

Sorry for the long post.

Br,
Gaspar