Hello everyone, I tried to create a patch for one of our products and stumbled across the issue that the components key paths was changed accidentally. It was changed because the key path is a registry key that is going to be removed during the update. The result is that when using wix/pyro for the patch creation, pyro exist with an error complaining about the changed key path, which is correct to me. What is curious is, when using the "old" msimsp way and tool, there is no error message on the changed component code.
MSDN documentation (http://msdn.microsoft.com/en-us/library/aa367850%28v=VS.85%29.aspx) is clear on filepath change: "The update must not change the component code of any component. Consequently, a small update or minor upgrade must never change the name of a component's key file because this would require changing the component code." , but does say nothing about the registry paths as key path... So my question is if someone could tell me who (pyro or msimsp method) is correct? Is it a bug/feature in either pyro or msimsp? For reference I used wix 3 RTM version and MSI 5.0 for patch creation. Any guidance is greatly appreciated. Best regards, Tobias -- GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
