> Our team is using WIX to generate Fragments and an Installer package. > Today, we have two Configurations that we build during our TFS build. > First, we build a Release configuration so that we can digitally sign > the output for inclusion into the Installer file. Second, the > installer is built during the Deployment Configuration. We have put > each of our features into Fragments and used Project References to > point back to the actual location of the artifacts we want to include > for that fragment. The fragments are then included in one MSI > installer file. The installer package CABs all of the files and > includes them inside the final MSI. > > The issue we are seeing is that during our Deployment configuration > build any project that is contained in the Project Reference for the > Fragment is getting built again overwriting the digital signature. We > dug into it a see that it is using Wix2010.targets during the MSBuild > process. In addition, the "Build Order" and "Project Dependecies" > have nothing in them for each of the Fragment projects. > > Is this the expected behavior? We have a pretty large build process > that encompasses many project so changing signing to a post build > event wouldn't be possible so I need a way to ensure that the signed > version of the binary isn't overwritten. > > Thanks > > Terry
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
