Walter Boggs wrote: > I reverse engineered an MSI created by someone else into a wxs file > using dark. The wxs shows all sorts of files from Windows\System, SDK > folders and other places, as well as a bunch of system-level registry > entries. Is my installer really going to include all that? I really want > to just install my app and treat most other stuff as system requirements.
You shouldn't need to ship anything beyond what your application needs. > The wxs seems to expect some sort of folder structure under the location > I specify as BaseInputPath (I’m using wix.targets). That means I have to > copy all of those files from various places into the specified tree > before I compile/link. Is that the normal way of doing it? Or should I > just edit the wxs directory element structure to point to where the > files actually are located? This is for an automated build situation. The [EMAIL PROTECTED] and [EMAIL PROTECTED] can be used to point directly to a location. Our installers get all the files from various locations on one of our servers. Rob > > > > Thanks for your help. > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
