Hello Bob,
Bob Arnson-6 wrote: > > On 6/19/2010 4:06 AM, Stefan Kuhr wrote: >> is it possible to use the DefaultVersion attribute for unversioned files? > > No. DefaultVersion just sets the File.Version column. See the MSI SDK > doc for the File table for limitations. > > OK, thanks for the answer and the clarification. I still wonder how Jim Evans did this with his text file, I am referring to: http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg19007.html So what would then be a proper solution for my problem? I have PNG files (so theses are unversioned by definition) that I always want to replace with those from my install, even if the customer replaced them with his own files in the older version of my app that I am about to upgrade with a major update. I am always doing major updates and currently have only one file per component, so each PNG file represents its own component. I guess if I created each PNG-component with a new GUID with each new major version that would break component rules, right? Would making the PNG files companion files of a DLL or exe, that I replace with a new version in each major update, solve the problem? Thanks, -- Stefan -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-can-I-use-DefaultVersion-for-unversioned-files-tp5198138p5209040.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
