WMIFldr Forum Rss Feed

New Post: x64 project small fixes

cristianamarie — Sun, 07 Dec 2008 07:25:55 GMT

I just created the x64 project and compiling it I've noticed the following errors:

- IPersistFolder2::Initialize should take a PCIDLIST_ABSOLUTE as parameter instead of PCUIDLIST_ABSOLUTE

- IPersistIDList::SetIDList is declared in CWMIFldr.h as

IFACEMETHODIMP SetIDList(PCIDLIST_ABSOLUTE pidl)

but in CWMIFldr.cpp is

HRESULT CWMIFldr::SetIDList(PCUIDLIST_ABSOLUTE pidl)

should be PCIDLIST_ABSOLUTE also in the .cpp file.

(At least so they are declared in the SDK v6.0 I have installed).

Regards,

Cristian Amarie

Doing COM yourself or using ATL:

JamesFinnigan — Sun, 11 Mar 2007 19:52:45 GMT

Hi Victor,

(Well, the source code is not in a good state at the moment - it's entirely because I've had almost no time to give to this project. So it's definitely good to not infer too much from the code layout as is. I'm learning WMI with this code, which will get a substantial scrubbing and rewrite. I would characterize it as pre-alpha quality.)

I moved away from ATL because I wanted more flexibility around QueryInterface logging (important for diagnosing IShellFolder issues). So I'd like to get back to ATL, but I don't want to lose the improvements - I have to consider how to do that. I'd like to generalize the logging so that it can be applied to any shell folder without recompilation which will probably allow a return to ATL COM. At the same time, there are usually calls within the shell folder that could not be intercepted with a proxy approach without cooperation, so I may keep this style or consider other approaches.

Hope that helps,
James

Doing COM yourself or using ATL:

vbaderks — Sat, 10 Mar 2007 20:59:04 GMT

Hi James,

While reading your source code, I saw that you handle all low level COM stuff yourself. Is this is a design decision or just the current implementation?

Victor

Shellfolder test suite:

JamesFinnigan — Thu, 22 Feb 2007 04:53:58 GMT

So one of the projects that I've been considering is making some software that could detect the known bugs in shell folders and generate a list of issues. Wow, not exactly groundbreaking idea there, but is anybody interested in it? I found that I hit a lot of subtle issues writing shellfolders - do you? Would you rather just get the list of errors? Would you fix the errors?