Re: [WiX-users] building an msi in the same dir as source files?
I think what you need to add is -var var.SourceFiles; from the help file: -var VariableName Substitute File/@Source=SourceDir with a preprocessor or a wix variable (e.g. -var var.MySource will become File/@Source=$(var.MySource)\myfile.txt and -var wix.MySource will become File/@Source=!(wix.MySource)\myfile.txt. This will result in the File elements having the source folder set to a pre-processor variable, e.g.: File Id=fil8E5129A8454C2AA40A71DF50F7CD8484 KeyPath=yes Source=$(var.SourceFiles)\File1.exe / You can then set this a compile time. Neil -Original Message- From: Andrew Maxwell [mailto:andrew.maxw...@papercut.com] Sent: 18 May 2012 06:01 To: wix-users@lists.sourceforge.net Subject: [WiX-users] building an msi in the same dir as source files? Hi again all, My last post was a bit of a brain-dump, so I can boil my question down to a few points here: :) - using heat, is there a way to harvest a directory and suppress directory id/name insertion in the resulting .wxs? (when automating heat output , this is an annoyance) eg . heat.exe dir MyDirectory -gg -cg MyComponents -o output.wxs would generate something like: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=TARGETDIR *Directory Id=dir682EE88536E915B58CEC9559EC161A89 Name=MyDirectory* Component Id=cmp789AABFBE814C745D68B0EC1FE51DF26 . etc - I'm trying to build an installer where the .msi *sits in the same directory as the uncompressed source files*. However, if my dir structure looks like: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=APPLICATIONROOTDIRECTORY Name=MyApplication/ /Directory /Directory DirectoryRef Id=APPLICATIONROOTDIRECTORY ...components... /DirectoryRef This will happily install MyAppliation to Program Files/MyApplication however will require my msi to reside one level down, and expect the source files to be in a dir called MyApplication. Can anyone set me in the right direction? My process is something like this atm: heat dir AppSource -gg -sfrag -sreg -svb6 -scom -cg MainAppComps -o installer.wxs [modify heat .wxs] candle -out installer.wxsobj installer.wxs light -b AppSource -sl -spdb AppSource/installer.wxsobj -out AppSource/installer.msi Will create a .msi in the AppSource directory (good!), but when installed expects the files to reside in AppSource/MyApplication/ ! Sorry again for the double post. Any thoughts anyone? ps. if anyone's interested the reason for this seemingly bizarre project layout is the .msi exists purely to simplify deployment via a group policy. cheers, Andrew -- 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 -- 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] Launch an msi after installation
Hello, I created a wix installer in which I want to launch an msi after installation. I was trying using following code but it's not working. CustomAction Id=StartAppOnExit FileKey=Dlg_Setup.msi ExeCommand=param1 Execute=immediate Return=asyncNoWait / InstallExecuteSequence Custom Action='StartAppOnExit' After='InstallFinalize' / /InstallExecuteSequence Can anyone help me to do this. -- Warm Regards Vivek Soni vivek.s...@brisetech.com +91-7877127178 -- 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] Launch an msi after installation
Firstly to launch an msi you would need to use msiexec ( http://support.microsoft.com/kb/227091) you cannot call an msi directly as it is not an executable. However in your case this will not be possible as you are in a msi transaction already and won't be able to start a new one. You will need to use a bootstrapper to launch the two msi's one after the other. Take a look at Burn the Wix bootstrapper http://wix.sourceforge.net/manual-wix3/authoring_bundle_intro.htm *Richard Mayes* ***Blog:* http://blog.slinkysoftware.com *Twitter:* http://twitter.com/caveman_dick On 18 May 2012 09:17, Vivek Soni vivek.s...@brisetech.com wrote: Hello, I created a wix installer in which I want to launch an msi after installation. I was trying using following code but it's not working. CustomAction Id=StartAppOnExit FileKey=Dlg_Setup.msi ExeCommand=param1 Execute=immediate Return=asyncNoWait / InstallExecuteSequence Custom Action='StartAppOnExit' After='InstallFinalize' / /InstallExecuteSequence Can anyone help me to do this. -- Warm Regards Vivek Soni vivek.s...@brisetech.com +91-7877127178 -- 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 -- 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] light.exe error when merging VC100 merge modules for both x86 and x64
But you can install 64-bit dlls withoin a 32-bit package - they're just files. So, we add a dll that allows the 64-bit operating system to interogate our bespoke document formats in order to draw pretty thumbnail previews. But this code only works if the operating sytem has the required dependencies also installed. I cannot install my 32-bit application in a 64-bit package as it will not have it's registry in the expected virtualised area. I can install my single 64-bit dll within my 32-bit package though - just as I have time and time again. And I used to be able to include and distribute both 32-bit and 64-bit VC90 merge modules. This has only caused a problem when updating the VC90 merge modules with the VC100 equivelent. Bob, are you suggesting that Microsoft have deliberatly sabotaged their merge module behaviour in order to prevent what might be prceived as a hack in installations that is installing them both in a 32-bit package? If so then how can a 64-bit operating system interogate a bespoke file format in order to draw a thumbnail preview when it is installed as part of a 32-bit package? Cheers, G -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/light-exe-error-when-merging-VC100-merge-modules-for-both-x86-and-x64-tp7539587p7565612.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] light.exe error when merging VC100 merge modules for both x86 and x64
Hi Gareth, I install 32-bit applications in a 64-bit installer all the time. I use the Win64=no attribute on the 32-bit registry entries to ensure they go in the 32-bit hive on the 64-bit platform. Sincerely, Daniel Madill -Original Message- From: Gareth [mailto:gmor...@serif.com] Sent: May-18-12 11:32 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] light.exe error when merging VC100 merge modules for both x86 and x64 But you can install 64-bit dlls withoin a 32-bit package - they're just files. So, we add a dll that allows the 64-bit operating system to interogate our bespoke document formats in order to draw pretty thumbnail previews. But this code only works if the operating sytem has the required dependencies also installed. I cannot install my 32-bit application in a 64-bit package as it will not have it's registry in the expected virtualised area. I can install my single 64-bit dll within my 32-bit package though - just as I have time and time again. And I used to be able to include and distribute both 32-bit and 64-bit VC90 merge modules. This has only caused a problem when updating the VC90 merge modules with the VC100 equivelent. Bob, are you suggesting that Microsoft have deliberatly sabotaged their merge module behaviour in order to prevent what might be prceived as a hack in installations that is installing them both in a 32-bit package? If so then how can a 64-bit operating system interogate a bespoke file format in order to draw a thumbnail preview when it is installed as part of a 32-bit package? Cheers, G -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/light-exe-error-when-merging-VC100-merge-modules-for-both-x86-and-x64-tp7539587p7565612.html Sent from the wix-users mailing list archive at Nabble.com. -- 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 -- 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] service uninstall fails if ServiceControl does not specify install= ???
On 17-May-12 20:20, Dave Combs wrote: MSI (s) (9C:24) [17:03:39:948]: Component: CMP_162; Installed: Local; Request: Absent; Action: Null That usually indicates something else, expressed earlier in the log, is preventing the requested action, such as violating the component rules. Try it in a clean VM. -- sig://boB http://joyofsetup.com/ -- 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] Specifying source subdirectory
On 16-May-12 12:52, Martin Sustrik wrote: C:\Users\me\libxs\foo.wxs(98) : error LGHT0103 : The system cannot find the file 'foo.h'. See How To: Specify source files in wix.chm. -- sig://boB http://joyofsetup.com/ -- 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] MSI projects fail to build after upgrading to v3.6.2914.0
On 16-May-12 05:28, Pally Sandher wrote: Just don't need them. Never got around to using WiX only for patching so I don't see any use for them. There's nothing in WiX today that needs them, other than patching, but that might change; there's lots of good info that's pre-digested in a way that makes for easier tooling. -- sig://boB http://joyofsetup.com/ -- 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] light.exe error when merging VC100 merge modules for both x86 and x64
On 18-May-12 11:32, Gareth wrote: But you can install 64-bit dlls withoin a 32-bit package - they're just files. Not if they're marked as a 64-bit component that goes into a 64-bit part of the file system. Then they're special. then how can a 64-bit operating system interogate a bespoke file format in order to draw a thumbnail preview when it is installed as part of a 32-bit package? It can't. That requires a 64-bit package, as I said. The rules are that a 32-bit package can contain only 32-bit components but a 64-bit package can contain both 64-bit and 32-bit components. -- sig://boB http://joyofsetup.com/ -- 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] light.exe error when merging VC100 merge modules for both x86 and x64
Just to add the doc link: http://msdn.microsoft.com/en-us/library/windows/desktop/aa367451(v=vs.85).aspx Phil W From: Bob Arnson [b...@joyofsetup.com] Sent: Friday, May 18, 2012 9:13 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] light.exe error when merging VC100 merge modules for both x86 and x64 On 18-May-12 11:32, Gareth wrote: But you can install 64-bit dlls withoin a 32-bit package - they're just files. Not if they're marked as a 64-bit component that goes into a 64-bit part of the file system. Then they're special. then how can a 64-bit operating system interogate a bespoke file format in order to draw a thumbnail preview when it is installed as part of a 32-bit package? It can't. That requires a 64-bit package, as I said. The rules are that a 32-bit package can contain only 32-bit components but a 64-bit package can contain both 64-bit and 32-bit components. -- sig://boB http://joyofsetup.com/ -- 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 *** 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/en/legal/default.aspx. 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). -- 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] In .wixproj, default Build Configuration ignored or not settable?
It's my understanding that with MSBuild, the configuration and platform used when none are specified is defined near the top of the project file in the elements with blank conditions, like this: ?xml version=1.0 encoding=utf-8? Project ToolsVersion=4.0 DefaultTargets=Build xmlns=http://schemas.microsoft.com/developer/msbuild/2003; PropertyGroup *Configuration Condition= '$(Configuration)' == '' Debug/Configuration Platform Condition= '$(Platform)' == '' x86/Platform * This doesn't seem to be happening for a wixproj I have. I've added two new build configurations, and it keeps building one of those by default, called Debug SU. I want it to build Debug by default. I'm calling MSBuild from a script. Does anyone know how to have a specific configuration used by default when one isn't specified to MSBuild? I could add logic to check for this one solution and pass in a specific configuration, but that's a bit ugly if there is supposed to be a settable default. Thanks, - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/In-wixproj-default-Build-Configuration-ignored-or-not-settable-tp7565859.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Error when doing a REG_MULTI_SZ registry search within Burn.
Hi I've been trying to bootstrap Sql 2008 Express and install if required however my detection Registry search is failing with the following error: Error 0x80004001: Unsupported registry key value type. Type = '7' RegistrySearchValue failed: 'SOFTWARE\Microsoft\Microsoft SQL Server', HRESULT 0x8000400 If this a Burn RegistrySearch limitation? Or have I setup the search incorrectly? util:RegistrySearch Root=HKLM Key=SOFTWARE\Microsoft\Microsoft SQL Server Value=InstalledInstances Variable=SQLServerInstalled / I'm running the latest source on codeplex (3.6.2907) Thanks Richard -- 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] Error when doing a REG_MULTI_SZ registry search within Burn.
I believe you need to set the attribute RegistrySearch/@Type=raw to read REG_MULTI_SZ values, see http://wix.sourceforge.net/manual-wix2/wix_xsd_registrysearch.htm Neil -Original Message- From: Richard Mayes [mailto:caveman.d...@gmail.com] Sent: 18 May 2012 20:54 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Error when doing a REG_MULTI_SZ registry search within Burn. Hi I've been trying to bootstrap Sql 2008 Express and install if required however my detection Registry search is failing with the following error: Error 0x80004001: Unsupported registry key value type. Type = '7' RegistrySearchValue failed: 'SOFTWARE\Microsoft\Microsoft SQL Server', HRESULT 0x8000400 If this a Burn RegistrySearch limitation? Or have I setup the search incorrectly? util:RegistrySearch Root=HKLM Key=SOFTWARE\Microsoft\Microsoft SQL Server Value=InstalledInstances Variable=SQLServerInstalled / I'm running the latest source on codeplex (3.6.2907) Thanks Richard -- 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 -- 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] Error when doing a REG_MULTI_SZ registry search within Burn.
On 18-May-12 15:53, Richard Mayes wrote: Error 0x80004001: Unsupported registry key value type. Type = '7' RegistrySearchValue failed: 'SOFTWARE\Microsoft\Microsoft SQL Server', HRESULT 0x8000400 Like MSI, Burn doesn't support getting the value of a multi-sz string. However, if all you want to do is check whether the registry value exists, use @Result=exists. -- sig://boB http://joyofsetup.com/ -- 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] CheckBox Value via Custom Action
Any suggestions???
On Tue, May 15, 2012 at 11:49 AM, Ravi Raj raviraj.callin...@gmail.comwrote:
I have done this thing:
Property Id=ENABLEVIRTUALIZATION Secure=yes /CustomAction
Id=CA_SetProperty_EV Property=ENABLEVIRTUALIZATION Value=0
Execute=firstSequence /
InstallExecuteSequence Custom Action=CA_SetProperty_EV
Before=AppSearchNOT Installed AND NOT
OLDERVERSIONDETECTED/Custom/InstallExecuteSequenceInstallUISequence
Custom Action=CA_SetProperty_EV Before=AppSearchNOT Installed AND NOT
OLDERVERSIONDETECTED/Custom/InstallUISequence
Now when chkbox is disabled, the registry stored value=0 (which is
correct). Again, when I click Verify button (some action performed) and
chkbox gets enabled (and its checked by default even in disabled state) but
still i found registry value to be 0 but actually it should be one.
why is this strange behavior?
On Mon, May 14, 2012 at 7:38 PM, Ravi Raj raviraj.callin...@gmail.comwrote:
I need to perform certain action on my checkbox.
At the start if the installation the chkbox is disabled. There is a
button to call a custom action and verify certain things and assign a value
to a variable.
This variable will decide whether to enable chkbox or not. I have
implemented till this part:
Control Id=ImportCheckBoxType=CheckBoxCheckBoxValue=1
X=35 Y=100Width=160 Height=20Disabled=yes
Text=!(loc.Virtual_ChkBox) Property=ENABLEVIRTUAL Condition
Action=enable![CDATA[INTEGRATED = 1]]/Condition Condition
Action=disable![CDATA[INTEGRATED = 0]]/Condition/Control
So as soon as I launch the installer, the chkbox is disabled and
unchecked. If Verify is OK then its became enable but still unchecked.
Suppose a user does not check this box and proceeds with installation then
what vale gets stored in registry (I am storing this value ENABLEVIRTUALto
registry).
If empty gets stored then it will give error while performing repair or
uninstall. How can I store this value?
Again,
In custom action i have used a string null or empty chk (obtained from
previous installer dialog), if not null then verify works else it give
throw exception:
[CustomAction]
public static ActionResult Check(Session mpSession)
{
mpSession.Log(Begin CustomActions.Check);
String sServerName =
GetSetProperties.GetSessionProperty(mpSession, INSTALLMACHINE, false);
if (!String.IsNullOrEmpty(sServerName))
{
try
{
//Something
GetSetProperties.SetSessionProperty(mpSession,
INTEGRATED, packs.Count != 1 ? 0 : 1);
}
catch (Exception oException)
{
HandleException(mpSession, oException);
return ActionResult.Failure;
}
}
else
{
throw new Exception(SDK Service Machine cannot be empty.);
}
return ActionResult.Success;
}
private static void HandleException(Session mpSession, Exception ex)
{
string errorMsg = Exception during custom action execution: +
ex.ToString();
mpSession.Log(errorMsg);
mpSession.Message(InstallMessage.Error, new Record {
FormatString = errorMsg });
}
Here in this code Catch, else and HandleException are not working
properly and the installer gets interrupted in between. How can I fix this?
Some working code will be very useful as I am new to WiX.
--
Thanks and Regards,
Ravi Raj
--
Thanks and Regards,
Ravi Raj
--
Thanks and Regards,
Ravi Raj
--
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
