So basically you say you need a separate installer for 64 bits (no
problem with that anyway, my bootstrapper should handle this )
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Bob Arnson
Verzonden: woensdag 21 juni 2006 8:15
Aan: rchiodo
CC: wix-users@
Previously I mainly use major upgrades with changes of product codes. Now I need minor upgrades which allow more soft upgrade - just reinstall and also allow patches. Major upgrades for some strange reasons doesn't allow it.
So I research this questions and have non-answered.
1. I found rules of
Well no not really. I just need to install a component differently on 64 than
on 32. Specifically I want the component to be permanent on 32, but not on
64.
I think I can get around this by having two versions of the same component,
and then for the 64 bit one, rename (CopyFile) it to the origin
Albert van Peppen wrote:
>
> So basically you say you need a separate installer for 64 bits (no
>
Almost always. You can't mark a package as supporting both Intel (x86)
and x64, for example. And while a 64-bit package can also install 32-bit
components, a 32-bit package isn't allowed to inst
rchiodo wrote:
> I think I can get around this by having two versions of the same component,
> and then for the 64 bit one, rename (CopyFile) it to the original name
> during the install. Something like so:
>
CopyFile is dangerous because you can't service the files that are
copied/moved/rename
Igor Lemsky wrote:
> Previously I mainly use major upgrades with changes of product codes.
> Now I need minor upgrades which allow more soft upgrade - just
> reinstall and also allow patches. Major upgrades for some strange
> reasons doesn't allow it.
Don't allow what?
You're right that removin
Neil Sleightholm wrote:
In
the online help there is this paragraph: "You can most easily add
and remove dialogs from the stock dialog sets by copying one of the
existing sets and modifying it. For an example, see the project in the
doc/examples/wixui/custom directory."
This
examp
Peter:Is it possible to try something like:HWND hWndParent;hWndParent = GetActiveWindow();I'm facing a similar problem with a dialog that pops up during the MSI UI. Unfortunately, sometimes it pops up behind the MSI dialog and other times it is in front of it.
Anybody else have any ideas?DanaOn
On Thu, 22 Jun 2006 09:12:57 -0700, Bob Arnson wrote:
Neil,
>> This example doesn't seem to exist, is it missing from the
>> downloads? Is the example available somewhere?
The tutorial shows how to add a dialog, removing one would be done much the
same way...
Bye,
Gábor
--
Dana,
I think the better way is try to use FindWindow, since we always know
the name of the MSI dialogs we use and all MSI dialogs have same class
name - "MsiDialogCloseClass". But I have no chance to try this way yet.
Best regards,
Peter G. Sakhno
C-MAP RUSSIA Ltd
http://www.c-map.ru/
Dana Gut
Gábor/Bob
Thanks for the comments. It turned out to be fairly easy as you say.
Neil
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on A
Peter:Thanks for the suggestion, I just tried HWND hWndParent; hWndParent = FindWindow(_T("MsiDialogCloseClass"), NULL);This seems to work very well. I haven't noticed any times (yet) where my dialog is behind the MSI main dialog.
Thanks,DanaOn 6/22/06, Peter G. Sakhno <[EMAIL PROTECTED]> wr
Ok so I tried rebuilding the sca.wixlib.
I used the command
nant –D:dir.root=c:\wix\wixsource
From the directory that holds the scawixlib.build
file.
I have Microsoft platform sdk (R2)
(3790.2075) installed on my machine
I got the following error.
What am I doing wrong?
C:\wix\wixs
After doing this, does anything need to be recompiled?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Thursday, June 22, 2006 12:13 PM
To: Neil Sleightholm
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Customizing dialog sets
N
The WiX Tutorial covers some of this but the process I
used:
1. Copy all the files in src\ui\wixui to a
new folder
2. Copy src\ui\wixui\mondo\WixUI_Mondo.wxs (or which
ever base file you want) to the same folder.
3. Rename WixUI_Mondo.wxs and edit it to add/remove the
features you want.
4. R
I read something in the history file about
support for a newer release of the SDK being added (“BobArnso: Add support for Windows
2003 R2 Platform SDK”), so you may want to make sure you are using the
latest build.
Frederik.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED
Hi,
I have been using minor upgrades for most of our updates,
our application is primarily a server based web application and in most cases
the changes are to ASPX and DLL files. Minor updates work well when
you are changing existing files or adding some new ones (as a new
component).
Sam
I
ran into the same issue 2 builds ago - tried changing the GUID to the
new one used by the latest SDK but had further downstream errors and gave up.
The latest build is successful with the R2 SDK so you should be good to go
now.
HTH
Subbu
-Original Message-From:
[EMAIL
Frederik Carlier wrote:
I read
something in the history file about
support for a newer release of the SDK being added (“BobArnso: Add support
for Windows
2003 R2 Platform SDK”), so you may want to make sure you are using the
latest build.
Yes, I just added support for th
Believe it or not,
this is my fault. LocalCache is failing on your machine. I wrote
the LocalCache feature for Office 2003. There were two or three subtle
bugs that didn't show up until some serious patches were sent out. You
can read about it more here: http://blogs.msdn.com/robm
20 matches
Mail list logo
