Re: [WiX-users] Allow Multiple Package Versions to Coexist, But Always Install Over Same Version?
You would need to calculate a guid using your version number to use as your ProductCode (such that the same version number always generates the same guid and different version numbers generate different guids). Either a hash-based guid generator or a V1-style guid, I would think. -Original Message- From: Haw Bin Chai [mailto:haw-bin.c...@tradeweb.com] Sent: Monday, December 21, 2009 3:11 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Allow Multiple Package Versions to Coexist, But Always Install Over Same Version? Hi all, New WiX user here. I'm creating an installer for a win32 side-by-side assembly. I'm like to fulfill the following requirements, and I haven't been able to find a solution: - Allow multiple installations to coexist, so long as their major or minor version numbers are different. - Installing the same version should always overwrite an existing installation of the same version (i.e. even if the contents are different) - Never allow multiple entries for the same version to appear in Add/Remove Programs. - Avoid having to update Product or Package Id's manually - either set them once, or have them be auto-generated. I've been playing around with using "*" for Product / Package Id's, as well as with the element, but I have not been able to achieve the desired effect. Is what I want possible? Haw-Bin --- The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Tradeweb reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Tradeweb e-mail system. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional installation of a feature
I have tried that but, it doesn't work. It seems that the MSI evaluates the feature condition during CostFinalize. As CostFinalize takes place before my UI sequence, so any property change has no effect on the install behavior. So, looking at other similar references, I took a different approach. I set my feature's default install level as '1' (i.e. to be installed). In the UI control, I am removing the feature depending on the property value: But curiously, if I do so, my installation starts failing. If I comment out the 'Remove' event statement above, it installs fine. But, it installs the feature too, that I don't want to install (as I have that feature's level set to 1). I am not sure why the ' To: "'General discussion for Windows Installer XML toolset.'" Sent: Monday, December 21, 2009 8:47 PM Subject: Re: [WiX-users] Conditional installation of a feature > Do not use 0 and 1 as values as 0 is recognizes as "uninitialized". > Have you tried strings like "yes" and "no"? > > Best regards, > Sebastian Brand > > Deployment consultant > E-Mail: sebast...@instyler.com > Blog: www.sebastianbrand.com > > > >> -Original Message- >> From: Sudripta Nandy [mailto:sudrip...@sarangsoft.co.in] >> Sent: Monday, December 21, 2009 15:11 >> To: wix-users@lists.sourceforge.net >> Subject: [WiX-users] Conditional installation of a feature >> >> Hi, >> I want to install a feature depending on the user's choice. I have a > property >> 'MYPROPERTY' whose default value is '0'. If the user checks a checkbox, I > am >> setting that property value to '1' and installing that feature. I have >> the >> feature element as below: >> >> >> >> >> >> MYPROPERTY = 0 >> >> >> >> >> The problem is that the feature is never getting installed. But, if I set > the >> default value of 'MYPROPERTY' as '1', it gets installed. >> >> >> Please let me know what am I doing wrong. >> >> >> >> Thanking You, >> With Regards, >> // Sudripta Nandy >> >> >> > > -- >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and > easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Clarification on the MSI security
If anybody can use the orca tool to edit a shipped MSI package, are we not compromising on the security of the installer database? Or is there any way i can make my MSI read only? - Andy MSI Developer Schneider Electric:working: -- View this message in context: http://n2.nabble.com/Clarification-on-the-MSI-security-tp4202247p4202247.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX, InstallShield and combining multiple MSIs
What you don't mention are the following: Which of the 21 MSIs are written in WiX (as opposed to InstallShield) and how many (of each) are written in older versions of each of those two toolsets. Will you be supplying your own UI binary (a bootstrapper) or will you be attempting to combine the various UIs of each of those 21 MSIs (using Windows Installer UI)? How complicated is the UI of any of those 21 MSIs? -Original Message- From: Carter, Patrick [mailto:patrick.car...@stryker.com] Sent: Monday, December 21, 2009 5:47 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX, InstallShield and combining multiple MSIs I have a question regarding WiX and the referenced installation tools. I am not a Windows Installer expert (I am not even sure if you could call my skill level a newbie!), but I have been tasked with a project and I need to get up to speed fast. The question is likely very easy: I have an installation that requires several prerequisites (.NET 3.5 SP1, Microsoft WSE 3.0, 64-bit OS, etc...) The previous development team (almost all of who are gone) built 21 MSI files for each "Feature" each MSI having multiple "components" This currently gives us a night mare for version control, patches, etc... I have been tasked with building a CD-based "install" that check the pre-reqs (this I can do) and get all these MSI's into one install so they can be selected and de-selected as "features". What is the fastest and most reliable way to do that (assuming the original expertise from the guy who wrote the WiX script that builds the MSI's is gone)? Thanks for any help pointing me in the right direction. I have the latest Wix toolset, Visual Studio 2005 and 2008 and InstallShield 2010 as my tools. Patrick Carter -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX, InstallShield and combining multiple MSIs
I have a question regarding WiX and the referenced installation tools. I am not a Windows Installer expert (I am not even sure if you could call my skill level a newbie!), but I have been tasked with a project and I need to get up to speed fast. The question is likely very easy: I have an installation that requires several prerequisites (.NET 3.5 SP1, Microsoft WSE 3.0, 64-bit OS, etc...) The previous development team (almost all of who are gone) built 21 MSI files for each "Feature" each MSI having multiple "components" This currently gives us a night mare for version control, patches, etc... I have been tasked with building a CD-based "install" that check the pre-reqs (this I can do) and get all these MSI's into one install so they can be selected and de-selected as "features". What is the fastest and most reliable way to do that (assuming the original expertise from the guy who wrote the WiX script that builds the MSI's is gone)? Thanks for any help pointing me in the right direction. I have the latest Wix toolset, Visual Studio 2005 and 2008 and InstallShield 2010 as my tools. Patrick Carter -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RegistrySearch execution
The documentation indicates that it happens during AppSearch (http://msdn.microsoft.com/en-us/library/aa367578(VS.85).aspx) - RegistrySearch elements map to the RegLocator table in the MSI. > The AppSearch action searches for signatures using the CompLocator table > first, the RegLocator table second, the IniLocator table third, and finally > the > DrLocator table. File signatures are listed in the Signature table. A > signature > that is not in the Signature table denotes a directory and the action sets the > property to the directory path for that signature. Sascha On Tue, Dec 22, 2009 at 10:01 AM, Kevin Garman wrote: > Hi, > > Can anyone tell me when the RegistrySearches are evaluated in terms of > InstallUISequence and InstallExecuteSequence actions? For some reason I > was thinking it happens during AppSearch but now I can find evidence of > that. > > Thanks, > Kevin > -- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Allow Multiple Package Versions to Coexist, But Always Install Over Same Version?
Hi all, New WiX user here. I'm creating an installer for a win32 side-by-side assembly. I'm like to fulfill the following requirements, and I haven't been able to find a solution: - Allow multiple installations to coexist, so long as their major or minor version numbers are different. - Installing the same version should always overwrite an existing installation of the same version (i.e. even if the contents are different) - Never allow multiple entries for the same version to appear in Add/Remove Programs. - Avoid having to update Product or Package Id's manually - either set them once, or have them be auto-generated. I've been playing around with using "*" for Product / Package Id's, as well as with the element, but I have not been able to achieve the desired effect. Is what I want possible? Haw-Bin --- The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Tradeweb reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Tradeweb e-mail system. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] RegistrySearch execution
Hi, Can anyone tell me when the RegistrySearches are evaluated in terms of InstallUISequence and InstallExecuteSequence actions? For some reason I was thinking it happens during AppSearch but now I can find evidence of that. Thanks, Kevin -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows installer problems when users choose install directory.
Hey Rob, I think I know what you're referring to. The ICE57 error comes up if you mix per machine and per user data, however this wasn't happening with the registrykey I was setting for the unadvertised shortcuts. Thanks for the input though! Rob Mensching-7 wrote: > > Where was the File installed? If it was to a per-machine location then > mixing in per-user stuff (like HKCU registry key) can create interesting > behaviors. Sorry, I don't remember more specifics but I know there is an > ICE > that complains about it. Maybe that will lead to a trail... > > On Thu, Dec 17, 2009 at 10:11 AM, XorPtr wrote: > >> >> Hey! I think I was able to finally solve this issue which also related so >> other issues with alternate patching not working. The reason for all the >> trouble seemed to be the use of RegistryKey entries for non advertised >> shortcuts in the related components. Original wix for example: >> >> >> > Source="$(var.PATH)\Filename.exe"> >>> Name="File >> Name" WorkingDirectory="directoryBin"> >> >> > Key="Software\Product\NamedDirectory\Uninstall"> >> >> >> >> >> To fix the problem I had to remove the registrykey and set the shortcut >> as >> advertised as follows: >> >> >> > Source="$(var.PATH)\Filename.exe"> >>> Name="File >> Name" WorkingDirectory="directoryBin" Advertise="yes"> >> >> >> >> In case anyone else out there has a similar issue, after making this >> change >> everything worked fine! >> >> >> XorPtr wrote: >> > >> > This is actually another cry for help on what's probably a related >> issue >> > with installing a patch when users install to an alternate directory. >> The >> > original issue was that when patching our product the patch only works >> > when the user installs to the default directory, if they choose their >> own >> > the patch does not work. The result of this was due to the patched >> files >> > installing into the default directory rather than the install >> directory. >> > Upon further investigation the same issue also occurs when repairing >> the >> > product if it is installed to a different directory. Removing the >> product >> > has a similar issue in not removing the files unless they're in the >> > default directory. At this point I'm confident the problem goes beyond >> > the patch and I'm making a basic mistake with the windows installer, >> but >> I >> > have no idea what I'm doing wrong. >> > >> > Thanks in advance! >> > >> > Big Jim. >> > >> >> -- >> View this message in context: >> http://n2.nabble.com/Windows-installer-problems-when-users-choose-install-directory-tp4141782p4182655.html >> Sent from the wix-users mailing list archive at Nabble.com. >> >> >> -- >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> > > > -- > virtually, Rob Mensching - http://RobMensching.com LLC > -- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://n2.nabble.com/Windows-installer-problems-when-users-choose-install-directory-tp4141782p4199708.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Security problem with installed shortcut
We have an odd behavior with our 2 Applications that are installed via WiX. Even though the Desktop shortcut is stored in the All Users\Desktop folder, it behaves differently for administrators that it does for normal users. For Administrators, it has a Target Type of "Application". For all other users, it has a target type of "Application (install on first usage)". I have tried changing the ALLUSERS flag to 0,1 and 2 to no effect. My desktop shortcut tag is similar to the following: Any idea on why this is happening? Kent -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action .net dll referring signed assembly
Hello, Sorry for the late reply. The dll is signed before the reference was created in the CA. Does it make a difference? We tried one more thing. We manually added the signed dll into GAC before running the installer, then it worked just fine. Is it a right / recommended approach? If so I can try create one more custom action to install the signed dll into GAC just before executing this particular custom action and remove the dll at the end of the installation. Please let me know. Thanks Ranganatha On Fri, Dec 4, 2009 at 12:39 PM, Blair wrote: > In your build, was it signed before the reference was created in your CA > project, or after? > > -Original Message- > From: Ranganatha H C [mailto:ranganatha...@gmail.com] > Sent: Thursday, December 03, 2009 9:32 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Custom Action .net dll referring signed assembly > > Hey, > > Thanks for the response. > > The dll is not signed with the certificate; Its signed with a private key. > > The custom action is a immediate custom action , scheduled after a Next > button click in dialog which comes before install file path selection. > > Thanks > Ranganatha > > On Fri, Dec 4, 2009 at 12:02 AM, Wilson, Phil > wrote: > > > If you mean certificate signed, Windows is going to try to verify the > > signature by going to the internet to validate it. This may be something > to > > do with the error. Where is the CA sequenced? > > > > Phil Wilson > > > > > > -Original Message- > > From: Ranganatha H C [mailto:ranganatha...@gmail.com] > > Sent: Thursday, December 03, 2009 7:01 AM > > To: General discussion for Windows Installer XML toolset. > > Subject: [WiX-users] Custom Action .net dll referring signed assembly > > > > Hey All, > > > > We have a signed .net assembly, it has some functionality(e.g, validate > > license key .. etc) > > > > While installing the application we need to validate the user entered > > license key. For this to happen we have create a WIX Custom Project , > which > > refers the our signed .net assembly. The custom action inside this , call > > the method on the license key to validate. > > > > But since , the assembly is signed , I always get a the below error > > > > *The installer has encountered an unexpected error installing this > package. > > This may indicate a problem with this package. The error code is 2896. > The > > arguments are: ValidateLicense'* > > > > > > After a call to custom action. > > > > > > How can we resolve it. > > > > > > But If I use the un-signed dll and reference it in the custom action > > project > > everything works fine. > > > > > > Any idea what I am missing. > > > > > > Thanks in advance > > > > Ranganatha > > ** > > > > > > > -- > > Join us December 9, 2009 for the Red Hat Virtual Experience, > > a free event focused on virtualization and cloud computing. > > Attend in-depth sessions from your desk. Your couch. Anywhere. > > http://p.sf.net/sfu/redhat-sfdev2dev > > ___ > > 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 > > Portland House, Bressenden Place, London, SW1E 5BF (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 7821 3848 or e-mail > > inet.hqhelpd...@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). > > > > > > > > > > > > > -- > > Join us December 9, 2009 for the Red Hat Virtual Experience, > > a free event focused on virtualization and cloud computing. > > Attend in-depth sessions from your desk. Your couch. Anywhere. > > http://p.sf.net/sfu/redhat-sfdev2dev > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.
Re: [WiX-users] Conditional installation of a feature
Do not use 0 and 1 as values as 0 is recognizes as "uninitialized". Have you tried strings like "yes" and "no"? Best regards, Sebastian Brand Deployment consultant E-Mail: sebast...@instyler.com Blog: www.sebastianbrand.com > -Original Message- > From: Sudripta Nandy [mailto:sudrip...@sarangsoft.co.in] > Sent: Monday, December 21, 2009 15:11 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Conditional installation of a feature > > Hi, > I want to install a feature depending on the user's choice. I have a property > 'MYPROPERTY' whose default value is '0'. If the user checks a checkbox, I am > setting that property value to '1' and installing that feature. I have the > feature element as below: > > > > > > MYPROPERTY = 0 > > > > > The problem is that the feature is never getting installed. But, if I set the > default value of 'MYPROPERTY' as '1', it gets installed. > > > Please let me know what am I doing wrong. > > > > Thanking You, > With Regards, > // Sudripta Nandy > > > -- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditional installation of a feature
Hi, I want to install a feature depending on the user's choice. I have a property 'MYPROPERTY' whose default value is '0'. If the user checks a checkbox, I am setting that property value to '1' and installing that feature. I have the feature element as below: MYPROPERTY = 0 The problem is that the feature is never getting installed. But, if I set the default value of 'MYPROPERTY' as '1', it gets installed. Please let me know what am I doing wrong. Thanking You, With Regards, // Sudripta Nandy -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action .net dll referring signed assembly
Hello, Sorry for the late reply. The dll is signed before the reference was created in the CA. Does it make a difference? We tried one more thing. We manually added the signed dll into GAC before running the installer, then it worked just fine. Is it a right / recommended approach? If so I can try create one more custom action to install the signed dll into GAC just before executing this particular custom action and remove the dll at the end of the installation. Please let me know. Thanks Ranganatha On Fri, Dec 4, 2009 at 12:39 PM, Blair wrote: > In your build, was it signed before the reference was created in your CA > project, or after? > > -Original Message- > From: Ranganatha H C [mailto:ranganatha...@gmail.com] > Sent: Thursday, December 03, 2009 9:32 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Custom Action .net dll referring signed assembly > > Hey, > > Thanks for the response. > > The dll is not signed with the certificate; Its signed with a private key. > > The custom action is a immediate custom action , scheduled after a Next > button click in dialog which comes before install file path selection. > > Thanks > Ranganatha > > On Fri, Dec 4, 2009 at 12:02 AM, Wilson, Phil > wrote: > > > If you mean certificate signed, Windows is going to try to verify the > > signature by going to the internet to validate it. This may be something > to > > do with the error. Where is the CA sequenced? > > > > Phil Wilson > > > > > > -Original Message- > > From: Ranganatha H C [mailto:ranganatha...@gmail.com] > > Sent: Thursday, December 03, 2009 7:01 AM > > To: General discussion for Windows Installer XML toolset. > > Subject: [WiX-users] Custom Action .net dll referring signed assembly > > > > Hey All, > > > > We have a signed .net assembly, it has some functionality(e.g, validate > > license key .. etc) > > > > While installing the application we need to validate the user entered > > license key. For this to happen we have create a WIX Custom Project , > which > > refers the our signed .net assembly. The custom action inside this , call > > the method on the license key to validate. > > > > But since , the assembly is signed , I always get a the below error > > > > *The installer has encountered an unexpected error installing this > package. > > This may indicate a problem with this package. The error code is 2896. > The > > arguments are: ValidateLicense'* > > > > > > After a call to custom action. > > > > > > How can we resolve it. > > > > > > But If I use the un-signed dll and reference it in the custom action > > project > > everything works fine. > > > > > > Any idea what I am missing. > > > > > > Thanks in advance > > > > Ranganatha > > ** > > > > > > > -- > > Join us December 9, 2009 for the Red Hat Virtual Experience, > > a free event focused on virtualization and cloud computing. > > Attend in-depth sessions from your desk. Your couch. Anywhere. > > http://p.sf.net/sfu/redhat-sfdev2dev > > ___ > > 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 > > Portland House, Bressenden Place, London, SW1E 5BF (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 7821 3848 or e-mail > > inet.hqhelpd...@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). > > > > > > > > > > > > > -- > > Join us December 9, 2009 for the Red Hat Virtual Experience, > > a free event focused on virtualization and cloud computing. > > Attend in-depth sessions from your desk. Your couch. Anywhere. > > http://p.sf.net/sfu/redhat-sfdev2dev > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.n
Re: [WiX-users] Add multiple elements into xml with XmlConfig orXmlFile
Hi Alex, Thank you for response, but it seems to me that mail server blocked your attachment. Is it possible for you to upload it to some server? Again thank you! Igor -Original Message- From: Alex Shevchuk [mailto:shevc...@live.com] Sent: Saturday, December 19, 2009 9:19 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Add multiple elements into xml with XmlConfig orXmlFile Hi Igor, I've been having problems with Internet connection at home recently and I am sorry I don't have time to give you extended answer. What you want is easily doable and this is more of XPATH issue. Attached is my old document I wrote for my colleagues which may help you to understand how to target nodes with specific attributes. Let me know if you still need help. I am finally online, but it is my midnight now. Alex -Original Message- From: Igor Paniushkin [mailto:ipaniush...@sdl.com] Sent: Friday, December 18, 2009 2:24 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Add multiple elements into xml with XmlConfig or XmlFile Hi All, Is it possible to add multiple elements with XmlConfig or XmlFile actions? I mean that for example I have this xml: And I want to add element to all a elements with test equals to true, so in the end I want to receive such xml: Best Regards, Igor SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Tutorial: a minor issue in the Patchwork section
Thanks, forwarded. -- Yan -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, December 18, 2009 18:32 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] WiX Tutorial: a minor issue in the Patchwork section At the bottom of each page, the author's name is a hyperlink that opens a partially populated email message to compose (assuming your email client and your computer's browser are both setup for that). Here is that hyperlink: mailto:d...@tramontana.co.hu?subject=wixtutorial -Original Message- From: Yan Sklyarenko [mailto:y...@sitecore.net] Sent: Thursday, December 17, 2009 11:08 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WiX Tutorial: a minor issue in the Patchwork section Hello WiX community, I noticed a minor issue in the Patchwork section of the WiX tutorial. I don't know the place to register the issues for this, but I know that the author is reading this list ;) Here (http://www.tramontana.co.hu/wix/lesson4.php#4.3) the tutorial says: " A PatchFamily tag encompasses the items to be patched. Its DiskId has to be larger than any Media/@Id found in the installation packages and ..." But PatchFamily element doesn't have DiskId attribute. It is a Patch/Media element and the attribute is called just 'Id'. Well, it is clear what is meant here, but the people new to WiX and patching might get confused. :) Thanks, -- Yan -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
