/build/static/layout/Breadcrumb_cap_w.png

Backslash disappears in App-V shortcut

I have a problem with shortcuts in App-V 5.x When I create shortcuts to an executable with parameters like \\SERVERNAME\Sharename\Prowin32.exe -basekey "INI" -ininame \\SERVERNAME\Sharename\inifile.ini and I publish the sequence, the shortcut changes in \SERVERNAME\Sharename\Prowin32.exe -basekey "INI" -ininame \SERVERNAME\Sharename\inifile.ini (1 backslash is missing from the location of the inifile).

I tried putting in more backslashes or put the location between "" but nothing seems to work.

Does anyone know this problem? And hopefully know the solution?




0 Comments   [ + ] Show comments

Answers (1)

Posted by: rileyz 4 years ago
Red Belt
0

Create a batch file file with the command/parameters you want to use use. And in the sequence or post sequence create a shortcut to the batch file - you'll need to capture the batch file of course. 

This should do the trick.

Without knowing what your application is, I have a feeling you are creating a shortcut to a network executable which does not reside in the package - App-V wasn't designed to be used this this way. The method above allows App-V to load the "bubble" then punch out to the network executable.


Comments:
  • I was afraid this would be the answer. But you are right. The sequence is a local installed prereq and points to a network location. I knew several years ago it had the same problem and hoped something had changed. I will check with my customer if this solution is ok to implement. Thank you. - AndyPl 4 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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