Using WiX 3.0.5120.0, I can create a private queue easily enough, but if
I try to create a public queue the installer fails.
The log says:
MessageQueuingExecuteInstall: Error 0xc00e0005: Failed to create
message queue
MessageQueuingExecuteInstall: Error 0xc00e0005: Failed to create
message
I've confirmed this seems to be a bug for me too, in 3.0.4923.0. Going
back to 3.0.4909.0 resolved the issue.
Yan Sklyarenko wrote:
Hello WiX developers,
Sorry, but it seems I found another bug in the IIS extension.
WiX version is 3.0.4917.0. Here is a component definition:
Component
builds ConfigureIIsExec comes before
WriteMetabaseChanges.
Chris Eldredge wrote:
I've confirmed this seems to be a bug for me too, in 3.0.4923.0. Going
back to 3.0.4909.0 resolved the issue.
Yan Sklyarenko wrote:
Hello WiX developers,
Sorry, but it seems I found another bug in the IIS
Sorry for the all the self-replies but I've been updating as I go.
Build 3.0.4827.0 works for me on Server 2003 and on Vista.
Chris Eldredge wrote:
Actually, scratch that. Neither build works on my Windows Server 2003 /
IIS 6 box, but both work on my Windows Vista / IIS 7 box.
I haven't
in
the same working directory? What version of WiX are you running?
Matt
On Thu, Nov 20, 2008 at 12:32 PM, Chris Eldredge
[EMAIL PROTECTED]wrote:
I have a continuous integration server with multiple, unrelated
projects. The machine has multiple cores so I let the projects build
asynchronously
I have a continuous integration server with multiple, unrelated
projects. The machine has multiple cores so I let the projects build
asynchronously. When 2 instances of light.exe run at the same time, bad
things seem to happen.
Can anyone confirm or deny that light.exe does something (maybe
Actually, I'm trying to load the assembly from the file system, not the
GAC. Does that change your answer?
Thanks,
Chris
Adam Majer wrote:
No. GAC is updated after MSI install is finalized. Wix has no control
over this.
- Adam
Doh! I figured out that the reference to the File ID was wrong, so the
path to the assembly was evaluating to a blank string. Turns out
standard action sequence works fine for this scenario.
Thanks,
Chris
Alexander Shevchuk wrote:
Hi Chris,
Sorry, I am still on WiX 2, but that should not
I'm trying to create an MSI that installs a .NET assembly and registers
it for use in SQL Server 2005.
The problem is that the SQL I'm executing inside a SqlString is telling
SQL Server to load the assembly, but when I install the MSI it seems
that the assembly hasn't been copied to its final
Is there an example of wix markup to prompt for a password during
installation? Also, this is more of a stretch, but is there a custom
action that could verify that a given username/password are valid in the
domain?
Thanks,
Chris Eldredge
10 matches
Mail list logo