/build/static/layout/Breadcrumb_cap_w.png

UNC Path in the Directory table

Maybe somebody here can help me out on this.
I'm using Wise Package Studio 7.x
I need to set a UNC path as the working directory for a shortcut. When I did the setup Capture, WPS set the path to c:\myserver\myshare\myfolder. What I need is \\myserver\myshare\myfolder.

I went into the Directory table and found this:
Directory -> Parent -> Default -> Full Directory
myserver -> TARGETDIR -> myserver -> myserver
myshare -> myserver -> myshare -> myserver\myshare
myfolder -> myshare -> myfolder -> myserver\myshare\myfolder

So I modifed the myserver entry so that the parent is empty and the default is \\myserver, but WPS puked out an error about an "Invalid Argument". The MSI compiles but fails to install with a 2714 error.

What magical incantation do I have to do to set a UNC path up in the Directory table?

Thanks.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: cygan 14 years ago
Fifth Degree Brown Belt
0
first of all gtimlin you are looking in the wrong place

if you have messed up your msi with all that hacking then I suggest start again

what you want to do is this


go to the property table and create a property


property value
WORK | \\server name\unc path


go to the shortcut table and in the workingdir col change the value to WORK

that's all you need to do
cheers
Posted by: gtimlin 14 years ago
Orange Belt
0
Yep. That was it. I actually started looking in the shortcut table and was halfway there before I re-checked the forums.

Thanks for the help!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ