Hi Don,

Currently, we are looking into this problem. We will reply here with more
information as soon as possible.
If you have any more concerns on it, please feel free to post here.

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Don,

What version of VS .Net are you targeting with this package? (just curious,
as I may need to mangle the appropriate MyC sample to confirm some of this).

This functionality is actually provided through the
cmdidPropSheetOrProperties command, which is handled by the IDE. The shell
calls an internal function called PageFrameCanShowPropertyPages and if this
fails, drops down into the cmdidPropertyPages case which simply displays
the properties dialog.

If memory serves, this PageFrameCanShowPropertyPages uses a global object
that's populated by the IDE's selection state. And if I recall correctly,
that code actually relies upon there being a valid browse object for the
selected hierarchy item(s).  Additionally, there is a pretty nasty bug in
VC 2003 that may require you to pass that VSHPROPID_BrowseObject  as an
IUnknown pointer instead of an IDispatch pointer.  For example:

  // CVsHierarchy::GetProperty (hyarchy.cpp) workaround for crashing
problem invoking Properties dialog with multiple items selected.

   case VSHPROPID_BrowseObject:        // CHierNode derived property
       // if the node is the root node check if CVsHierarchy object
implements IDispatch
//        if (pNode->GetVsItemID() == VSITEMID_ROOT && SUCCEEDED(hr =
this->QueryInterface(IID_IDispatch, (void **)&V_DISPATCH(pvar))))
       if (pNode->GetVsItemID() == VSITEMID_ROOT && SUCCEEDED(hr =
this->QueryInterface(IID_IUnknown, (void **)&V_DISPATCH(pvar))))
       {
//            V_VT(pvar) = VT_DISPATCH;
                V_VT(pvar) = VT_UNKNOWN;
         }
       else
       {   // reclear the variant
           ::VariantInit(pvar);
           if (FAILED(hr = pNode->GetProperty(propid, pvar)))
               hr = E_NOINTERFACE;
       }
       break;

I ran into this a few months ago with another customer, so in addition to
ensuring your hierarchy item supports that VSHPROPID_BrowseObject property,
you migth want to modify the hierutil7 codebase with the above workaround
if you're targeting VS 2003.

Sincerely,
Ed Dore [MSFT]

This post is 'AS IS' with no warranties, and confers no rights.

Hi Don,

Please disregard my previous posts on this topic. That info was actually in
references to a different issue where we were attempting to invoke the
property frame dialog from the classview.

To invoke the property frame via the Properties (actually the
cmdidPropSheetOrProperties command), the hierarchy node in question must
implement either ISpecifyPropertyPages, or IVsCfgProvider2, which in turn
provides an object implementing IVsCfg that also implements
ISpecifyPropertyPages.

Using Whidbey Beta2 with the matching VSIP SDK, I was able to get this
dialog invoked, by implementing ISpecifyPropertyPages on the
CFileVwFileNode class. You mentioned that you were not seeing the GetPages
method getting called, which leads me to suspect you didn't add an entry
for this interface in your COM map.

Regarding the reference to IVsCfgProvider2, I believe this is in reference
to whether or not the properties associated with the object ( in this case
the file ) are stored in a per configuration basis. For example, the build
options for a specific file may differ between debug and release
configurations. In the case of the C++ project system, we actually
implement IVsCfgProvider2 on the C++ hierarchy object representing the
file, along with IVsPerPropertyBrowsing, IPerPropertyBrowsing and
IVsExtensibleObject.

Here's the modifications I made to the MyC sample to allow for the
PropertyFrame to display:

PrjNFile.h

class CFileVwFileNode :
  public CFileVwBaseNode,
   public IConnectionPointContainerImpl<CFileVwFileNode>,
   public IPropertyNotifySinkCP<CFileVwFileNode>,
  public IDispatchImpl<IMyCPrjProjHierItemProps,
&IID_IMyCPrjProjHierItemProps, &LIBID_MyCPrjPKGLib>,
  public ISpecifyPropertyPages
{
  friend CMyProjectHierarchy;
  friend CFileVwProjNode;

  ........

   BEGIN_COM_MAP(CFileVwFileNode)
      COM_INTERFACE_ENTRY(IMyCPrjProjHierItemProps)
      COM_INTERFACE_ENTRY(IDispatch)
      COM_INTERFACE_ENTRY(IConnectionPointContainer)
      COM_INTERFACE_ENTRY(ISpecifyPropertyPages)
   END_COM_MAP()

  .........

  // ISpecifyPropertyPages
  public:
     STDMETHOD(GetPages)(CAUUID* pPages);
       .........
};

PrjNFile.cpp

HRESULT CFileVwFileNode::GetPages(CAUUID* pPages)
{
  pPages->cElems = 3;
  pPages->pElems = (GUID*)CoTaskMemAlloc(pPages->cElems * sizeof(GUID));
  if (!pPages->pElems)
     return E_OUTOFMEMORY;

  pPages->pElems[0] = CLSID_StockFontPage;
  pPages->pElems[1] = CLSID_StockColorPage;
  pPages->pElems[2] = CLSID_StockPicturePage;

  return S_OK;
}

Sincerely,
Ed Dore [MSFT]

This post is 'AS IS' with no warranties, and confers no rights.