Regarding pseudobundle.cpp, there is a version check that makes sure the
related bundle engine version is >= the last breaking change (3.6.2221.0)
and <= the current version. But if you build an addon or patch related
bundle with a newer version of Burn (which is very likely), then a host of
burn.* switches are not passed (oddly, -burn.related.* is, which seems
inconsistent). One example that does not get passed - since it's only passed
for Burn EXEs - is -burn.ignoredependencies.
If all new burn.* switches require a separate between switch and parameter
(if any parameter at all), do we really need this check? Any burn.*
variables that are not understood are thrown away.
Heath Stewart
VS Pro Deployment Experience, Microsoft
<http://blogs.msdn.com/heaths> http://blogs.msdn.com/heaths
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
