Bob Arnson wrote: > >It appears to be by design, based on this comment in the code: >
IMHO, it is a bug, by design, but still a bug. According to Aaron Stebner's blog http://blogs.msdn.com/astebner/archive/2005/02/12/371646.aspx the fusion bug was fixed long time ago (.Net 1.1 SP1 & .Net 2.0) and I see no reason to keep this limitation in Wix. At least let the user choose (a command switch will do) whether "light" should produce .Net 1.1 compatible code or a more general one. Do you have any "best practice" suggestion for registering and installing an assembly with vesion=4.0.0.0 and fileversion=4.0.767.0 ? I don't want the assembly version to be hardcoded in the Wix source files. I want to get it dynamically from the actual assembly being packed in the MSI file. Thanks, Dov ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
