I now have in my UI a custom step that requires user to enter some data until
he can proceed to the next step.
However, the Next button won't get enabled, until user changes focus from the
last entry box.
I'd rather, if it went enabled as soon as user enters first character, without
waiting for
Maybe just give the two File elements different Name attribute values.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sergey Abakumoff
Sent: Thursday, September 04, 2008 22:53
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Install satellite
Thanks, it works like a charm!
On Fri, Sep 5, 2008 at 2:21 PM, Rob Mensching
[EMAIL PROTECTED]wrote:
Maybe just give the two File elements different Name attribute values.
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Sergey Abakumoff
Sent:
It actually doesn't work. You only get the properties that were built
into the MSI at build time. Any ideas?
Thx
dB.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Thursday, September 04, 2008 11:58 PM
To: General discussion for
The way I handled this for my DBScript piece was to load the file into a
temporary table in an immediate action, then use the table entries in the
deferred CA. By loading the file immediately, you have access to all the
properties, and can store it post-process. Then your deferred action can
use
That's not what I am trying to accomplish. I need a list of all
properties available during an immediate CA. I don't know the property
names ahead of time. Thx.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christopher Karper
Sent: Friday, September 05,
Run your custom actions to set the properties in the
InstallExecuteSequence as well. Your installer may not run with the UI
anyways.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Rerick
Sent: Thursday, September 04, 2008 6:29 PM
Hi all,
After struggling for a couple of days I have decided to write a tutorial on
how to install files into the WinSxS folder. There are some pitfalls and I
hope I can spare frustration by providing this tutorial. Well, here it is:
Basically the WinSxS folder is for native assemblies what the
Mike Rerick wrote:
It appears that in the InstallExecuteSequence, all of the various global
properties that had their values modified in the InstallUISequence have
reverted back to having whatever default value they had initially when they
were declared.
Properties have to be public (Id
Jeff Yates wrote:
So the best way is to have my additional installers write to the registry
and then have a custom action to do a runonce key registry entry written
during the uninstallation of the main product? That runonce would be my own
tool that reads the other installer registry keys and
Troy Howard wrote:
Also, since I imagine this will annoy a lot of people, is there any reason
why it's different in the first place?
When I created WixUI, I started with the MSI SDK samples, not with the
.vdproj UI.
Is there any interest in updating the
official codebase to use the
You just invoke custom action before files are removed. I don't backup
files but do some COM unregister before files are removed and there are
no problems doing that.
-Original Message-
From: xiaoli [mailto:[EMAIL PROTECTED]
Sent: Friday, September 05, 2008 1:46 AM
To:
I read section 8 of http://www.tramontana.co.hu/wix/lesson8.php but
there's no mention on how to write a dialog box that prompts for user
name and password and use them to register COM+.
Can anyone help?
-
This SF.Net
No, you're trying to do token replacement in files based on properties,
right? That's exactly what I'm doing.
You write an immediate CA to do your token replacement, and put the
resulting string in a temporary record... Then you schedule your deferred
CA for execution.
You write the deferred
Christopher Karper wrote:
You write an immediate CA to do your token replacement, and put the
resulting string in a temporary record... Then you schedule your deferred
CA for execution.
MsiFormatRecord/WcaGetFormattedString take care of resolving all
[FormattedPropertyValues] so you
Robert O'Brien wrote:
Q1 - does running upgrade msi or patch msi still require additional command
line switches?
Minor upgrades must be applied with arguments. Major upgrades don't need
them.
Q2 - I seem to recall running into upgrade capable msi's and patch msp's that
I could simple
Robert O'Brien wrote:
is there a recommended approach to getting current wix vs08 project
extensions to output a patch msp?
Currently, Votive and the MSBuild tasks/targets don't support the WiX v3
patching tools. I don't know if they'll be supported as target types in v3.
--
sig://boB
Radha Vaidyanathan wrote:
I am using WiX v3 and visual Studio 2005 (VC 8).
You might need to rebuild dutil.lib with VS2005; we build the ship
versions with VS2008.
Also for msi.lib: I downloaded Microsoft SDKs/v6.1 - that does not
contain msi.lib.
I have three
Krzysztof Kozmic wrote:
I now have in my UI a custom step that requires user to enter some data until
he can proceed to the next step.
However, the Next button won't get enabled, until user changes focus from the
last entry box.
I'd rather, if it went enabled as soon as user enters first
In article [EMAIL PROTECTED],
Yu, Brian [EMAIL PROTECTED] writes:
I read section 8 of http://www.tramontana.co.hu/wix/lesson8.php but
there's no mention on how to write a dialog box that prompts for user
name and password and use them to register COM+.
Its never a good idea to prompt
I have set all of the needed properties to have the Secure=yes attribute.
The install is a perMachine install on XP. The properties do appear in the
SecureCustomProperties property in the properties list that the installer
dumps at the end of the log. I also set the EnableUserControl property to
The best way to get the least confusing behavior is to have the
validity checks done when Next is clicked. If the validity checks
fail, display a modal dialog box displaying the error message and
don't transition to the next dialog box in the wizard sequence.
Otherwise, transition to the next
Bob - Thanks for your help.
You might need to rebuild dutil.lib with VS2005; we build the ship
versions with VS2008.
I downloaded the source. I could not import the VC project that comes
with source.
While trying to compile in VC2005, I get a ton of errors:
1inetutil.cpp
I am just starting to try wix. I have built and run the sample UI projects up
through the WixCustomSample.zip in vs2008. I don't see a way to process the
key on the custom dialog. It appears there is an event system but I don't
see any docs on this. Are there any tutorials that expand on this
I found the sample WixSampleDllCA. So just the images question remains for
now.
--
View this message in context:
http://n2.nabble.com/custom-ui-sample-question-tp842093p842175.html
Sent from the wix-users mailing list archive at Nabble.com.
In article [EMAIL PROTECTED],
Mike Rerick [EMAIL PROTECTED] writes:
I have set all of the needed properties to have the Secure=yes attribute.
The install is a perMachine install on XP. The properties do appear in the
SecureCustomProperties property in the properties list that the
Yes, all of the problem property Ids are in uppercase.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard
Sent: Friday, September 05, 2008 3:00 PM
To: WiX Users
Subject: Re: [WiX-users] Property problem - additional info
In article [EMAIL
What is more interesting, I have other global properties that get set from
an edit field in the UI and their values are available in the execute
sequence. It seems that only the ComboBox property and VBscript modified
properties are causing problems.
-Original Message-
From: [EMAIL
28 matches
Mail list logo
