Re: [WiX-users] Setting the version number...
See http://wix.sourceforge.net/manual-wix3/light.htm Section "Package Properties" Dirk On Tue, Nov 6, 2012 at 12:39 PM, Goran wrote: > Has there been an improvement regarding this issue? We can use !bind > without > any problems from the msi wxs file, but I could not find a way to get > version from the wxi (or from the bundle, if we are able to reference the > version of msi package)? > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setting-the-version-number-tp5942903p7581771.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > LogMeIn Central: Instant, anywhere, Remote PC access and management. > Stay in control, update software, and manage PCs from one command center > Diagnose problems and improve visibility into emerging IT issues > Automate, monitor and manage. Do more in less time with Central > http://p.sf.net/sfu/logmein12331_d2d > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.6 MergeModule creation regression?
will do! Dirk -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3.6 MergeModule creation regression?
Hello Rob, here is a minimal mergemodule showing the error: http://schemas.microsoft.com/wix/2006/wi";> W:\tmp\CommonFiles.wxs(14) : error LGHT0231 : The component 'cComSTAHelper.63744358_CA08_4563_B039_4BE7181B668E' has a key file with path 'TARGETDIR\acme\comsta helper\comstahelper.dll'. Since this path is not rooted in one of the standard directories (like ProgramFilesFolder), this component does not fit the criteria for having an automatically generated guid. (This error may also occur if a path contains a likely standard directory such as nesting a directory with name "Co mmon Files" under ProgramFilesFolder.) Kind regards Dirk -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX 3.6 MergeModule creation regression?
Hello, I just upgraded from WiX 3.5 to WiX 3.6 (always the release versions) The following merge module does not compile any more now: http://schemas.microsoft.com/wix/2006/wi";> The ComponentGroup "ComponentGroup.PFCoDIA.Fdt.Profibus" contains a component "cComSTAHelper" that has a DirectoryRef to "CommonFilesFolder". Error message: W:\PFCoDIA\Deployment\PFCoDIA.Framework.MergeModule\PFCoDIA.Framework.Lib.Fdt.wxs(65) : error LGHT0231 : The component 'cComSTAHelper.GUID_GUID_GUID_GUID' has a key file with path 'TARGETDIR\MyEmployer\comstahelper\comstahelper.dll'. Since this path is not rooted in one of the standard directories (like ProgramFilesFolder), this component does not fit the criteria for having an automatically generated guid. (This error may also occur if a path contains a likely standard directory such as nesting a directory with name "Common Files" under ProgramFilesFolder.) Is this a bug/regression in WiX or is this a real problem which the old WiX 3.5. simply did not catch? No, I can't use wixlibs in this case, because the final product must be a merge module. Thank you in advance Dirk -- Dirk Ziegelmeier * d...@ziegelmeier.net * http://www.ziegelmeier.net -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Detect perUser install from perMachine install (Launchcondition)
Thank you Peter, I should be able to make it work using your information! That's what I was looking for. Dirk -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Detect perUser install from perMachine install (Launch condition)
Hello, I'd like to author an MSI that shall upgrade an old (non-WiX) setup. The old setup had an option where it could either be installed perMachine or perUser. The new setup should be perMachine only, so I'd like to write a launch condition that reads "Please uninstall old [Product] before installing the new one" when an old perUser install is detected. I am aware that the launch condition will only work for the user installing the setup, if another user has installed the old setup, too, it will not be detected. This limitation is acceptable. My problem is that I'm unable to find an example for a RegistrySearch or whatever which I need to detect the old perUser setup. Can someone point me into the right direction? Thank you in advance Dirk -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix upgrade process does not consider 4th part of the version string
Hi, read this thread. Maybe this is what you need: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setup-upgrade-needs-to-care-for-4th-part-of-version-number-td3250189.html Dirk On Fri, Jan 14, 2011 at 23:55, Wilson, Phil wrote: > That's a Windows Installer limitation on upgrades. > > http://msdn.microsoft.com/en-us/library/aa369786(v=vs.85).aspx > > "Note Windows Installer uses only the first three fields of the product > version ..." > > Phil Wilson > > -Original Message- > From: Sanjay Rao [mailto:s...@noida.interrasystems.com] > Sent: Friday, January 14, 2011 1:33 PM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Wix upgrade process does not consider 4th part of the > version string > > Hi, > > I have an installer having 4-part version strings. Our installer stops > installation if a newer version is already installed on the system. We > often have alpha/beta releases of our product in which we do not change > first 3 parts of the product. Suppose we have two releases of our product : > Release1 : 3.0.1.14500(Alpha) > Release2 : 3.0.1.14900(Beta) > > Our users are able to install alpha release even if beta is already > present on their systems. > I went through this article > http://wix.sourceforge.net/manual-wix3/major_upgrade.htm > see the paragraph having text "Windows Installer only uses the first 3 > parts of the" > > Is there any way in Wix to take care of 4th part of version string in > upgrade process ? > OR > Do I need to dive into clumsy custom action thing to take care this ? > > Regards, > Sanjay Rao > > -- > Sanjay Rao > Digital Media Group, Interra Systems > s...@interrasystems.com > Phone: +1-408-873-1212 > http://www.interrasystems.com > > > -- > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > *** Confidentiality Notice: This e-mail, including any associated or > attached files, is intended solely for the individual or entity to which it > is addressed. This e-mail is confidential and may well also be legally > privileged. If you have received it in error, you are on notice of its > status. Please notify the sender immediately by reply e-mail and then delete > this message from your system. Please do not copy it or use it for any > purposes, or disclose its contents to any other person. This email comes > from a division of the Invensys Group, owned by Invensys plc, which is a > company registered in England and Wales with its registered office at 3rd > Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For > a list of European legal entities within the Invensys Group, please go to > http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77 > . > > You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail > recept...@invensys.com. This e-mail and any attachments thereto may be > subject to the terms of any agreements between Invensys (and/or its > subsidiaries and affiliates) and the recipient (and/or its subsidiaries and > affiliates). > > > > > -- > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about register .net COM object
Hello,
this is a working example of a COM object registration:
Examples for the defines:
D_Product_Fqn: Adm2.Adm.Dtm, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=7b26e28fb8781288
C_DtmClass: Adm2.Adm.Dtm.Adm
D_ProductImageRuntime: v1.1.4322
C_DtmClassId:
C_DtmProgId:
D_ProductVersion: 1.0.0.0
I hope you can see in there what you need/want to do.
Dirk
On Mon, Jun 14, 2010 at 15:55, Christopher Painter <
chr...@deploymentengineering.com> wrote:
> regasm /regfile doesn't always work because if you have any user defined
> register functions they will not be in the regfile. From what I've seen of
> heat, it's not vunerable to this extraction problem. InstallShield does
> have this problem.
>
> Personally I wrote a little UI over heat that watches a directory for
> changes and spits out a wix fragment. I just scrape up the harvested XML
> and paste it into my installer source.
>
>
>
> - Original Message
> From: "gree...@cox.net"
> To: General discussion for Windows Installer XML toolset. <
> wix-users@lists.sourceforge.net>
> Cc: Elfe Xu
> Sent: Sat, June 12, 2010 2:48:58 PM
> Subject: Re: [WiX-users] Question about register .net COM object
>
> I saw regasm in the CustomAction element, so I am assuming that this is a
> .NET assembly exposing COM objects. Use the /reg option to create a .reg
> file containing all of the registry settings. Then you can manually enter
> these values into the Wix projects.
>
> Wix has some tools that can automate some of this, but check the results
> and make sure what you have is correct. What you may need to do is run a CA
> to set the Codebase value in the registry for the installed COM .NET
> assembly.. The value regasm puts in the .REG file will not be value for the
> install.
>
> Regards,
> greenaj
>
>
> Elfe Xu wrote:
> > Hi,
> >
> > I'm trying a CA
> > Execute="immediate" />
> > and found it can only success if I make the CA run after
> InstallFinalized. Otherwise, it will fail.
> >
> > I think the right way is to use Class element, but I just cannot make the
> result the same as I execute regasm.exe.
> > Here is my trying:
> > Guid="D75C79A1-83C9-467D-89FB-4B7E081401CE" Win64="$(var.USEWIN64)" >
> > Source="..\..\TestCOM.dll" KeyPath="yes">
> > > Description="test com"
> > ThreadingModel="both"
> > Context="InprocServer32"
> >
> >
> >
> >
> > I just cannot find way to set lots of other stuffs, like
> > Implemented Categories with value {62C8FE65-4EBB-45e7-B440-6E39B2CDBF29}
> > The Assembly, Class, RuntimeVersion under InprocServer32.
> > I want to set the ForeignServer with mscoree.dll, but wix says it cannot
> be used under .
> >
> > I guess I might doing totally wrong. Anyone can give me a sample of how
> to do the register?
> >
> > Another question is: when I want to add the .net assembly into wix
> project reference, why I get the error of "Test.dll could not be added.
> Please make sure that the file is accessible, and that it is a valid WiX
> reference." Because of this failure, I can only add the file by the relevant
> path. Not sure if it is a cause of the register failure.
> >
> > Thanks,
> > -Elfe
> >
> --
> > 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
>
>
>
> --
> 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
>
>
>
>
>
>
> --
> 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
>
--
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:
Re: [WiX-users] KeyPath problem that I do not understand
Hello Bob,
good to know! This leaves me 3 questions:
1) Did you see that I attached another error case to my bug report? It
may have the same root cause, but it look different from my "black-box
view".
2) Is there a chance this gets backported to V3.0 "SP1"? (nightly/weekly build)
3) Is it OK to use V3.5 for production setups as long as I don't use
burn? In other words, is the MSI generation part still stable
(enough)?
Thank you for your time!
Dirk
On Thu, Sep 17, 2009 at 18:05, Blair wrote:
> I noticed (looking last night for something else) that this is fixed in
> v3.5.
>
> -----Original Message-
> From: Dirk Ziegelmeier [mailto:d...@ziegelmeier.net]
> Sent: Thursday, September 17, 2009 5:42 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] KeyPath problem that I do not understand
>
> Hello Bob!
>
> done: Bug Id: 2860637
>
> Thank you for your quick reply! I created a minimal file that
> reproduces the problem and attached it to the bug.
>
> For everyone who is interested:
>
>
>
> Manufacturer='ACME'
> UpgradeCode="{C55F30AA-8323-4ED0-AB2C-18C65F70C26B}">
>
> Comments="Cool ACME Product"
> Manufacturer="ACME" InstallerVersion="200"
> InstallPrivileges='elevated'
> InstallScope='perMachine' />
>
>
>
>
> Name='ACMEProduct'>
>
> Id="SomeComponent" Guid="*">
> Root="HKLM" Key="Software\ACME" Action="create">
>
> Type="string" KeyPath="yes"/>
>
> Type="string" />
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Dirk
>
>
> On Thu, Sep 17, 2009 at 11:52, Bob Arnson wrote:
>> Dirk Ziegelmeier wrote:
>>> The line causing the error is ">> Name="[MergeRedirectFolder]ConstantNameB"..." so the problem seems to
>>> be the property substitution in there.
>>> *** But this RegistryValue is NOT the KeyPath of the component! ***
>>>
>>
>> Please file a bug at SourceForge.
>>
>> --
>> sig://boB
>> http://joyofsetup.com/
>>
>>
>>
>>
>
> --
>> Come build with us! The BlackBerry® 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/devconf
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>
>
> --
> Come build with us! The BlackBerry® 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/devconf
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
> Come build with us! The BlackBerry® 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/devconf
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Come build with us! The BlackBerry® 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/devconf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] KeyPath problem that I do not understand
Hello Bob! done: Bug Id: 2860637 Thank you for your quick reply! I created a minimal file that reproduces the problem and attached it to the bug. For everyone who is interested: Dirk On Thu, Sep 17, 2009 at 11:52, Bob Arnson wrote: > Dirk Ziegelmeier wrote: >> The line causing the error is "> Name="[MergeRedirectFolder]ConstantNameB"..." so the problem seems to >> be the property substitution in there. >> *** But this RegistryValue is NOT the KeyPath of the component! *** >> > > Please file a bug at SourceForge. > > -- > sig://boB > http://joyofsetup.com/ > > > > -- > Come build with us! The BlackBerry® 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/devconf > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Come build with us! The BlackBerry® 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/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] KeyPath problem that I do not understand
Hello again, my code fragment can even be simplified (no need for two "RegistryKey" entries): Dirk -- Come build with us! The BlackBerry® 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/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] KeyPath problem that I do not understand
Hello all, I have the following code fragment in my merge module (Notice: Guid="*"): The fragment above works. However, if I include the line that is commented out above, I get the following error: error LGHT0230 : The Component/@Guid attribute's value '*' is not valid for this component because it does not meet the some of the criteria for having an automatically generated guid. Only components with no ODBCDataSource child elements and either exactly one file which is the key path or no files and a registry with no Property substitutions as the key path may use an automatically generated guid. The line causing the error is "http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setup upgrade needs to care for 4th part of version number
Hello Neil, thank you - I didn't find this one. It is not perfect, but sufficiently good :-). If someone can tell me the perfect solution, I'm still open to it. Thanks again! Dirk On Mon, Jul 13, 2009 at 12:00, Neil Sleightholm wrote: > I had a similar problem the way I got round it was to set the upgrade code > to include the maximum version, e.g. UpgradeVersion/@IncludeMaximum="yes". > This will generate an ICE61 which you will need to ignore. This isn't > perfect as 1.2.3.4 will be downgraded by 1.2.3.3 but if you are sure two > releases with the same 3 part number will never go live you should be ok. > > If you search back through the list you should find a discussion about > doing this. > > Neil > > Neil Sleightholm > X2 Systems Limited > n...@x2systems.com <mailto:n...@x2systems.com> > > > > > From: Dirk Ziegelmeier [mailto:d...@ziegelmeier.net] > Sent: Mon 13/07/2009 12:42 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Setup upgrade needs to care for 4th part of version > number > > > > Hello All, > > due to political issues (see below) my setups need to be able to upgrade > when only the 4th part of the version info changes. > > Example: V1.0.0.1 needs to upgrade V1.0.0.0. My installers always do major > upgrades, the product GUI always changes (that is OK and not an issue to > discuss). > > After a lot of googeling, my idea is to write a custom action that can to > the version comparision, but then I need to tell MSI somehow at runtime > that > this run is an upgrade - how can I do that? > > Is there another (better?) way to achieve this? > > > Thank you in advance > Dirk > > PS: Political issue explanation: We label Major.Minor.Bugfix.SvnRevision. > During the development phase only the SVN revision will increase. My bosses > install the setups on their PCs and do not always want to uninstall by hand > before installing a new Setup... > > -- > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > -- > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Setup upgrade needs to care for 4th part of version number
Hello All, due to political issues (see below) my setups need to be able to upgrade when only the 4th part of the version info changes. Example: V1.0.0.1 needs to upgrade V1.0.0.0. My installers always do major upgrades, the product GUI always changes (that is OK and not an issue to discuss). After a lot of googeling, my idea is to write a custom action that can to the version comparision, but then I need to tell MSI somehow at runtime that this run is an upgrade - how can I do that? Is there another (better?) way to achieve this? Thank you in advance Dirk PS: Political issue explanation: We label Major.Minor.Bugfix.SvnRevision. During the development phase only the SVN revision will increase. My bosses install the setups on their PCs and do not always want to uninstall by hand before installing a new Setup... -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
