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

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: >

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

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 wil

Re: [WiX-users] BrowseDlg & SelectionPathOn help

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

[WiX-users] icon change of the installer

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] Creating MSI for 64bit machine

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

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

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 wrote:

Re: [WiX-users] writing to console from smoke.exe using customaction

Looking at your code and reading msdn WriteConsole(szBuffer); might fail. Something with ansi and widechar but this is really not my area of expertise. Can you try to see if this might work: (everybody else: HELP!) AttachConsole(...); HANDLE file; file = GetStdHandle(STD_OUTPUT_HANDLE); // che

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

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 Inst

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

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

[WiX-users] Creating MSI for 64bit machine

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 muc

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

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 h

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

Thanks, as you suggested earlier I think the COM component should have references to any one of below tables Class table ProgId table Registry table SelfReg table TypeLib table & hence I think there should be a reference in File table to any one above for COM component - Nag -Original Messag

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

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)

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 i

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

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 attr

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

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@lists.sourceforge

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

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, December