[WiX-users] Killing a task on Windows 2000 and WinXP
Hello, I want to kill a task on both WinXP and Win2000. I wrote custom action for that. Using custom action i am invoking taskkill.exe command. But my problem is winXP has taskkill.exe in system folder win2000 doesn't. Win2000 has kill.exe. How I can manage this situation. Thanks Veerendra Regards, Veerendra Gangwar M +91 94 486 88537 - Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Handling Feature Dependencies
Okay. So what if the hidden fC actually contains a merge module (meaning, a MergeRef / element)? But I still don't want fC displayed in the interface anywhere. AFAIK, ComponentGroupRefs do not contain MergeRefs. Should I make fC an sub-Feature of fA and fB? Will it still be hidden from the interface if I do that? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, October 16, 2007 11:23 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Handling Feature Dependencies Thanks for the info guys. I will try these solutions and let you know how it goes. From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 16, 2007 1:10 AM To: John Hall Cc: Robert Priest; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Handling Feature Dependencies John Hall wrote: However, in hindsight, I think just using a ComponentGroupRef instead of feature fC and including it in both fA and fB might be simpler and more robust. Not sure what the relative downsides are. If the feature was used just for grouping (i.e., it's never visible or user installable) then a component group is the best approach. Components can belong to multiple features just fine -- that's an MSI thing. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename
I converted all my wx* files to utf-16 and saved them as Unicode with the same result. Thanks, Mike -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Szentpali Janos Sent: Friday, November 30, 2007 3:27 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename Schuett, Michael wrote: Hello, If I use an accented character in a Shortcut Name, the following error results... D:\WiX\ClientInstall\Application.wxs(39,0): Error LGHT0204: ICE03: Invalid Filename; Table: Shortcut, Column: Name, Key(s): TrayAppShortcut Here's the section from Application.wxs. File Id=Tray.exe Name=Tray.exe KeyPath=yes Source=ClientFiles\Tray.exe Shortcut Id=TrayAppShortcut Directory=ProgramGroupDir WorkingDirectory=INSTALLLOCATION Arguments=/EnableTray Name=Redémarrer le moniteur Icon=tray.ico Advertise=yes / /File If I remove the é from the Shortcut Name it builds successfully. Any suggestions? I'm using WiX 3.0.2925.0. Thanks, Mike -- --- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Try changing the encoding... put ?xml version='1.0' encoding='utf-8'? on the beginning of the .wxs file... or whatever encoding that is the one you are using -- Szentpáli János - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename
On Sat, 01 Dec 2007 00:38:21 +0200, Szentpali Janos wrote: János, :D... I have just noticed that. Like in the old DOS days. It is supposed to be there for backwards compatibility. I just don't know with what... Some Novell servers, where one or two people in the Universe might still want to place a network installation package, or so I was told... :-) Bye, Gábor --- DEÁK JAHN, Gábor -- Budapest, Hungary E-mail: [EMAIL PROTECTED] - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename
Schuett, Michael wrote: Hello, If I use an accented character in a Shortcut Name, the following error results... D:\WiX\ClientInstall\Application.wxs(39,0): Error LGHT0204: ICE03: Invalid Filename; Table: Shortcut, Column: Name, Key(s): TrayAppShortcut Here's the section from Application.wxs. File Id=Tray.exe Name=Tray.exe KeyPath=yes Source=ClientFiles\Tray.exe Shortcut Id=TrayAppShortcut Directory=ProgramGroupDir WorkingDirectory=INSTALLLOCATION Arguments=/EnableTray Name=Redémarrer le moniteur Icon=tray.ico Advertise=yes / /File If I remove the é from the Shortcut Name it builds successfully. Any suggestions? I'm using WiX 3.0.2925.0. Thanks, Mike - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Try changing the encoding... put ?xml version='1.0' encoding='utf-8'? on the beginning of the .wxs file... or whatever encoding that is the one you are using -- Szentpáli János - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename
Hello, If I use an accented character in a Shortcut Name, the following error results... D:\WiX\ClientInstall\Application.wxs(39,0): Error LGHT0204: ICE03: Invalid Filename; Table: Shortcut, Column: Name, Key(s): TrayAppShortcut Here's the section from Application.wxs. File Id=Tray.exe Name=Tray.exe KeyPath=yes Source=ClientFiles\Tray.exe Shortcut Id=TrayAppShortcut Directory=ProgramGroupDir WorkingDirectory=INSTALLLOCATION Arguments=/EnableTray Name=Redémarrer le moniteur Icon=tray.ico Advertise=yes / /File If I remove the é from the Shortcut Name it builds successfully. Any suggestions? I'm using WiX 3.0.2925.0. Thanks, Mike - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSCONFIG shows unknown for service manufacturer
Look again at my previous post - my vote is for an issue with msconfig. Look at the service paths for services where it doesn't work and I bet they have quoted paths. The ones that work fine do not have quoted paths. Windows Installer starting quoting service paths relatively recently. Your command line install doesn't quote the service path. When it's quoted msconfig apparently can fail to get the path to the executable properly to get the version info. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Richardson Sent: Thursday, November 29, 2007 6:54 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MSCONFIG shows unknown for service manufacturer There is very little doubt in my mind that msconfig is getting the company name from the resources of the code file (in the cases where it gets it right). For just one example, look at what msconfig says about the Logical Disk Administrator Service, and then look at the company name in the actual service code file. Not only that, but there are no Service-oriented APIs or registry entries about Services that let you specify the company name.=20 I completely agree with you that msconfig is supposed to grab the company name from the resources of the code file; the point of my post is that it's not doing that when I install the service through the ServiceInstall table. It only displays the company name if the service is self-registered from the command-line. I would assume that MSI invokes the CreateService API for entries in the ServiceInstall table, just as the self-registering code does, so I'm confused as to why it doesn't work. -kevin - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcut
Dhaval Patel wrote:
I think it is because you are not creating a 2nd level to start off with. I
use the following snippet in my packages all the time - you can use it as a
reference (credit goes to Rob. I think he blogged it a long time ago):
Directory Id=ProgramMenuFolder Name=PMFolder
Directory Id='ShortcutFolder' Name='MyUni' LongName='Acme
1.0'
Component Id='Shortcuts' Guid='
{MYGUID-6E17-41ef-8C7D-AAD2F355862D}'
Registry Root=HKCU Key=SOFTWARE\My
Company\MyProduct
Type=string KeyPath=yes Value=Uninstall/
Shortcut Id=UninstallProduct Name=unin.msi
LongName=Uninstall Acme 1.0
Target=[System64Folder]msiexec.exe
Arguments=/x [ProductCode]
Directory=ShortcutFolder
Description=Removes
Acme 1.0. /
RemoveFolder Id=RemoveShortcuts On=uninstall /
/Component
/Directory
/Directory
This snippet can sit immediately beneath your regular TARGETDIR element.
You'll need to reference the component in your feature tree. Hope this
helps.
On Nov 29, 2007 7:02 PM, Szentpali Janos [EMAIL PROTECTED] wrote:
Hi,
I have a setup that contains:
...
File
...
Shortcut
Directory='ProgramMenuFolder'
IconIndex='0'
Id='StartMenuShortcut'
LongName='Title of the program'
Name='Title'
WorkingDirectory='INSTALLDIR'
/
/File
...
What should i do for the shortdut to be created not in the Programs
Start menu folder, but in a subfolder of it?
I am very new to Wix and the documentation related to the Shortcut
element is empty :D. Thanks in advance.
--
Szentpáli János
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Thanks for the tip. It works fine now ;)
--
Szentpáli János
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Installation Deployment via Group Policy (GPO)
Hello,
I am trying to deploy a sample MSI package which simply installs a
text file to Program Files folder. The setup runs just fine if you run
it through double-clicking or via msiexec /i package.msi command line
interface (with the current user is being an administrator on that
computer). Then I have created a GPO for the domain that the computer
resides and added the MSI package as an Assignment to that user. So
when that user, who is a local admin on that computer, logins the
computer; the installation is deployed to that computer just fine. But
whenever I have removed that user's local admin privileges the MSI
package can not be deployed with these event log error records:
1)
Source : Userenv
Event ID : 1085
User : NT AUTHORITY\SYSTEM
Description: The Group Policy client-side extension Software
Installation failed to execute. Please look for any errors reported
earlier by that extension.
2)
Source : Application Management
Event ID : 108
User : DOMAIN\user.name
Description: Failed to apply changes to software installation
settings. Software changes could not be applied. A previous log
entry with details should exist. The error was : Access is denied.
3)
Source : Application Management
Event ID : 103
User : DOMAIN \user.name
Description: The removal of the assignment of application
{OurProductName} from policy {OurGroupPolicyName} failed. The error
was : The system cannot find the file specified.
4)
Source : Application Management
Event ID : 101
User : DOMAIN \user.name
Description: The assignment of application {OurProductName}
from policy {OurGroupPolicyName} failed. The error was : Access is
denied.
In a nutshell, both (manual and GPO-deployed) installations fail if
the running user is not an admin. Since a GPO-deployed installation is
granted by a domain administrator, I think there must be an option to
run that installation as a privileged user during a non-privileged
user's login.
Any help/pointer would be greately appreciated.
Hüseyin.
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] subset of compluscomponents
Hi all! I have received a com .dll (Server.dll) that I need to build an installer for. There are 2 main requirements on the Installer: 1. It should make the same registry entries as if running regsvr32 on the dll. 2. It should create a COM+ application for the dll and place a subset of its classes as components in the application. The first requirement was not hard to meet. I just used tallow to capture the reg-entries for the dll. This part works fine when I run the installer. The second reuirement was a bit harder to figure out. Right now I use the PUBCA extension to set up the com+ part. Server.dll consists of 10 classes, but only classes 1-3 should be created as components in the com+ application. My wix markup: Component Id=component418 DiskId=1 Guid=358E0BE2-86B2-4A23-8856-A692567BDC31 File Id=file466 Name=SERVER_1.DLL LongName=Server.dll KeyPath=yes Source=X:\My\Path\ToDLL\Server.dll / pca:ComPlusApplication Id=MyCOM Name=MyServer ApplicationAccessChecksEnabled=no pca:ComPlusAssembly Id=MyComPlusAssembly Type=native DllPath=[#file466] pca:ComPlusComponent Id=MyFirstClass CLSID=3FCE151B-C805-4AAD-A7B7-2B87F0F59CA9 / pca:ComPlusComponent Id=MySecondClass CLSID=3FCE151B-C805-4AAD-A7B7-2B87F0F59CA9 / pca:ComPlusComponent Id=MyThirdClass CLSID=3FCE151B-C805-4AAD-A7B7-2B87F0F59CA9 / /pca:ComPlusAssembly /pca:ComPlusApplication Registry Root=HKCR . registry entries below /Component This creates a an application, but all 10 of my classes are added as components. I thought that only the ComPlusComponents that I defined would be added. Is this correct? Btw Im using wix v2. Regards Tobias - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Not install Database during the reinstall
Another question here --- I need the application to be reinstalled but not the database. The CreateOnReinstall has already been set to NO, see my code below SqlDatabase Id=SqlDatabase Database=master Server=[ComputerName] Instance = '[SQLINSTANCE]' ConfirmOverwrite = yes CreateOnReinstall=no CreateOnInstall=yes DropOnUninstall=no ContinueOnError=yes SqlScript Id=CreateDB BinaryKey=CreateDB ExecuteOnReinstall= no ExecuteOnInstall=yes Sequence=1 / SqlScript Id=CreateSQLLogin BinaryKey=CreateSQLLogin ExecuteOnReinstall= no ExecuteOnInstall=yes Sequence=2 / SqlScript Id=CreateTable BinaryKey=CreateTable ExecuteOnReinstall= no ExecuteOnInstall=yes Sequence=3 / SqlScript Id=StoredPrec BinaryKey=StoredPrec ExecuteOnReinstall= no ExecuteOnInstall=yes Sequence=4 / SqlScript Id=GrantAccess BinaryKey=GrantAccess ExecuteOnReinstall= no ExecuteOnInstall=yes Sequence=5 / SqlScript Id=Initialize BinaryKey=Initialize ExecuteOnReinstall= no ExecuteOnInstall=yes Sequence=6 / /SqlDatabase But it still complains during the SQL Script execution : Error -2147217900: failed to execute SQL string, error detail: Database 'SYSQ' already exists. Choose a different database name., SQL key: CreateDB SQL string: DECLARE @SmoRoot NVARCHAR(512) EXEC[master].[dob].[xp_instance_regread] N'HKEY_LOCAL_MACHINE', ...\SYSQ_log.ldf',S... Any ideas? Anna ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ _ Telly addicts unite! http://www.searchgamesbox.com/tvtown.shtml- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deletion of sys, cab and inf files after succesful DIFx install
Hi Bob, But how to specify that folder is temporary in WiX. I am used INF and SetupAPI technology in mine previous installer. But now it was requested to created MSI installer for the product. So I would like to say that I relatively new WiX/MSI world. Could you point me to some solution. And also will DIFx work correctly at uninstallation time if I will delete *.cat, *.sys and *.inf files upon successful install. Best regards, Al Bob Arnson-6 wrote: ashatilo wrote: I just implemented WiX/DIFx installer and everything works well except that driver files (i.e. sys, cab and inf files) are not deleted from my application folder after successful installation. I.e. sys files are installed in system32/drivers folder but additionally present in my application folder. I would like to avoid from this. You're installing the files so they're not deleted after the drivers are installed. That's how MSI and Difx work. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/Deletion-of-sys%2C-cab-and-inf-files-after-succesful-DIFx-install-tf4897124.html#a14042439 Sent from the wix-users mailing list archive at Nabble.com. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI does not auto elevate on Vista
I think it was ALLUSERS after all that, plus ignoring some warnings. Thanks to everyone for the help. Bob Arnson wrote: Ryan O'Neill wrote: 1) Should it not automatically ask for elevation (the shield icon is showing up nicely on my button, which sounds correct) according to code snippet 1 below? Yes. Get a verbose log (msiexec /l*vx) and look for LUA to see what MSI is deciding about the need to elevate. 2) Somehow I am creating a per-user / hybrid install, will creating a shortcut under program files do this? See the ALLUSERS property doc. You want to set it to 1. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installation Deployment via Group Policy (GPO)
Something that might come handy:
The package can be also deployed as a per machine installation, and after
that it will be out of the scope of the users to tamper with the installed
state of the software, but they'll still be able to launch it.
2007/11/30, Huseyin Tufekcilerli [EMAIL PROTECTED]:
Hello,
I am trying to deploy a sample MSI package which simply installs a
text file to Program Files folder. The setup runs just fine if you run
it through double-clicking or via msiexec /i package.msi command line
interface (with the current user is being an administrator on that
computer). Then I have created a GPO for the domain that the computer
resides and added the MSI package as an Assignment to that user. So
when that user, who is a local admin on that computer, logins the
computer; the installation is deployed to that computer just fine. But
whenever I have removed that user's local admin privileges the MSI
package can not be deployed with these event log error records:
1)
Source : Userenv
Event ID : 1085
User : NT AUTHORITY\SYSTEM
Description: The Group Policy client-side extension Software
Installation failed to execute. Please look for any errors reported
earlier by that extension.
2)
Source : Application Management
Event ID : 108
User : DOMAIN\user.name
Description: Failed to apply changes to software installation
settings. Software changes could not be applied. A previous log
entry with details should exist. The error was : Access is denied.
3)
Source : Application Management
Event ID : 103
User : DOMAIN \user.name
Description: The removal of the assignment of application
{OurProductName} from policy {OurGroupPolicyName} failed. The error
was : The system cannot find the file specified.
4)
Source : Application Management
Event ID : 101
User : DOMAIN \user.name
Description: The assignment of application {OurProductName}
from policy {OurGroupPolicyName} failed. The error was : Access is
denied.
In a nutshell, both (manual and GPO-deployed) installations fail if
the running user is not an admin. Since a GPO-deployed installation is
granted by a domain administrator, I think there must be an option to
run that installation as a privileged user during a non-privileged
user's login.
Any help/pointer would be greately appreciated.
Hüseyin.
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX Patches
I'm using WiX patches to patch an installation of our suite of products. This has gone well except 2 products in the suite have not been patched (even though there have been changes to them). Any ideas as to what this could be? -- View this message in context: http://www.nabble.com/WiX-Patches-tf4902193.html#a14042566 Sent from the wix-users mailing list archive at Nabble.com. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
