Vista - Shell extension - how do I disable the preview pane for my shell e

I have a shell extension we've used for years on Win2k, XP, 2k3 server.

Porting this to Vista, testing using build 5270, using .net 2005 VS C++.

What API exists for a shell extension to disable the explorer preview pane
for it?
I've looked in the 5270 SDK, in the header files, etc. Nothing looks
interesting.

Currently, even though I've added an entry in my manifest for the shell
extension .dll to request execution as administrator, I"m convinced in 5270
my dll isn't running at admin priv. How do I handle this? I"m still looking
for an answer myself, but a quick reply could save my company $$.

TIA

I guess I tried to slip two questions in there.

The first is the new preview pane for the Vista computer explorer. This can
be easily made rather large by user action. For my shell extension, it
serves no purpose, since all the info is already conveyed in my window. I'd
like to programatically be able to disable the preview pane, just for my
window, or at least set it to some minimal size out of the way. The problem
is my windows tries to adjust itself to fit in the available space. With the
possible largeness of the preview pane, this can be a problem when it doesn't
really need to be.

The second is a more general question. I figured out how to add to my
manifest for utilities ( non-managed .net 2005 created utils ) to request
admin priv upon user invocation. I tried to do this also for my shell
extension manifest ( in the shell extension .dll ). This doesn't seem to
help. It doesn't help either if I try to invoke an instance of the explorer
with 'run elevated'. It always seems to be non-admin priv, since my COM
interface complains about not having access to its service.

No information on these topics have been found yet in the MS SDK or online
documentation. I've gone through this before for previous OSes, so I'm
assume that eventually good docs will be released. I'm just under the gun
now to get something showable for a big customer...same ol; same ol.

"Zack Whittaker (R2 Mentor)" wrote:

> Well, not too sure on this one. Could you give me a step by step guide of
> what you're trying to do? T'is been a crazy day... mind is a bit jaggled!
>
> Thanks )
>
>
> --
> Zack Whittaker
> Microsoft Beta (Windows Server R2 Beta Mentor)
> » ZackNET Enterprises: www.zacknet.co.uk
> » MSBlog on ResDev: http://msblog.resdev.net
> » ZackNET Forum: www.zacknet.co.uk/forum
> » This mailing is provided "as is" with no warranties, and confers no
> rights. All opinions expressed are those of myself unless stated so, and not
> of my employer, best friend, mother or cat. Let's be clear on that one!
>
>
>

It's hard to say for sure without knowing exactly what your extension does,
but IMHO as a user, you shouldn't mess with the preview pane as it is the
user's choice how, where, and, what size to display it, and that they may be
viewing other files along side yours and would not appreciate the
enabling/disabling as they select different files (though it just occurred
to me that you may be talking about a shell namespace extension where you
want to disable it within your namespace).

"Trurl" <Trurl@discussions.microsoft.com> wrote in message
news:252B1B85-05EB-4066-BCD9-C725E5632F25@microsoft.com...
>I guess I tried to slip two questions in there.
>
> The first is the new preview pane for the Vista computer explorer. This
> can
> be easily made rather large by user action. For my shell extension, it
> serves no purpose, since all the info is already conveyed in my window.
> I'd
> like to programatically be able to disable the preview pane, just for my
> window, or at least set it to some minimal size out of the way. The
> problem
> is my windows tries to adjust itself to fit in the available space. With
> the
> possible largeness of the preview pane, this can be a problem when it
> doesn't
> really need to be.
>
> The second is a more general question. I figured out how to add to my
> manifest for utilities ( non-managed .net 2005 created utils ) to request
> admin priv upon user invocation. I tried to do this also for my shell
> extension manifest ( in the shell extension .dll ). This doesn't seem to
> help. It doesn't help either if I try to invoke an instance of the
> explorer
> with 'run elevated'. It always seems to be non-admin priv, since my COM
> interface complains about not having access to its service.
>
> No information on these topics have been found yet in the MS SDK or online
> documentation. I've gone through this before for previous OSes, so I'm
> assume that eventually good docs will be released. I'm just under the gun
> now to get something showable for a big customer...same ol; same ol.
>
> "Zack Whittaker (R2 Mentor)" wrote:
>
>> Well, not too sure on this one. Could you give me a step by step guide of
>> what you're trying to do? T'is been a crazy day... mind is a bit jaggled!
>>
>> Thanks )
>>
>>
>> --
>> Zack Whittaker
>> Microsoft Beta (Windows Server R2 Beta Mentor)
>> » ZackNET Enterprises: www.zacknet.co.uk
>> » MSBlog on ResDev: http://msblog.resdev.net
>> » ZackNET Forum: www.zacknet.co.uk/forum
>> » This mailing is provided "as is" with no warranties, and confers no
>> rights. All opinions expressed are those of myself unless stated so, and
>> not
>> of my employer, best friend, mother or cat. Let's be clear on that one!
>>
>>
>>