I'm changing jobs in two weeks, and with the change in responsibility
I'll be leaving the Wix-users community. I subscribed to the list last
year and was able to successfully - and relatively painlessly - change
our products from InstallShield to Wix. Almost all of that invaluable
knowledge came f
[EMAIL PROTECTED] wrote:
> > For the machine name, use the ComputerName property.
Tris Hodges wrote:
> I assume you meant like the following.. $(sys.COMPUTERNAME)? I
> believe this is set at compilation [
]
No, Calin meant the Windows Installer property ComputerName, see the Windows
Installer P
Daryn Mitchell originally wrote:
> > ... merge module's ... SecureCustomProperties ... how should the
> > merge module get the result of its file search during Vista repair?
Bob Arnson wrote:
> The only thing I can think of is a custom action that adds you
ad to ask.)
- If not, how should the merge module get the result of its file search
during Vista repair?
Thanks,
Daryn Mitchell
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio
> -Original Message-
> From: wix-users On Behalf Of Boris Krivonog
...
> Attached is a simple VS 2005 project which locates a process by name and
> sends it a WM_CLOSE.
That's really generous of you, Boris. Thanks for sharing that with the
community.
Daryn.
--
> -Original Message-
> I have a feature with the ID="SomeFeature".
>
> $SomeFeature
> This throws an ICE79 error.
>
> However, changing the $ to a ! is fine.
$ is for components, & and ! are for features.
(Conditional Statement Syntax
http://msdn2.microsoft.com/en-us/library/aa368012(VS
> -Original Message-
> Yes, I know the short answer is 'no'
> ... installers that can make a single multilingual install package
> ... isn't there some creative work-around for this?
"Multi-Language MSI Packages without Setup.exe Launcher"
http://www.installsite.org/pages/en/m
> -Original Message-
> From: Sneha Gharpure
>
> the "WriteToRegistry" action is called only during the
> installation and therefore the condition " Not Installed".
> I am not sure about the condition for "WriteToRegistry_Rollback".
> I have tried both- "Installed" and "Not Installed"
>
>
> -Original Message-
> I have one service related binary(guardsvc.exe)
>
> It is started properly while installing and stoped while uninstalling.
>
> The problem is it is not deleted the corresponding registry
> key(HKL\SYSTEM\ControlSet001\Services\guardsvc.exe) and because of
> this re
ould not depend upon the condition $Component1=3
to check whether Component1 is locally installed on the computer..."
Question:
So what is the correct way for the Product2 install to know that the shared
component is already installed locally by Prodcut1?
Thanks for any suggestions
Daryn Mitc
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> Subject: Re: [WiX-users] Re Post: Msi Logging
> I dont have idea about "bootstrapper".
>
> Could you tell me in detail or send me the url
http://www.nabble.com/forum/Search.jtp?forum=4468&local=y&query=bootstrapper
-
Adam Langley wrote:
> ...
> the Progress Text in the dialog shows "Removing Backup Files"
> during the execution of my slow custom action, it never
> renders my text
> ...
>
My guess: You should make your action be deferred instead of commit.
a) Wix ProgressText maps to Windows Install
Here's a couple of possibilities:
1) If you've got an existing MSI you're converting to Wix, use the Wix tools
(Dark) to decompile it into Wix markup.
2) Very handy Custom Action Type Calculator on the InstallShield web site
makes the guess and test go much quicker. (Needs IE, doesn't work in Fi
Your CustomAction needs to be defined differently.
Instead of ExeCommand, use VBScriptCall='' (value = blank to just run the
script, or put the name of the VBScript function). ExeCommand attribute
tries to execute an EXE, not run VBScript.
Also I'm pretty sure that deferred custom actions have to
Rob Hamflett wrote:
> The general advice is usually to offer the option of deleting
> files/settings for the current user.
I like this, but as a beginner setup guy I'm unclear on where exactly I'm
supposed to offer that option.
My natural inclination is to put it in the UI during the uninstall st
> From: Jeff Hunsaker
> Sent: Friday, June 08, 2007 1:55 PM
>
> I'm adding a program menu which should be created if it's not there.
> Other programs install to this menu so I do not want to delete it
> at uninstall. My XML looks like this:
[...]
> error LGHT0204 : ICE64: The directory scmworkbe
I see that the use of [INSTALLDIR] in the registry entry - perhaps edited by
hand? - does not match the the TARGETDIR DirectoryRef.
This is not guaranteed to be an error, e.g. if you've ensured that the two
properties are equal, but it seems fragile.
You can check the installed registry entries t
Anidil,
Does it help if you pass Value='1' instead of Value='#0x0001(1)'?
Daryn.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anidil [...]
Now that i don't get permission denied message after prefexing # for all the
DWORD types as follows :
I found it very easy to debug a DLL CA with the debugger:
I figured the DLL in the binary table has to be extracted before the code
can be called, right? So the following seemed to work for me to debug an
error I was getting while developing the CA:
1) Use a debug version of the DLL
2)
I don't know if there's a better way than this, but you could certainly make
a custom action to do it using WMI. The Win32_Process class lets you see if
there's a process running of a certain name, command line, etc.
('Win32_Product', http://msdn2.microsoft.com/en-us/library/aa394372.aspx)
Ther
Rennie,
I'd be very happy to see a more beginner-oriented tutorial to help with
getting started. I'm currently evaluating whether to switch from
InstallShield to WiX, and there are still things I have not yet got
running/tested in WiX.
I'm a software developers who happen to also do setup -- as
Also for an concise example of using the Automation interface you might find
it helpful to look at "WiRunSQL.vbs" in the Installer SDK / Platform SDK.
Use of the script is described in "Examples of Database Queries Using SQL
and Script"
http://msdn2.microsoft.com/en-us/library/aa368562.aspx
Dar
Does it fix that if you schedule it after='InstallFiles' instead of
CreateFolders?
Daryn.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of JCWrs
Sent: Thursday, April 19, 2007 12:39 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Sequence o
Kevin Burton wrote:
> Durint installation I briefly see a German message appear during the
"progress: dialog. When there is an error I see an error dialog piop up that
is entirely in German.
[]
> Do you know how to change that?
I've been learning WiX this week and I saw the same behaviour aft
24 matches
Mail list logo
