Yes E: drive is local not a network share.
The location of the heat.exe is correct, when i copy the full path i get
from the error and run heat.exe from there it works i.e. the path is
correct.
I have built the project with MSBuild without any problems the issue came
when introducing
Read two values with RegSearch, and convert thay to formatted text with custom
action (jscript). And compare properties in conditions.
Отправлено с Почта Windows
От: bwehking
Отправлено: пятница, 14 февраля 2014 г. 17:12
Кому: wix-users@lists.sourceforge.net
Hmm, sorry
Hi,
I've managed to create add WiX project to my C# solution which build the msi
package. I've set the product version to be automatically obtained from the
app's executable file version. But now I want to be able to get that version
inside the msbuild script (wixproj file).
What I'm trying
Hi everyone!
I was doing some changes to an existing installer, and I needed to enable
.Net 3.5 on Windows 8.
This can easily done with the comand dism.exe /online /enable-feature
/featurename:NetFX3 /all /NoRestart.
So I was doing a simple Installer to add to my Bootstrapper that would run
Moving this to wix-users.
I was asking if I should create a feature request to ignore ICE38 in per-user
installs. But after I asked I found another thread on wix-users (see link
below) that pointed out if the user has the ability to choose the install
location then multiple users could
In the bootstrapper the burn engine is tacking on:
Action time: CustomAction name. progress text
I don't believe I can change the first two elements (Action time:)
I am just using straight forward strings to describe what the custom action
is doing, my dev manager wants to filter out the extra
I'm trying to include a sample C# project in my installer using HeatProject
as follows:
Target Name=BeforeBuild
HeatProject
OutputFile=$(IntermediateOutputPath)_DSVDemo.wxs
ToolPath=$(WixToolPath)
Project=..\samples\csharp\DSVDemo\DSVDemo.csproj
Hello guys,
Is there a way to use WiX in a form of a library (no executables)
So that I could e.g. create a .net web-application which can be hosted
somewhere (e.g. on windows azure), and produce MSI installers for users?
The scenario is that user enters some info, and then downloads the
That error is just a %1 could not be found., implying that something
(most likely dism.exe?) could not be found.
I see no trace of the code you used - didn't make it into your post.
---
Phil Wilson
On Wed, Feb 19, 2014 at 2:50 AM, JoeMarks jose.marq...@waveform.pt wrote:
Hi
As Jacob says, those messages come from the ActionText data in the MSI
files. Take a look at what's in there, if anything. If you want to
control the text, that's the place to start. The callbacks just send
you what's in there.
I haven't looked at the bootstrapper and exactly what it may do with
First, those blog comments are from before Restart Manager,
MsiRMFilesInUse and the changes made in MSI 4.0 and higher to reduce
the need for reboots. They are ok as far as they go, but cannot be
used as a guide to what happens in a Restart Manager world.
Second, I still don't think there is an
Okay I will take a look, however if you look at the ActionText within the MSI
(I have an MSI running NOT silently) so I can position the MSI and the
bootstrapper side by side and see the Action Text the bootstrapper is prefixing
Action time to the MSI stream...
Steve
-Original
I thing the mailing list hides the raw text, it's only visible on the
thread in here
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-td7592771.html
Even if I remove the CustomAction from the installer i get the same log
file, so I guess it
See:
http://support.microsoft.com/kb/834484
Is the dsim tool your executing meet the criteria discussed in the
article. If the tool is mapped as a Network drive:
* The drive that contains the folder that you are trying to install
the Windows Installer package to is accessed as a substitute
The log is available on stackoverflow, has no evidence that it is
trying to run a custom action, and contains this line:
MSI (s) (04:D4) [17:20:10:936]: PROPERTY CHANGE: Adding REMOVE
property. Its value is 'ALL'.
So it does not appear to be the failing install log, I think the same
MSI is being
@eyoung100: So it mean I can't test this on a Virtual Machine?
@Phill: Yes, I also posted this question on stackoverflow to improve my
chances of getting an answer :)
That sounds interesting, any way to check if the installer is indeed being
run again?
Thank you for your replies.
--
View this
AFAIK, you can test this on a virtual machin as long as the installer
is started from a non networked drive. IE, on the Virtualbox Virtual
Disk, but none of the shared folders you mapped as Drives...
Carter
Quoting JoeMarks jose.marq...@waveform.pt:
@eyoung100: So it mean I can't test
I'm running the installer on Desktop, so it's not on a Networked drive.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592788.html
Sent from the wix-users mailing list archive at Nabble.com.
Your call to dism has the path '[WindowsFolder]SysWOW64\dism.exe'. If you
open an Admin CMD box and type your full command you will get a better
explanation of the error. SysWOW64 specifies the 32 bit operating system
files. Error 11 is returned which indicates that you cannot service a
running
Yes, you are correct, after some search I got to this thread
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/using-dism-exe-in-my-custom-action-td3667299.html
So by setting the command to [WindowsFolder]Sysnative\dism.exe would fix
that, but my problem persists...
--
View
Is your Desktop mapped to a roaming profile??
Quoting JoeMarks jose.marq...@waveform.pt:
Yes, you are correct, after some search I got to this thread
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/using-dism-exe-in-my-custom-action-td3667299.html
So by setting the command to
Did you type that command in a Admin CMD box and see what happens? It does
not work for me either.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592792.html
Sent from the wix-users mailing list
Alex,
The MSI version is different from a file version and you have to extract it
from the MSI database. I did it using a python script and msilib but I was
doing it outside of MSBuild. You could also do it with C#, here's a page with
an example:
Sigh... I finally figured out what was causing this issue :(
I was creating some registry values in EventLog\My Company
and these registry keys had forcecreateoninstall forcedeleteonuninstall...
Fixed that up... nuts!
thanks,
Steve
--
View this message in context:
24 matches
Mail list logo
