Could you not run the installer using CreateProcess(), and then wait for it
with something like
WaitForSingleObject()? This way you know when the installer finished.
Rob
Chesong Lee wrote:
How does your bootstrapper interact with MSI engine?
If your bootstrapper calls
That's correct - we generate the entire guid every time.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of DEÁK JAHN,
Gábor
Sent: Wednesday, August 02, 2006 1:14 AM
To: WiX-users
Subject: [WiX-users] rfc: Package element changes
On Tue, 1 Aug 2006
Title: Documento sin ttulo
Diseño Publicitario
Atrás quedo la vieja idea de comunicación que afirmaba que tan solo existía un emisor-mensaje-receptor. Ahora, las nuevas tecnologías permiten acceder a la lógica de la interactividad en la cual no somos tan
Hello.
1) MSM is copied to the MSI when MSI references MSM. And I want to leave
MSM out side of the main MSI. How to do it?
2) I want to author a custom action in MSM. Can I use
InstallExecuteSequence inside MSM to schedule the CA, since I did not
find ModuleInstallExecuteSequence in WiX
Peter G. Sakhno wrote:
1) MSM is copied to the MSI when MSI references
MSM. And I want to leave MSM out side of the main MSI. How to do it?
You cann't. A merge module cannot be installed alone because its lacks
some vital database tables that are present in an installation
database.
I've done some more thinking about this. I think Rob's main objection with
making Product/@Id optional was that someone might accidentally forget to
specify it. However, what if we displayed a warning to the user whenever
they omitted the Property/@Id attribute informing them that doing so is
Hmm, that's a very good point. I'm just trying to address Rob's concern
that a developer wouldn't understand what it means to generate the guid.
Honestly, I'd be more worried about them copying a setup with a guid and
failing to modify it (thus introducing collisions for users). It almost
Forgive my
newbiness... how do I create a directory using the directory element
that points to a specific location on the user's machine? For instance,
"C:\NewPath"? Or do I need a component tag that does
so?
Thanks,
Brian
Hello.
I have authored a custom action inside MSM and scheduled it, like that:
Binary Id=MyCA.dll SourceFile=MyCA.dll/
CustomAction Id=MyCA BinaryKey=MyCA.dll DllEntry=MyCA/
InstallExecuteSequence
Custom Action=MyCA After=LaunchConditions /
/InstallExecuteSequence
In log I found that this
You may have to check if your custom action function has a correct function
prototype:
extern C
__declspec(dllexport)
UINT __stdcall MyCa(MSIHANDLE hInstall);
1. extern C is required if your source code is C++.
2. __declspec(dllexport) is required if you do not have separate DLL definition
Im trying to use a custom action type 1, to create a dialog box from c++
code. I keep getting the error 1813 and the dialog box of course doesn't
appear. I need a dialog that I can have use a timer to close after a
specified amount of time. Its functionality works outside of MSI, in a
standard
I remember this same issue coming up in one of my projects. I couldn't find the defect at a glance through our database, but I seem to remember it having to do with the extension. I believe you can't use the .ico extension (either that or you have to use the .ico extension).Something weird like
I've got an
installer I'm working on where the main feature is required. All of the
subfeatures are not required however. Since I'm still new at this, I'm
trying to actually set the subfeatures so they do not install by default.
I want the user to select which ones to install.
What
I'll look a little more closely in that direction. I initially set the
subfeatures level to Level = 0 and that just kept them from displaying.
Brian
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 02, 2006 4:41 PM
To: Brian Beaudet;
Not that my other problem has a solution yet, but I've move on to try to get
something done. I am no having a problem trying to use the WcaGetProperty
function. I have a property Property Id =EULA[License]/Property
I call the function using
WCHAR l_wcLicense[2];
HRESULT hResult =
Be wary of level 0 for features - you can get into scenarios where it's
difficult to bring the features back to life :)
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Beaudet
Sent: Wednesday, August 02, 2006 2:01 PM
To:
Never mind,
I
found the problem. The Target attribute must be a pointer to a property such as
Target=[SOMECMD]. The property is the actual command.I remember
trying it before, but for some reason, it failed
Best regards,
Calin
From: [EMAIL PROTECTED]
[mailto:[EMAIL
You're probably crashing. The Windows Installer has an exception handler to
ensure that poorly written CustomActions don't hose the transaction.
You should look at other places in the code where WcaGetProperty() is used.
You'll find the WiX code has very, very few hard code buffer sizes.
Hi List,
If
I use Shortcut Target=[!INSTALLDIR] / then
everything goes fine. I would like to create a shortcut called Command Shell to
point to the installation directory. For some reason, this code fails and there
are no log entries referring to it.
Shortcut Id=_shCommPrompt
WcaGetProperty() isn't being used anywhere else this is the only call.
What I need to do is combine My license with DX License, but if I leave in
the code for
getting the DXEULA the entire program doesn't even run weird.
I tried with both allocation of memory and tried to see if maybe the fuction
20 matches
Mail list logo
