shell extension: IColumnProvider and vista

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi

I'm finding that my shell extension for the Windows Explorer Details View
customization through the IColumnProvider interface is not working on vista.

I've registered the extension the same way as I do in Windows XP - i.e. put
the CLSID of the object implementing IColumnProvider under
HKCR\Folder\shellex\ColumnHandlers. It works fine on XP.

Anyone know if there is any change in Vista regarding support of legacy
column handlers ? (I know there is the new IPropertyStore based interface,
but I was assuming the older interfaces will work as well).

thanks for any information.
 
Ravik said:
I'm finding that my shell extension for the Windows Explorer Details View
customization through the IColumnProvider interface is not working on vista.
Click to expand...

same problem here; have not had time to investigate the cause
 
i intended to include: have you reviewed the info about SHCOLUMNID being
deprecated in favor of PROPERTYKEY? I have been assuming this was this issue
but, as I said, I haven't followed up on it yet.
 
It appears that my object is not even being created. I.e. my com server dll
is not getting loaded.
Would the PROPERTYKEY change apply to legacy interfaces as well ? I think
the contents of both structures are same, though.
Thanks for any more info.
 
Ravik said:
It appears that my object is not even being created. I.e. my com server dll
is not getting loaded.
Click to expand...

I took some time today to play with this a bit, and I have come to the same
conclusion that you have. Too, not only do my own column handlers not work
under Vista, but so far I haven't found anybody else's that work, either.

Also, FYI, when i created my first column handler, I used some example code
that apparently has a pretty basic defect (altho fixing it doesn't address
the problem we're having, of course). In that example, the author used ATL's
_Module.pguidVer to set the SHCOLUMNINFO scid.fmtid field inside
GetColumnInfo(), but that value is not unique to the compiled binary. He has
now changed his code example to use the CLSID of the extension (which really
makes more sense, but I had never before examined ATL very closely and just
went along with what he was doing, as I needed to create a column handler
quickly). I just thought I'd mention it on the off chance that you happened
to find and use the same example - or a derivitive thereof - for your own.

I think at this point I'm going to start again from scratch, without using
anyone else's examples, and see where it leads me.
 
Back
Top