forum.vdsworld.com

vdsalchemist · Posted: Wed Jun 27, 2007 3:45 pm Post subject:

Hmmm somewhat easier to understand as far as Item ID List's (PIDL) go is when you set a link to a Control Panel Applet, a printer, or another computer. I think you might understand now. These are shortcuts but they resolve to something more than just a single directory or file.

LiquidCode · Posted: Wed Jun 27, 2007 4:03 pm Post subject:

Ok, I got it. When I edit the .lnk file, can I change it to a path/file that may not exist yet (or even be a "valid" path)? I am thinking about using the setx.exe to add an environmental variable for part of the path of the shortcut. Now when I set the variable, I can go and manually change the path in a .lnk file using the variable (i.e. %drive%:\Program Files\My Program\Program.exe). the LINK command in VDS does not let me make a .lnk file because it cannot find the file because of using the %drive%. Will your dll let me create/edit a .lnk file to use the %drive%? Know what I mean?

vdsalchemist · Posted: Wed Jun 27, 2007 4:56 pm Post subject:

Hmmm I don't think that will work? The DLL has a command called Set,RelativePath which will allow you to make it possible to move the LNK and/or file that the lnk points too to any drive you like and the LNK will automaticly be updated to reflect the change. This is called Resolving the LNK file. You will also be able to force a resolution of the link as well. There is a Resolve command in the DLL to make this possible. Also when you create a new link with the DLL it will automaticly perform the Set,RelativePath before saving the new link. Existing links you will need to set the relative path before saving the link. The save command handles both saving new links and updating existing links. This information will be in the help file.

LiquidCode · Posted: Wed Jun 27, 2007 5:09 pm Post subject:

Ok, I'll have to change my app a little. Don't think it'll be a big deal.

Thanks!

vdsalchemist · Posted: Wed Jun 27, 2007 7:00 pm Post subject:

Hmmm

the GUI allows you to use evironment variables inplace of the drive letter but when I try to use the Shell to Set the target it keeps putting C:\ infront of what ever path I use. 'scratching my head in total confusion'

vdsalchemist · Posted: Wed Jun 27, 2007 8:29 pm Post subject:

Ok after much research and mostly Trial & Error I found that if I use one of the default environment variables like %windir%, %SystemDrive%, or %SystemRoot% then the Set,Target and Save commands work without issue. I suspect my PC needs a reboot since I added the new environment variable %DRIVE% to the list of variables and I didn't use the setx.exe program that you were refering too. All I can say at this point is to try what you were going to do and let me know. Worse case I write the target directly without useing the Shell COM objects. It would take a bit of work on my part but I am confident that I could do it if the normal way does not work. Let's try the norm first then we will go from there.

LiquidCode · Posted: Wed Jun 27, 2007 8:53 pm Post subject:

Ok sounds good. I'll give it a try. Any estimate when the dll will be ready?

vdsalchemist · Posted: Wed Jun 27, 2007 9:08 pm Post subject:

I am working on the help file now. It should be ready by tomorrow or the next day.

vdsalchemist · Posted: Thu Jun 28, 2007 9:44 pm Post subject:

Chris,
I have uploaded the DLL here http://www.vdsworld.com/search.php?view_mode=fileinfo&file_id=489 for now. I will be uploading it to my site tonight or tomorrow. Please try it out and let me know what you think.

LiquidCode · Posted: Fri Jun 29, 2007 12:31 am Post subject:

Thanks! I'll try it out tonight or tomorrow.

LiquidCode · Posted: Fri Jun 29, 2007 5:39 pm Post subject:

Works great so far. Much faster then re-creating the shortcuts over.

vdsalchemist · Posted: Fri Jun 29, 2007 6:19 pm Post subject:

LiquidCode · Posted: Fri Jun 29, 2007 6:29 pm Post subject:

Thanks a bunch. FYI: I sent you a PM on your forum.

vdsalchemist · Posted: Fri Jun 29, 2007 7:16 pm Post subject: