Thanks The problem was solved using your inputs. giora
Blair wrote: > Generally not. The Component's guids should be stable (if a component > contains the same things, only newer, being installed, it generally should > keep the same guid). Only if you change the name or path of the file/key of > the component's keypath (if you only have one file/registry item that will > be its keypath) should you be changing the guid. > > If you are changing ProductCodes (as you appear to be) you generally don't > include REINSTALL in the command-line nor do you include 'v' in > REINSTALLMODE. Those are used for minor upgrades and small updates (and > patches, which are generally either minor upgrades or small updates), and > for both those cases, the ProductCode doesn't change, which is why REINSTALL > and the 'v' in REINSTALLMODE become required. > > -----Original Message----- > From: Giora keinan [mailto:grkei...@gmail.com] > Sent: Thursday, October 29, 2009 9:06 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] MSI upgrade is looking for the original MSI file > > Hello > Thanks for the quick response. > > I think I am using different GUIDs. > in the original MSI it is > <Product Name='CapsCake' Id='D497344E-D020-4DD8-B2CD-653287D8DA80' ... > > int the upgrade it is > <Product Name='CapsCake' Id='D34C4CCF-495E-453E-9F7A-5A8CEC65643F' > > Should I replace the guide of each component that I am replacing in the > upgrade (one executable and one registry key) > > thanks > Giora > > > > > Blair wrote: > >> If you keep the same ProductCode (the guid at produ...@id in your code) >> > then > >> the MSI must keep the same name. If you can't guarantee the same name then >> you should look at Major Upgrades. The easiest way to keep the ProductCode >> changing is to use '*' as the value for produ...@id. >> >> -----Original Message----- >> From: Giora keinan [mailto:grkei...@gmail.com] >> Sent: Thursday, October 29, 2009 8:29 AM >> To: wix-users@lists.sourceforge.net >> Subject: [WiX-users] MSI upgrade is looking for the original MSI file >> >> Hello >> >> I created an installation and upgrade MSI files using WIX. >> (Which was relatively easy). >> >> I am testing the upgrade msi. >> >> if the original MSI (Xyz.msi) is present in the original path the >> upgrade is done smoothly. I am using the command: >msiexec /i >> XyzUpgrade.msi REINSTALL=ALL REINSTALLMODE=vomus >> >> But if the original Xyz.msi is not present the msiexec displays a >> message similar to >> "A Network error occurred while attempting to read from the file >> "c:\.......\Xyz.msi"" >> >> My problem is that many users delete the MSI file after the installation >> and the upgrade will fail. How can I solve this problem? >> >> Thanks >> >> Giora >> >> >> >> >> >> >> > ---------------------------------------------------------------------------- > >> -- >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> > ---------------------------------------------------------------------------- > -- > >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> > > ---------------------------------------------------------------------------- > -- > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
