[WiX-users] Installing multiple versions of the same product under the same upgrade code
Hi, I want to have multiple versions of the same product to live on the target machine at the same time. Each of them has its own installer. To have a common key for all versions I would like to share the upgrade code. From what I have learned so far, the upgrade code is good for a major upgrade that uninstalls the older version. But is it safe to use the same upgrade code for multiple versions without uninstalling the older ones? I have seen that Microsoft does it - among others - for the MSVC 2005 Redistributables. Does anyone have experiences with this? Thanks, Sven -- 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] Pass data into localization wxl file
Thanks again Bob. I looked at the docs for the Product element and it is not clear to me from this URL whether the Name property, for instance, is formatted or not: Product Element http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm If you know what marks a field as formatted please let me know, or if im looking at the wrong documentation, please let me know as well. Ta, Kristjan -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: 02 May 2012 03:50 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Pass data into localization wxl file On 28-Apr-12 17:03, Kristjan Laane wrote: Thanks for the info Bob - but what determines whether a localized string is formatted or not? Whether it appears in a field that's documented as being formatted. Many fields are but some are required to be string literals and aren't formatted, so properties aren't evaluated. I just tried $(sys.CURRENTDIR) and that is not evaluated either! That is a preprocessor variable; localization strings are processed much later than the preprocessor. -- 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 -- 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] Customising a bootstrapper theme
Indeed you were right. There was a mismatch between the wix sources and the wix build I had. Now everything works accordingly. Thanks again for your help. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customising-a-bootstrapper-theme-tp7501905p7519454.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] Bundle failing to build after upgrading to latest release (3.6.2823)
Working again with 3.6.2830.0. Cheers all, Palbinder Sandher Software Platform Engineer T:+44 (0) 141 945 8500 F:+44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: 02 May 2012 04:03 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bundle failing to build after upgrading to latest release (3.6.2823) On 30-Apr-12 11:10, Pally Sandher wrote: Unfortunately still happens with 3.6.2328.0. Heath's fix came in v3.6.2830.0. -- 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 -- 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] Installing multiple versions of the same product under the same upgrade code
You want an installer designed to use instance transforms. It can be tricky and a lot of authoring has to be done manually to make it all work, but I do have one installer that currently supports up to 16 instance transforms. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Sven Riede [mailto:sven.ri...@alliedvisiontec.com] Sent: Wednesday, May 02, 2012 2:07 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing multiple versions of the same product under the same upgrade code Hi, I want to have multiple versions of the same product to live on the target machine at the same time. Each of them has its own installer. To have a common key for all versions I would like to share the upgrade code. From what I have learned so far, the upgrade code is good for a major upgrade that uninstalls the older version. But is it safe to use the same upgrade code for multiple versions without uninstalling the older ones? I have seen that Microsoft does it - among others - for the MSVC 2005 Redistributables. Does anyone have experiences with this? Thanks, Sven -- 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 NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- 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] Adding paramater to msi that will set value in config file
Hi Wix Users, I'm trying to do what I would think would be pretty trivial and that is update a config file value based on a parameter passed into the msi. But when I try to do this, I keep getting the error : error CNDL0200 : The Component element contains an unhandled extension element 'util:XmlConfig'. Wix xmlns='http://schemas.microsoft.com/wix/2006/wi' xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; Component Id='DiskUtilQuery' Guid='6130f032-09e0-46c7-a8e0-cb38c238c0b0' File Id='DiskUtilRecorder.exe' Name='DiskUtilRecorder.exe' DiskId='1' Source='DiskUtilRecorder.exe' / File Id='DiskUtilRecorder.exe.config' Name='DiskUtilRecorder.exe.config' DiskId='1' Source='DiskUtilRecorder.exe.config' / util:XmlConfig Id=SetDataAccessWS File=[#DiskUtilRecorder.exe.config] Action=create ElementPath=/configuration/system.serviceModel/client/endpoint Node=value Value=[DATAACCESSWS] On=install / Myapp.exe.config client endpoint address=[my endpoint address] binding=basicHttpBinding bindingConfiguration=DataAccessServiceSoap contract=DataAccessWS.DataAccessServiceSoap name=DataAccessServiceSoap / What am I doing wrong? Thanks Charles -- 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 support for (gulp!) WinNT4
On 01-May-12 20:03, Bob Arnson wrote: See wix.chm on WIXUI_DONTVALIDATEPATH for how to skip validation. That sounds perfect Bob. Unfortunately, now when I build from the same source/toolset, the resulting MSI won't start at all. It gives error 1620 on WinNT4+SP6 (but works on newer OSes). This happens, of course, with or without your WIXUI_DONTVALIDATEPATH property. The schema is 200, and when built back in 2010 using the same source and toolset it worked up until the path validation. Is there anything I can do to determine exactly what caused MSIEXEC 2.00.2600.2 to reject the MSI file? The only ICE I get through Orca is ICE66: Complete functionality of the Shortcut table is only available with Windows Installer version 4.0. Your schema is 200. This is likely caused by the presence of the (empty) Display* and Description* columns. But I got that in the MSI file built in 2010 as well. Here is the short log that is generated by MSIEXEC 2.00.2600.2 on WinNT4+SP6: === Verbose logging started: 5/2/12 7:45:13 Build type: SHIP UNICODE 2.00.2600.02 Calling process: C:\WINNT\system32\msiexec.exe === MSI (c) (88:6F): Resetting cached policy values MSI (c) (88:6F): Machine policy value 'Debug' is 0 MSI (c) (88:6F): *** RunEngine: *** Product: rmcwin.msi *** Action: *** CommandLine: ** MSI (c) (88:6F): Note: 1: 2203 2: rmcwin.msi 3: -2147286779 MSI (c) (88:6F): MainEngineThread is returning 1620 === Verbose logging stopped: 5/2/12 7:45:13 === -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
http://www.netmarketshare.com/operating-system-market-share.aspx?qprid=11qp customb=0qptimeframe=Mqpsp=149qpnp=11 ^-- Source of my data in this message... That is something that has been bugging me too while reading this discussion. So my random thoughts on this topic of OS compatibility... The cryptic error originally reported by OP isn't good. We only support Windows XP SP3+ as well, but if the user double-clicks the bootstrapper / self-extracting EXE, they need to get a messaging saying they need XP - not some cryptic error that might turn a user away from our application. Unfortunately, with the way Visual C++ has been dumping support for older versions of Windows, it looks like we would need to retain an older Visual C++ compiler (or find a competing compiler) for the sole purpose of making our own custom bootstrapper that shows a reasonable error. What a pain! Would be nice if WiX prevented this piece of overhead... From that link, I would guess that Windows 2000 usage must be close to zero (lumped into the 2.51% Other category). I'm less worried about that. But there's still significant XP usage, and dumping support for pre-SP2 versions of XP is disturbing. How can the bootstrapper request the user to install SP3 if the bootstrapper itself requires SP2/SP3? From what I have read, the situation gets much worse with VS11 since it drops XP support completely. This is a problem, because apparently XP still has 46% of the market. I know many of our customers still use it. We can't drop support for it. VS11 is out of touch with reality in this respect. If bootstrappers and/or custom actions start requiring Vista+, we'd have to avoid the newer versions of WiX. We'll also have to avoid VS11 ourselves for the time being. The improvements in VS11 might not justify dropping support for a lot of our customers, if it turns out not to be realistic to ask them to upgrade. And the concerns I already outlined about bootstrappers not failing gracefully apply doubly-so here - even if XP drops to, say, 10% of the market and we decide to drop support, there's still enough out there that we need the bootstrapper to kindly request Vista+. It would be nice if XP suffered a precipitous drop in market share this year, but I doubt it. Hopefully it will go away soon. I suspect it will still be common for another 2 years until companies are forced to move away from it when MS finally kills support (or suffer the security liability from an unpatched/unsupported OS). Some people/companies tend to avoid change until their lack of planning forces them into it - and maybe MS dropping support will push them over the edge to get Win7/8. By then, VS12 would be coming down the pipeline, and companies like us would still be stuck on VS2010 or older due to XP compatibility concerns if we decide not to drop support for XP just yet. (XP is the energizer bunny or something... it keeps going and going. I can't remember another consumer OS version that has had such a long life cycle!) James -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, April 30, 2012 15:57 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application I agree with dropping support for Win2k but what is a shame is that running the exe doesn't display a more useful error message. I don't suppose there is anything that can be done to change this? Neil -- 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] Bundle fails on WIN2K machine .exe is not a valid Win32 application
I remain confused how this problem has arisen in the first place. WiX was (obviously) being compiled with versions of VS that support Win2K, Win XP. So what's changed? Windows XP hasn't changed under our feet. So that leaves WiX. What features of the newer versions of Windows and/or VS are so indispensable that they force WiX to be platform-dependent? Alex P.S. I'm happy to help restore backward comaptibility to the C++ parts of WiX but I would need someone else to do the same for the .net code; that's not my speciality. On 2 May 2012 18:50, James Johnston johnst...@inn-soft.com wrote: http://www.netmarketshare.com/operating-system-market-share.aspx?qprid=11qp customb=0qptimeframe=Mqpsp=149qpnp=11 ^-- Source of my data in this message... That is something that has been bugging me too while reading this discussion. So my random thoughts on this topic of OS compatibility... The cryptic error originally reported by OP isn't good. We only support Windows XP SP3+ as well, but if the user double-clicks the bootstrapper / self-extracting EXE, they need to get a messaging saying they need XP - not some cryptic error that might turn a user away from our application. Unfortunately, with the way Visual C++ has been dumping support for older versions of Windows, it looks like we would need to retain an older Visual C++ compiler (or find a competing compiler) for the sole purpose of making our own custom bootstrapper that shows a reasonable error. What a pain! Would be nice if WiX prevented this piece of overhead... From that link, I would guess that Windows 2000 usage must be close to zero (lumped into the 2.51% Other category). I'm less worried about that. But there's still significant XP usage, and dumping support for pre-SP2 versions of XP is disturbing. How can the bootstrapper request the user to install SP3 if the bootstrapper itself requires SP2/SP3? From what I have read, the situation gets much worse with VS11 since it drops XP support completely. This is a problem, because apparently XP still has 46% of the market. I know many of our customers still use it. We can't drop support for it. VS11 is out of touch with reality in this respect. If bootstrappers and/or custom actions start requiring Vista+, we'd have to avoid the newer versions of WiX. We'll also have to avoid VS11 ourselves for the time being. The improvements in VS11 might not justify dropping support for a lot of our customers, if it turns out not to be realistic to ask them to upgrade. And the concerns I already outlined about bootstrappers not failing gracefully apply doubly-so here - even if XP drops to, say, 10% of the market and we decide to drop support, there's still enough out there that we need the bootstrapper to kindly request Vista+. It would be nice if XP suffered a precipitous drop in market share this year, but I doubt it. Hopefully it will go away soon. I suspect it will still be common for another 2 years until companies are forced to move away from it when MS finally kills support (or suffer the security liability from an unpatched/unsupported OS). Some people/companies tend to avoid change until their lack of planning forces them into it - and maybe MS dropping support will push them over the edge to get Win7/8. By then, VS12 would be coming down the pipeline, and companies like us would still be stuck on VS2010 or older due to XP compatibility concerns if we decide not to drop support for XP just yet. (XP is the energizer bunny or something... it keeps going and going. I can't remember another consumer OS version that has had such a long life cycle!) James -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, April 30, 2012 15:57 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application I agree with dropping support for Win2k but what is a shame is that running the exe doesn't display a more useful error message. I don't suppose there is anything that can be done to change this? Neil -- 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 -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org) -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape
Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid Win32 application
The problem surfaced when I started bundling my MSI packages in order to take advantage of bootstrapping the perquisites like .NET Framework 2.0 SP2, C++ run time libraries. We've been careful to build all of our client adapters in .NET 2.0/VS2008 since WIN2K is still widely used in the retail world - we have a number of customers that have a mix of XPE and WIN2K in a single store... So my WiX 3.6 MSI packages work just fine; it's the WiX 3.6 burn binaries that are embedded into the .EXE that are incapable with WIN2K. At this point I'm just copying both the bundle EXE and the MSI to my customer dropboxes. I'm just glad that I wrote all my custom actions in C# and not C++! Rich - Rich Dingle Accelitec, Inc. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-fails-on-WIN2K-machine-exe-is-not-a-valid-Win32-application-tp7507520p7521373.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] Registry permissions are not inherited
I'm having kind of the inverse problem. Setting an Everyone permission to a key and all of its values, propagates that permission upwards on the registry tree! The following RegistryKey Root='HKLM' Key='SOFTWARE\IMyRegistryFolder\MyKey' Action='createAndRemoveOnUninstall' Permission User='Everyone' GenericAll='yes'/ RegistryValue Type='string' Name='Name1' Value='Value1' Permission User='Everyone' GenericAll='yes'/ /RegistryValue /RegistryKey /RegistryKey Will set both keys: MyKey and MyRegistryFolder to have Everyone user with full control on. I've also tried declaring the keys separately with the same result. The oddest case I'm experiencing can be seen in the following example: RegistryKey Root='HKLM' Key='SOFTWARE\MyRegistryKey' Action='createAndRemoveOnUninstall' RegistryKey Key=Subkey1 Action='createAndRemoveOnUninstall' Permission User='Administrators' GenericAll='yes'/ RegistryKey Key=Subkey2 Action='createAndRemoveOnUninstall' Permission User='Everyone' GenericAll='yes'/ RegistryValue Type='string' Name='Name1' Value='Value1' Permission User='Everyone' GenericAll='yes'/ /RegistryValue /RegistryKey /RegistryKey/ /RegistryKey/ /RegistryKey In this case: - MyRegistryKey has Everyone user with full control - Subkey1 has Administrators use with full control (and does not have Everyone user) - Subkey2 has Everyone user with full control I'm using wix 3.5. Windows Installer 4. Is there anything wrong in what I'm doing? Thanks and regards 2011/8/8 James Johnston johnst...@inn-soft.com I replaced Permission with util:PermissionEx in the sample below. Unfortunately, ordinary users are still not allowed to write to MySubKey. An examination of the permissions in Registry Editor shows that entries were added to the existing ACL for MyFile. (i.e. the existing entries were not stepped on like the old Permission element did - a good thing). But they were set to only apply to the current key, and not to subkeys - no inheritance. An examination of the custom action code in secureobj.cpp shows ea.grfInheritance = NO_INHERITANCE if the object is not a folder/directory. Now this is with WiX 3.0 sources but I searched the tracker and apparently somebody else reported the same issue last year with WiX 3.5 and it hasn't been looked at yet: http://sourceforge.net/tracker/index.php?func=detailaid=3029343group_id=10 5970atid=642717http://sourceforge.net/tracker/index.php?func=detailaid=3029343group_id=105970atid=642717 Another similar ticket: https://sourceforge.net/tracker/index.php?func=detailaid=2612975group_id=1 05970atid=642717https://sourceforge.net/tracker/index.php?func=detailaid=2612975group_id=105970atid=642717 And one more: https://sourceforge.net/tracker/index.php?func=detailaid=1241592group_id=1 05970atid=642717https://sourceforge.net/tracker/index.php?func=detailaid=1241592group_id=105970atid=642717 And finally: https://sourceforge.net/tracker/index.php?func=detailaid=2991460group_id=1 05970atid=642714https://sourceforge.net/tracker/index.php?func=detailaid=2991460group_id=105970atid=642714 (all seem to be duplicates) In fact looking at the WiX 3.6 code shows this code is still unmodified and in place. So this explains why I still have issues with util:PermissionEx. It seems to me that the best solution would be to specify inheritance via attribute, just as the tracker suggests. I can't think of a workaround when using util:PermissionEx because subkeys created later by my application will not inherit the Everyone entry and so other users won't be able to read it... So this raises two questions: 1. Any good workaround to get things inheriting properly? 2. Any feedback on the previous feature requests? I notice that an active subscriber actually posted a patch. But this was 3 years ago; it seems it didn't go anywhere? See: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/PermissionEx-e nhancements-wix-Bugs-2127236-2016138-td1303935.htmlhttp://windows-installer-xml-wix-toolset.687559.n2.nabble.com/PermissionEx-enhancements-wix-Bugs-2127236-2016138-td1303935.html Also see a follow-up: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chnaged-to-Cod y-Cutrer-s-SecureObjects-enhancements-tt1563118.htmlhttp://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chnaged-to-Cody-Cutrer-s-SecureObjects-enhancements-tt1563118.html I was originally thinking of offering to implement this feature as I would like to see this happen, but after seeing that somebody else already did and nothing really seemed to happen with it - I am not sure if that would be worth my time. (Also I have no idea what is involved with contributing to WiX - I haven't been able to find a web page describing how this process works for WiX - many open source projects have an entire page
Re: [WiX-users] Prevent Downgrade without any message prompt
Thanks, Rob. WixExitEarlyWithSuccess meets the requirements. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Prevent-Downgrade-without-any-message-prompt-tp7505576p7522108.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
