S
sethspublicemail
I've written an Icon Handler shell extension that generates a custom
icon (i.e. it provides a handle to the actual icon data rather than
pointing Windows at a file with an icon index). The icon is based on
the complete name of the file and not just the extension. This was
working (although with a minor workaround) in outlook 2003.
If the user attached a file, say, C:\afolder\afile.doc.ext, the icon
handler would get called with C:\afolder\afile.doc.ext and then again
with C:\<path to temporary internet files>\OLK1976\afile doc.ext
The weird part for outlook 2003 was the conversion to only have one
extension and replacing other periods with spaces. Weird, but
something we could work around.
In Outlook 2007 all I get for a path in the call to the Icon Handler
is: C:\WINDOWS\.ext
No path to an actual file, temporary or not. No stripping of periods
or anything, just the three letter extension. This seems to ignore
the entire purpose of an IconHandler (rather than just setting the
DefaultIcon for the file in the registry) and I was wondering if
anyone else has run into this issue or has any idea if this is a bug
or a feature with Outlook.
Additionally, I'm hoping this is the right forum for this question, if
not, could someone please direct me to the correct newsgroup? I've
spent quite a while searching.
Seth
icon (i.e. it provides a handle to the actual icon data rather than
pointing Windows at a file with an icon index). The icon is based on
the complete name of the file and not just the extension. This was
working (although with a minor workaround) in outlook 2003.
If the user attached a file, say, C:\afolder\afile.doc.ext, the icon
handler would get called with C:\afolder\afile.doc.ext and then again
with C:\<path to temporary internet files>\OLK1976\afile doc.ext
The weird part for outlook 2003 was the conversion to only have one
extension and replacing other periods with spaces. Weird, but
something we could work around.
In Outlook 2007 all I get for a path in the call to the Icon Handler
is: C:\WINDOWS\.ext
No path to an actual file, temporary or not. No stripping of periods
or anything, just the three letter extension. This seems to ignore
the entire purpose of an IconHandler (rather than just setting the
DefaultIcon for the file in the registry) and I was wondering if
anyone else has run into this issue or has any idea if this is a bug
or a feature with Outlook.
Additionally, I'm hoping this is the right forum for this question, if
not, could someone please direct me to the correct newsgroup? I've
spent quite a while searching.
Seth