Re: [WiX-users] Install external program from CDROM drive

2009-12-29 Thread dB .
You shouldn't be doing this from an MSI, but from a bootstrapper. MSIs are not design to run other installers. Try http://dotnetinstaller.codeplex.com. Hope this helps, Cheers dB. -Original Message- From: Arun Perregatturv [mailto:aperregatt...@napcosecurity.com] Sent: Monday,

Re: [WiX-users] WiX, InstallShield and combining multiple MSIs

2009-12-29 Thread dB .
Use a bootstrapper to chain multiple MSIs with pre-conditions. http://dotnetinstaller.codeplex.com is a good choice. Hope this helps, -dB. -Original Message- From: Carter, Patrick [mailto:patrick.car...@stryker.com] Sent: Monday, December 21, 2009 8:47 PM To:

[WiX-users] differentiating between COM C++ dlls from installer database (.msi)

2009-12-29 Thread nagaram.c
Hi, Is there a way that I could differentiate between COM C++ DLL by looking into the installer database file (.msi), I know that all .NET components are maintained in msiAssembly table but I think both COM C++ files are maintained under Files table, is there a way by looking into some

Re: [WiX-users] differentiating between COM C++ dlls from installerdatabase (.msi)

2009-12-29 Thread Peter Shirtcliffe
I presume you mean how do you differentiate between COM and non-COM DLLs - some COM DLLs are written in C++ :) There is no certain way of spotting a COM DLL from the MSI alone because it might be self-registering, registered by an external application or be used with registry-free COM. If there

Re: [WiX-users] differentiating between COM C++ dlls from installerdatabase (.msi)

2009-12-29 Thread nagaram.c
Hi, Thanks for your information. I have one more question. Is it true that both COM non-COM are maintained in Files table where as all .NET components are maintained under msiAssembly table - Nag -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday,

Re: [WiX-users] differentiating between COM C++ dlls from installerdatabase (.msi)

2009-12-29 Thread nagaram.c
Thanks once again for clarification, I think if there is any way to locate non-COM file then that should be File table selfReg table, like if suppose if a particular record in File table has reference to selfReg then it is COM component else a non-COM, but I am not really sure if the File table

[WiX-users] Creating MSI for 64bit machine

2009-12-29 Thread Sagar1111
Hi I want to develop a 64 bit MSI. I have already developed 32 bit MSI. But now if i had to modify it for 64 bit machine, what changes do i need to make? For eg:Package/@Platform , Component/@Win64, file/@ProcessorArchitecture or will candle -arch command build 64 bit MSI for me? I am pretty

Re: [WiX-users] Install external program from CDROM drive

2009-12-29 Thread Arun Perregatturv
Is it possible to make a small code snippet. Thanks. The link also says -- SourceDir Property The SourceDir property is the root directory that contains the source cabinet file or the source file tree of the installation package. This value is used for directory resolution. Default Value The

Re: [WiX-users] Install external program from CDROM drive

2009-12-29 Thread Arun Perregatturv
I know. But the requirements are such that I have to install certain things based on user selection. Server option - Install everything ( good with Bootstrapper) Client option - Install only certain things based on user selection. That's where the problem is. I have an InstallShield Windows

Re: [WiX-users] Creating MSI for 64bit machine

2009-12-29 Thread Rob Mensching
candle -arch will switch the Package/@Platform to 64-bit. That's about all you need to do. Then you can mark Components/@Win64 as necessary. File/@ProcessorArchitecture probably won't be needed. Play with it a little bit, that tends to help a lot. On Tue, Dec 29, 2009 at 6:24 AM, Sagar

Re: [WiX-users] Creating MSI for 64bit machine

2009-12-29 Thread Michael Clark
Check out the following ... http://blogs.msdn.com/astebner/archive/2007/08/09/4317654.aspx Good luck -Michael -Original Message- From: Sagar [mailto:sagarkavitak...@gmail.com] Sent: Tuesday, December 29, 2009 9:25 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Creating

[WiX-users] icon change of the installer

2009-12-29 Thread Sanjay Rao
Hi All, I have two issues for which I have not found any solution- 1. I need to change the icon of created MSI file using WIX. 2. I need to change the msi icon shown in title bar of dialogs during setup process. Can anybody help me on this ? Thank you very much in advance. If it is not possible

Re: [WiX-users] BrowseDlg SelectionPathOn help

2009-12-29 Thread Sagar1111
Anybody there to help me out? Please Sagar wrote: Hi I am using WixUI_Mondo as my UI. However i am skipping SetupTypeDlg which comes with standard WixMondo (This is because i have a single feature). Now i have added a my own dialog ChangeFolderDlg between LicenseAgreementDlg and

Re: [WiX-users] Clarification on the MSI security

2009-12-29 Thread Blair
You can try setting the packa...@readonly attribute. As far as I know Orca respects the read-only selection but I have never tried it myself. However, the APIs don't seem to prohibit editing (and committing) read-only MSI files. If your MSI file is authenticode-signed than any editing at all will

Re: [WiX-users] Creating MSI for 64bit machine

2009-12-29 Thread Sagar1111
Thank you very for the quick reply Rob and Michael. I have a custom Action written in C# which is being used in the MSI. So do i need to build that custom action separately for 32 bit and 64 bit and then use those specific CA.dll files for respective MSI -Sagar Rob Mensching-7 wrote: