I have a bundle that chains a prerequisite .NET framework using the NetFx40Web package group and an MSI and I'm using a custom managed BA. This works fine during installation and uninstallation. The .NET framework is either already present and detected or downloaded and installed, followed by my MSI. On uninstall, the .NET framework is left behind. However, during repairs Burn tries to repair the .NET framework package since it's part of my bundle. I would prefer that the .NET pre-req be left alone altogether after it's installed since it has nothing to do with my product directly and it can be repaired or uninstalled from the Programs and Features menu as necessary. Is there a way in my BA or elsewhere to prevent the .NET framework pre-req package from being repaired?
I apologize if I've overlooked a documented answer for this. Thanks in advance for any assistance. ------------------------------------------------------------------------------ The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
