We have been using WIX for building an MSI file for a new tool called Migration
Tool for Dynamics AX.
We are running into some issues with the msi files that were generated using
the Wix. We have to run APIScan on the msi before we can release the tool. The
purpose of the APIScan is from the on-line help -
The main goal of APIscan is to determine whether your software is using any
internal Windows interfaces that are not publicly documented. APIscan
enumerates every application programming interface (API) or service that is
invoked by your product and verifies that a reference topic has been published
on MSDN.
Unfortunately, we are using custom actions within WIX. We have to use the
libraries for custom actions - sca.wixlib, and wixca.wixlib. These libraries
have references to DLLs - ScaSched.dll, ScaExec.dll, and WixCA.dll, and those
DLLs become part of the our MSI, and they do not have any symbol information
within the msi.
Even though we can technically ignore those DLLs for APIScan, we won't be able
to run the APIScan on our msi that has those DLLs because it cannot analyze
those DLLs for any reference to undocumented windows API without the symbol
information.
Has anybody else faced this problem while running APIScan on the msi created
using WIX, and is there any workaround, other than just ignoring those three
DLLs?
Thanks
Madan
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
