InstallAware

Try to build a setup using a small project using Installaware studio (x14 or x15 makes no differences, same result):

The project (attached as *.zip) has the following structure: (Mark 1 on printscreen)

Notepad (Rootfolder)
- Folder1 (Subfolder) contains file notepad.exe
- Folder2 (Subfolder) contains no file
- Help (Subfolder) contains file license.txt
- Folder3 (Subfolder) contains file license.txt

We are using wildcards to add subfolders and files in these folders (Mark 2 on printscreen)

A single file setup builds the correct result.

convert the same small project to an App-V package, result in the error "Failed to add file" (Mark 3 on printscreen)

I would like to ask again the @installwareSupport what they plan to solve this issue?
This is a clear bug, as the correct install definition of InstallAware is not converted correctly to the App-V package. But Installaware has a 3rd party tool included which they probably cannot fix themselves (https://www.gridmetric.com/products/libv.html).

As first, you should provide a VERY MINIMAL project that replicates the issue you seem to have.

Hello Francesco
what is NOT VERY MINIMAL in the attached sample?
- project with 3 Folders
- the help folder has a '*.*' pattern to include files
- a normal setup can be built
-> but the "App-V virtualization process" does fail (as shown in the attached screenprint)

I assume, you tested the attached sample and it did "not fail on your side"?

Ops ...I got it.

I have to check this out. I'll let you know as soon as possible.

For what I can tell you, the problem seems to be caused by the "help" folder under "..\_InstallAware\Notepad\Folder2".
If you try with replacing:
> "..\_InstallAware\Notepad\Folder2\*.*
with:
> "..\_InstallAware\Notepad\Folder2\Help\LICENSE.txt"

...it works.

Hello Francesco

>If you try with replacing ...

yes exactly. As you see, this fact was reported in the initial post
... We are using wildcards to add subfolders ...

this is the typical use case for the delivery of a help environment which includes a set of generated files. There we cannot work with "hand selected single files". This means, it's not a valid workaround for our use case.

@Francesco

I think you verified that the is an issue with our test case and the App-V wrapper.
As well I hope you see why we need to use the *.* folder approach for our help environment setup.
This means a valid setup use case does not work

What are the next steps?

@Francesco

still waiting ...

I have escalated the issue, but I cannot anticipate any timeframe for a possible resolution.

To mitigate the issue, you may use a custom compiler variable (you have to define it) in order to invoke the command conditionally:


Hope this helps you

thank you for escalating.

>Hope this helps you

Not really. The example with the "license.txt" was really just a sample. In reality we do have growing set of SQL upgrade files that ALL have to be shipped. Otherwise the software will not work.

Means: We do need the '*.*' option. At the moment we have to create the App-V package manually instead of using the App-V converter. Each time about 30 minutes more work and another potential source of errors.