<div>
Hmm, that's a long time ago. <br />
I think NULL is a legal value for the explorer to give to you since it is not interested in the new PIDL. So everything seems ok. Just don't give him a new PIDL in this case.<br />

</div>


Hmm, that's a long time ago.
I think NULL is a legal value for the explorer to give to you since it is not interested in the new PIDL. So everything seems ok. Just don't give him a new PIDL in this case.


<div>
Yes, Although NULL is valid, the Actual Namespace PIDL is not being upgraded to the new name given by the user. Its reverts back to the original name. The original PIDL was not released, since the new one could not be provided, and the new one could not be provided since the return PIDL was NULL. DEADLOCK! So, whu did explorer give me a NULL return PIDDLE value ?<br />

</div>


Yes, Although NULL is valid, the Actual Namespace PIDL is not being upgraded to the new name given by the user. Its reverts back to the original name. The original PIDL was not released, since the new one could not be provided, and the new one could not be provided since the return PIDL was NULL. DEADLOCK! So, whu did explorer give me a NULL return PIDDLE value ?


<div>
<div class="content wysiwyg-content">
In my Shell Namespace Extension, IShellFolder::SetNameOf() insist on calling my extension with the return* PIDL set to NULL. All other parameters appear OK ? Why is this happening.
</div>
</div>


In my Shell Namespace Extension, IShellFolder::SetNameOf() insist on calling my extension with the return* PIDL set to NULL. All other parameters appear OK ? Why is this happening.

IShellFolder::SetNameOf() calls with Output PIDL NULL

C++ is an intermediate-level general-purpose programming language, not to be confused with C or C#. It was developed as a set of extensions to the C programming language to improve type-safety and add support for automatic resource management, object-orientation, generic programming, and exception handling, among other features.