WMI Shell Folder

Closed Task: Create a release [7168]

JamesFinnigan — Tue, 14 May 2013 07:27:58 GMT

We need an initial release. Quality is still too low to release at this point, even as an alpha.

Closed Task: update screenshots [8479]

JamesFinnigan — Tue, 14 May 2013 07:27:58 GMT

need to put up a view of the current code

Reviewed: 1.0.0.1 Alpha (Nov 09, 2012)

mvallino — Fri, 09 Nov 2012 10:24:40 GMT

Rated 5 Stars (out of 5) - 11 9 12 Wonderful!! When you use windows explorer on the desktop, look for "== WMI Namespace" and explore it. It seems have no properties. What does it mean when the namespace's icon is red?? MichaelJoBillyJimBob

Source code checked in, #99885

Project Collection Service Accounts — Mon, 01 Oct 2012 21:24:31 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #99884

Project Collection Service Accounts — Mon, 01 Oct 2012 21:16:08 GMT

Checked in by server upgrade

Source code checked in, #74794

_TFSSERVICE — Tue, 03 Aug 2010 19:44:57 GMT

Checked in by server upgrade

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

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

Project License Changed

Fri, 30 Nov 2007 20:02:50 GMT

Microsoft Public License (Ms-PL) This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software. 1. Definitions The terms "reproduce," "reproduction," "derivative works," and "distribution" have the same meaning here as under U.S. copyright law. A "contribution" is the original software, or any additions or changes to the software. A "contributor" is any person that distributes its contribution under this license. "Licensed patents" are a contributor's patent claims that read directly on its contribution. 2. Grant of Rights (A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative works that you create. (B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in the software or derivative works of the contribution in the software. 3. Conditions and Limitations (A) No Trademark License- This license does not grant you rights to use any contributors' name, logo, or trademarks. (B) If you bring a patent claim against any contributor over patents that you claim are infringed by the software, your patent license from such contributor to the software ends automatically. (C) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software. (D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license. (E) The software is licensed "as-is." You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

COMMENTED ISSUE: Too much noise

JamesFinnigan — Fri, 20 Jul 2007 04:59:36 GMT

There are tons of items that don't actually have anything in them. And they clutter the UI. We should have an option to only show the parts of the namespace that actually have something in them. (Optionally.) And we should have an option to show/hide system properties.
Comments: ** Comment from web user: JamesFinnigan **

removed the __types, but the larger issue is all those empty classes.

CLOSED ISSUE: Our shell folder assumes unique display names

JamesFinnigan — Fri, 20 Jul 2007 04:57:38 GMT

And this isn't guaranteed. Perhaps we should keep a set of encountered display names while enumerating and force uniqueness? (As a workaround - it's not yet clear how much work would need to be done to allow non-unique display names.)
Comments: This was fixed with the introduction of the identity column

Source code checked in

JamesFinnigan — Thu, 12 Jul 2007 05:13:59 GMT

Add identity, childcount columns ParseDisplayName, and some noise reduction

CREATED ISSUE: Too much noise

JamesFinnigan — Fri, 29 Jun 2007 21:39:29 GMT

Project License Changed

Thu, 31 May 2007 23:45:39 GMT

Microsoft Permissive License (Ms-PL) This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software. 1. Definitions The terms "reproduce," "reproduction," "derivative works," and "distribution" have the same meaning here as under U.S. copyright law. A "contribution" is the original software, or any additions or changes to the software. A "contributor" is any person that distributes its contribution under this license. "Licensed patents" are a contributor's patent claims that read directly on its contribution. 2. Grant of Rights (A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative works that you create. (B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in the software or derivative works of the contribution in the software. 3. Conditions and Limitations (A) No Trademark License- This license does not grant you rights to use any contributors' name, logo, or trademarks. (B) If you bring a patent claim against any contributor over patents that you claim are infringed by the software, your patent license from such contributor to the software ends automatically. (C) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software. (D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license. (E) The software is licensed "as-is." You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

Source code checked in

JamesFinnigan — Fri, 25 May 2007 08:45:12 GMT

Adds basic viewing of properties

Source code checked in

JamesFinnigan — Thu, 12 Apr 2007 07:29:49 GMT

Repair selfreg

Source code checked in

JamesFinnigan — Thu, 15 Mar 2007 05:55:02 GMT

Yank some dead code and our ugliest icon.

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

New Post: Doing COM yourself or using ATL

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

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