Summary: I wrote a few lines of code to detect if the application being put into the MSI has any new assemblies which haven't been added to the WiX code. This seems to work fine.
I'm trying to figure out how to get the WiX build to fail if my detection algorithm indicates that the WiX code is no up to date. Can this extra check be hooked into the build somehow? Details: I have a VS2008 solution that revolves around building an MSI with WiX. It also includes building a bootstrapper. I have some C# code that opens the WiX source files, extracts the source file names, and compares that list to the files produced by the application build. It determines whether there are new assemblies in the application's build directory which are not found in the WiX source file. My intention is for this algorithm to halt the build if it detects that the WiX code is out of date. As it exists now, the few lines of code exist as a console application. I'm looking for suggestions on how to integrate this into the build, so perhaps it's more of a Visual Studio question than a WiX question. Any suggestions? Thank you very much! ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
