I am creating an MSI for a collection of files and folders that are accessed locally by various unix-type (case sensitive) applications. The problem I have is that I need to create a junction for the main folder so that it can accessed by various unix-type applications in XP. I can use linkd to create the junction but if I try to capture it in IS, it converts the junction to a normal folder, duplicating both the the physical folder and removing the junction.

Example - I have c:\test\junk as the physical folder. I used linkd to create the junction named "morejunk" in c:\test and pointed it to c:\test\junk.
When doing a dir in the c:\test folder I get junk and morejunk. Junk shows up as a physical folder and morejunk shows up as a junction. Those are the expected results.

My goal is to have a package that will create the physical folder, put the files into it (got that part) and create a junction at the parent folder level (c:\test) with a different name (for the unix-type applicaions to look for).

I've looked through the forums and don't see much information on using linkd much less using it in an MSI. Is my best bet to use a script (or batch file) as a custom action to create the junction (using linkd)? If so, I guess I'll need to create another custom action for uninstall as well for the junction.

Any help with this would be appreciated.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Hi Lewis,

Don't know much about the linkd tool but based on what you've written I'd say you should definately use scripted CA's for install / uninstall - with the appropriate error trapping of course.

Let us know if you need a hand with the scripts / conditions etc.

Answered 06/05/2010 by: MSIPackager
Third Degree Black Belt

Please log in to comment