File bag plug-in fails when output to network share
Posted: Thu Jan 17, 2013 5:14 pm
Hi,
We just upgraded one of our setup projects from IA9 to IA15. (build 12.12.12)
After upgrading it we started getting build errors regarding the "File bag" plug-in for runtimes. The error is along the lines of
"WARNING! No files matching wildcard pattern ....". For example we got it for the "setupnet4aip_x64" script. If we excluded this script we just got the error from one of the other scripts regarding runtimes.
After trying a number of things such as reinstalling IA15, copying script files from the fresh install etc. I found out what the problem is.
Under Project Settings | Output | Custom folder we are using a network UNC such as "\\10.0.1.1\SOMESHARE\Folder". Changing this to a local folder such as "C:\Test\" resolves the problem.
However using the UNC worked in IA9 so I think a bug has been introduced in a later version.
Now that we know the cause we can make a workaround, but I would like to know if you can confirm that this is indeed a problem, and if so is it something you intend to fix? If not that is fine with us, but then please add a comment to the help file stating that only local/"normal" folders can be used and not UNC.
br Lars
We just upgraded one of our setup projects from IA9 to IA15. (build 12.12.12)
After upgrading it we started getting build errors regarding the "File bag" plug-in for runtimes. The error is along the lines of
"WARNING! No files matching wildcard pattern ....". For example we got it for the "setupnet4aip_x64" script. If we excluded this script we just got the error from one of the other scripts regarding runtimes.
After trying a number of things such as reinstalling IA15, copying script files from the fresh install etc. I found out what the problem is.
Under Project Settings | Output | Custom folder we are using a network UNC such as "\\10.0.1.1\SOMESHARE\Folder". Changing this to a local folder such as "C:\Test\" resolves the problem.
However using the UNC worked in IA9 so I think a bug has been introduced in a later version.
Now that we know the cause we can make a workaround, but I would like to know if you can confirm that this is indeed a problem, and if so is it something you intend to fix? If not that is fine with us, but then please add a comment to the help file stating that only local/"normal" folders can be used and not UNC.
br Lars