[WiX-users] Distinguish between SQL integrated security and normal authentication

Hello, what is the most elegant (common way) to distingwhish between sql connection with integrated security and with user name/password. I have a GUI to enter user database server, instance name, user name, password ... to connect to an database. If user name and password are not provided

[WiX-users] Adding ActionData control to ProgressDlg

Hi, I want add ActionData control to ProgressDlg: Control Id=ActionData Type=Text X=70 Y=125 Width=265 Height=10 Subscribe Event=ActionData Attribute=Text / /Control I tried develop new progress dialog with name MyProgressDlg. I also changed WixUI_Mondo to MyMondo but

Re: [WiX-users] Adding ActionData control to ProgressDlg

Take a look here http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html I think I have covered what you want to do. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: Dmitry Berkovich [mailto:[EMAIL

Re: [WiX-users] SQLExtension, check if database exists

I have written a custom action, thanks for clarifaction Thomas -- View this message in context: http://n2.nabble.com/SQLExtension%2C-check-if-database-exists-tp1613865p1643613.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Unresolved reference to symbol 'CustomAction:SchedSecureObjects'

Solved by including wixca.wixlib to light's input From: Alan Sinclair Sent: Wednesday, December 10, 2008 6:13 PM To: wix-users@lists.sourceforge.net Subject: Unresolved reference to symbol 'CustomAction:SchedSecureObjects' I'm trying to add code to set

[WiX-users] changing heat registry entries to createAndRemoveOnUninstall

Does anybody have a solution for fixing up RegistryValue elements generated by heat so that I can specify Action=createAndRemoveOnUninstall? I think this should be doable with XSL but I'm not sure how to go about it. For example: Heat gives me RegistryValues like this: RegistryValue

Re: [WiX-users] changing heat registry entries to createAndRemoveOnUninstall

Why do you want to add @Action to the Registry key. The default none should be sufficient for this case. -Original Message- From: David Jackson [mailto:david.jack...@ca.ibm.com] Sent: Thursday, December 11, 2008 12:07 To: General discussion for Windows Installer XML toolset. Subject:

Re: [WiX-users] changing heat registry entries to createAndRemoveOnUninstall

Without Action=createAndRemoveOnUninstall they weren't removed during uninstall. Is there a better way to do this? From: Rob Mensching rob.mensch...@microsoft.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: 12/11/2008 03:27 PM Subject: Re:

[WiX-users] Simple upgrade.

Hi all, I am somewhat perplexed with the whole upgrade path. I have read and re-read the Wix docs, the MSDN data, months of WiX posts relating to upgrading and anything else I can get my hands on. The more I read, the more confusing it gets and the less I seem to understand. I am hoping

Re: [WiX-users] changing heat registry entries to createAndRemoveOnUninstall

Can you be more specific about what wasn't removed? By default RegistryValues installed should be removed at uninstall. -Original Message- From: David Jackson [mailto:david.jack...@ca.ibm.com] Sent: Thursday, December 11, 2008 13:13 To: General discussion for Windows Installer XML

[WiX-users] Change in output behavior?

I've just upgraded to a newer v3 build and all of my post-build steps that expect $(TargetPath) to point to my build output are broken because OutDir, TargetPath, TargetPdbPath are all pointing to the wrong place. OutDir is shown as bin\Debug\, for example whereas the build is really dumping

[WiX-users] Phil Bevan is out of the office.

I will be out of the office starting 11/12/2008 and will not return until 15/12/2008. I will respond to your message when I return. This e-mail is sent by or on behalf of the named sender identified above. If: (a) you do not wish to receive any e-mail marketing material from this person in

[WiX-users] CA called from DoAction

Hi, I want to verify the directory the user entered in the UI exists. I created a custom action with DTF (Thanks Jason!) that works. However, my understanding from this thread http://tinyurl.com/6ovukx is that; The context/handle is different from within DoAction ControlEvent rather then

Re: [WiX-users] CA called from DoAction

In article 250bf09281efec4398de83072daed6ef713d32c...@ex3.messagegate.local, Dale Quigg da...@messagegate.com writes: I want to verify the directory the user entered in the UI exists. I created a custom action with DTF (Thanks Jason!) that works. However, my understanding from this

Re: [WiX-users] Change in output behavior?

Joe Coplen wrote: I've just upgraded to a newer v3 build and all of my post-build steps that expect $(TargetPath) to point to my build output are broken because OutDir, TargetPath, TargetPdbPath are all pointing to the wrong place. OutDir is shown as bin\Debug\, for example whereas the

[WiX-users] Unexpected error LGHT0204 on Maximum in UpdateVersion

Light.exe 3.0.4318.0 throws an error when the third field of Maximum field is over 32767, such as MaxVersion=2.0.65000 This code UpgradeVersion Property=NewerProduct OnlyDetect=yes Minimum=2.0.500 Maximum=2.0.65000/ generates this error C:\dev\brazil\installer\Installer.wxs(25) :

Re: [WiX-users] Unexpected error LGHT0204 on Maximum in UpdateVersion

It's not light that is actually reporting the error, it's ICE61. You can see the documentation in the MSI SDK. I'd say the Windows Installer team has a bug in their ICE. -Original Message- From: Gordon Dass Adams [mailto:gor...@mcneel.com] Sent: Thursday, December 11, 2008 15:24 To:

[WiX-users] Invalid ICE61 on major upgrade in WiX 3 (3.0.4805.0)

I am pretty sure I did not have this ICE before installing 3.0.4805.0. Here is an upgrade table I am using: Upgrade Id=$(var.UpgradeCode) UpgradeVersion Minimum=$(var.OriginalVersion) IncludeMinimum=yes Maximum=$(var.CurrentVersion)

Re: [WiX-users] CA called from DoAction

Date: Thu, 11 Dec 2008 15:49:45 -0700 From: Richard legal...@xmission.com Subject: Re: [WiX-users] CA called from DoAction The context/handle is different from within DoAction ControlEvent rather then sequenced CA. MsiProcessMessage calls won't work. My testing confirms this. Is there any

Re: [WiX-users] Invalid ICE61 on major upgrade in WiX 3 (3.0.4805.0)

You might double check to make sure the MSI's Upgrade table has the right bits. If those are wrong, then it's a WiX bug. If those are correct, it's probably an ICE61 bug. -Original Message- From: Alexander Shevchuk [mailto:alexander.shevc...@microsoft.com] Sent: Thursday, December 11,

Re: [WiX-users] CA called from DoAction

Dale Quigg wrote: I have a custom dialog and when I press Next, I want a custom action to fire to check a value in an edit box. If the CA detects an error, I want it to display a dialog (which does not work apparently due to the communication issue with MsiProcessMessage) and then set

Re: [WiX-users] Invalid ICE61 on major upgrade in WiX 3 (3.0.4805.0)

Sorry, forgot to include it. Attributes column in Upgrade table has expected value of 256. Looks like it is an ICE bug. -Original Message- From: Rob Mensching [mailto:rob.mensch...@microsoft.com] Sent: Thursday, December 11, 2008 4:50 PM To: General discussion for Windows Installer

[WiX-users] Verification of user account

Hi, Can somebody lead me to a CA or some other way through which I can validate the user account given in the UI. As in next to my Username text box is a button (Check Name) which should validate/verify the domain user name that has been entered in the textbox. Thanks in advance,

Re: [WiX-users] Distinguish between SQL integrated security and normal authentication

Has anyone some 50 cents? Any help would be appreciated. Thomas -- View this message in context: http://n2.nabble.com/Distinguish-between-SQL-integrated-security-and-normal-authentication-tp1642658p1646877.html Sent from the wix-users mailing list archive at Nabble.com.