|
|
|
date: Mon, 16 Jan 2006 20:10:32 -0500,
group: microsoft.public.platformsdk.ui_shell
back
Legacy Shell API
Hi -
I see that this group does not have any messages, but I hope that
someone with some knowledge checks it from time to time.
I have Win95 OSR2 as well as Win2K SP4, running VS6 SP6, targeting Win98
SE and WinXP SP2. (Ughh, I know.)
I need to write a very simple console application that updates (and
possibly creates) shortcuts on the Desktop. I need to change things
like the Target, the Working Directory, the WindowPlacement, etc.
Previously, we tended to just copy the .lnk files around, but I know
that it is dangerous to change things outside of the Shell's knowledge.
Reading through the documentation for the Shell, I see all these fancy
API's that make a lot of sense, but I am unable to compile any of the
examples. SHGetFolderLocation(), for instance, does not exist on my
system. SHGetDeskTopFolder() does, but either I'm using the returned
pointer incorrectly or I do not have a definition of the function calls
that I can make through that point, as the compiler complains, not
knowing anything about the parameters.
I think the root cause is that I'm running an older version of VC/C++,
VS6 SP6.
I see some discussion about the Shell() API, which seems to be supported
by Win95, but with few examples.
Unfortunately, I must use this platform combination, and not upgrade to
something more recent, or even install a newer SDK, as I am not in a
position to upgrade DLL's on the target machines. They are mobile
devices, with very limited resources, typically Win98 SE, and I
generally deploy with an over-the-air push, so sending a new DLL is out
of the question.
Does anyone have insight or an example of how I should approach this
problem. One of the things I want to do is maintain platform
independence between the Win98 SE and the WinXP SP2 platforms. I am
certain that the correct DLL's exist on both of these platforms, but my
development system, AND ITS DOCUMENTATION, is lacking, I think.
Any assistance will be appreciated. Please respond only to the
newsgroup - in fact, dues to SPAMming problems, my eMail address is
"invalid", though my first name is correct. Thank you.
Alex S.
date: Mon, 16 Jan 2006 20:10:32 -0500
author: Alex
|
|
