On 01/11/2012 01:23 PM, Peter Hull wrote:
>
> Hi Nikolaj!
>
> Could you comment on whether your installer was signed (the bundle and the
> actual engine which is unpacked out of it - see this link
> https://sourceforge.net/mailarchive/forum.php?thread_name=CAHdHTVc1c2h3QuYsiXWcR8A1Xtk38Z3W2KCyAvu
Not fixed in the Beta, fixed after the Beta. Weekly releases coming soon.
On Wed, Jan 11, 2012 at 9:18 PM, Sunny Li wrote:
> Hi there,
>
> Currently I've built a bundle and uploaded the bootstrapper to one of our
> webservers. When I download the bootstrapper from the web and run it,
> windows s
Hey,
I have a 3rd party executable to detect some hardware, and since it's a general
purpose exe, not detecting the hardware isn't a condition that has the exe
return a failure (I guess, to be expected and completely fair).
So, in order to determine whether the hardware I'm looking for is prese
Hi there,
Currently I've built a bundle and uploaded the bootstrapper to one of our
webservers. When I download the bootstrapper from the web and run it,
windows shows two "Open File - Security Warnings" which is kind of
annoying. I read from
http://sourceforge.net/tracker/?func=detail&aid=3418715
Thanks for the information Peter. Some follow up:
1) In previous versions of our app, we distributed patches to the customer as a
set of files in a zip that the customer simply unzips into the application
directory. While this isn't ideal (because of the problems associated with
uninstalling pa
There are like four Sign* targets in wix2010.targets. Create a target named
the same for each and all of your things can be signed. It's actually
really easy.
On Wed, Jan 11, 2012 at 2:13 PM, sunniejai wrote:
> Thanks Rob, a blog post would be great!
>
> As I am not that familiar with modifying
Thanks Rob, a blog post would be great!
As I am not that familiar with modifying the MSBuild sequence, do I just
specify something like
in my wixproj?
I guess I should probably sign all my MSI's with a digital certificate using
the signtool before calling that?
Thanks,
Sunny
--
View this mess
Yeah, XPath is horrid in those attributes given the escaping necessary to
pass through to MSI. Sadly, two "languages" designed in completely
different silos whose special characters collided really badly.
On Wed, Jan 11, 2012 at 8:20 AM, Dan Gough wrote:
> D'oh - solved. I was incorrectly esca
Rollback should and does happen automatically. If you have any custom actions
they need to cater for this. What does a verbose log say?
How are you installing the service, are you using the
element?
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL
Created SF Feature Request 3472491:
https://sourceforge.net/tracker/?func=detail&aid=3472491&group_id=105970&atid=642717
https://sourceforge.net/tracker/?func=detail&aid=3472491&group_id=105970&atid=642717
.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabb
Dear lord why did it add to this. I am sorry. Can ignore my post. :(
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-First-Bundle-tp7173712p7177148.html
Sent from the wix-users mailing list archive at Nabble.com.
---
My installer is installing a service (which starts automatically upon
installation) and a program. Now, if the install fails for any reason,
the service is still installed, but fails to start. How can I go about
doing a complete rollback upon failure? Is a custom action that calls
the instal
My installer is installing a service (which starts automatically upon
installation) and a program. Now, if the install fails for any reason,
the service is still installed, but fails to start. How can I go about
doing a complete rollback upon failure? Is a custom action that calls
the instal
Hi Rob, yeah I noticed I was using the Id rather than the variable name just
after posting this and that worked. Just a bit confusing since sometimes you
need to reference things by ID and sometimes by variable name.
I'm using the latest 3.6 Beta build of WiX.
-Original Message-
From:
D'oh - solved. I was incorrectly escaping the square brackets, using a
forward slash instead of a backslash! All working great now.
Dan
On Wed, Jan 11, 2012 at 3:43 PM, Dan Gough wrote:
> Hi,
>
> I've successfully set up a few xml file configuration items using the
> XmlFile element, but I ha
That looks right. Please file a bug if the command-line help wasn't
helpful.
On Wed, Jan 11, 2012 at 7:32 AM, Peter Hull wrote:
>
> Am I right to say that the documentation for the insignia tool is a bit
> out of date in the 3.6 beta?
> The output from insignia /? doesn't mention the options -a
Yep, reasonable.
On Wed, Jan 11, 2012 at 6:28 AM, jhennessey wrote:
> I can also verify that BootstrapperApplicationData.xml doesn't contain the
> payload information...it's in the manifest file.
>
> I think it would be advantageous to include all of the information from the
> manifest in the Boo
Can you try chaning your condition to "NOT
FindDotNet40ClientInstallRegValue" and let's see if that works. I agree
this should work, I'm a little surprised it doesn't.
What version of WIX toolset are you using?
On Wed, Jan 11, 2012 at 2:00 AM, James Green wrote:
> Hi Again,
>
> I spoke too soon.
Hi,
I've successfully set up a few xml file configuration items using the
XmlFile element, but I have an instance that is not working as expected,
hopefully somebody out there can help!
This is a cut down sample of my xml file:
UPDATEME
U
Am I right to say that the documentation for the insignia tool is a bit out of
date in the 3.6 beta?
The output from insignia /? doesn't mention the options -ab, -ib or -im.
Is the following correct usage?
- To inscribe a database installer.msi with external cabs:
1. Sign the cabs
2. insignia -i
Hi everyone,
If I create a package with a custom action and an upgrade of same with the same
custom action, can I change the properties in the upgraded one in such a way
that when the patch creator is run the resulting MSP package not only does the
CA run in the patch, but also the relevant cha
I can also verify that BootstrapperApplicationData.xml doesn't contain the
payload information...it's in the manifest file.
I think it would be advantageous to include all of the information from the
manifest in the BootstrapperApplicationData.xml file (or at least write the
manifest to the tempo
Hi,
I need to select different types of features based on condition.
the selection is like tree model,if select the last child parent child
files also should include.
for this type any example??
Thank You,
S.Rohini
--
R
Hi Nikolaj!
Could you comment on whether your installer was signed (the bundle and the
actual engine which is unpacked out of it - see this link
https://sourceforge.net/mailarchive/forum.php?thread_name=CAHdHTVc1c2h3QuYsiXWcR8A1Xtk38Z3W2KCyAvuP3hMjYqKAiA%40mail.gmail.com&forum_name=wix-users
Ok, I have Paraffin working nicely now. I initially used Heat.exe with the
-suid option so that my IDs have friendly names, then modified the
resulting wxs into Paraffin format.
When I run Paraffin however, the resulting .PARAFFIN file only contains the
default namespace declaration, and not the
It all looks reasonable. I'd probably go back and examine the text file in
the 2 MSIs that you're building the patch from. It could be a build problem.
Do an administrative install of both MSIs and the version of the text file
from each admin install.
-Original Message-
From: Ulrich Proell
Just tried again and the XmlFile tags are no longer being removed, must
have made a mistake somewhere! Also confirmed that test values for
registry and service entries are left untouched also.
Plodding on, wish me luck!
Cheers,
Dan
On Wed, Jan 11, 2012 at 11:33 AM, Dan Gough wrote:
> Ok, I'v
Ok, I've got an initial fragment created and sussed out how to perform an
update. However, some of my components have entries, and these
get dropped when updating. I tried putting these entries into
.paraffinmold files, but then if I want it associated with the original
component, I end up getti
I think that the patch doesn't include this text file. At least ORCA shows only
the file "Szenariorechner.exe" to be changed by the patch. The file
"Version.txt" is marked as unchanged.
-Ursprüngliche Nachricht-
Von: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Gesendet: Mittwoch, 11
We have built a EXE with Wix 3.6 beta which are detected by Trend Micro
as "Malware behavior" and
we are looking for the reason for this.
This is the log entry from Trend Micro
I'd generate a verbose log while installing the patch to try and work out why
the text file is not updated.
The product version is just a property like any other and often seems not to
be mentioned specially. That confused me when I wrote my first patch.
-Original Message-
From: Ulrich P
We have built a EXE with Wix 3.6 beta which are detected by Trend Micro
as "Malware behavior" and
we are looking for the reason for this.
This is the log entry from Trend Micro
Thank you, this helps me a huge step forward.
Referencing the ProductVersion changes the version as desired. Is this written
in any documentation/book and I have overlooked it?
And I didn't know about the "View Patch" feature in Orca. This makes life a lot
easier!
My patch family now looks lik
I'll try and answer this but it's best to seek some other opinions too.
1. The order of patch installation wont usually matter. When you create a
patch, you target it at a particular version or even multiple versions (eg
patched/upgraded installations) and MSI works out the right sequence. See the
No not naive, I don't think anyone can really anticipate the degree that your
life changes.
Congrats on your new bundle.
Dave
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 11 January 2012 05:27
To: General discussion for Windows Installer XML toolset.
Subjec
The Wix help contains a section "Working with visual studio". The "Using
Project References and Variables" topic under there describes how visual
studio settings map to Wix pre-processor variables. The one youre interested
in is var..FullConfiguration. There are some others that may be
of use too.
Add a propertyref to the ProductVersion property. If your text file is in a
separate component from the exe then add a componentref to that too.
Orca will only show 2 tables because the rest of the changes are in 2
transforms embedded in the patch. Use the View Patch menu item in Orca after
loading
That is a example from one of our released products. The Id in the
patchbaseline is something you invent and only appears otherwise on the pyro
command line.
Why do you say that your files are relevant ?
-Original Message-
From: tome...@qualisystems.com [mailto:tome...@qualisystems.com]
Hi Again,
I spoke too soon.
I've confirmed that .NET 4.0 isn't installed on the machine. My Bundle has an
install condition of:
FindDotNet40ClientInstallRegValue = 0
Which is a RegistrySearch:
[011C:0408][2012-01-11T09:44:42]: Condition 'FindDotNet40ClientInstallRegValue
= 0' evaluate
Hi,
I keep getting an error message during the installation:
Error configuring ODBC data source: MyDSN, ODBC error 11: Driver's ConfigDSN,
ConfigDriver, or ConfigTranslator failed. Verify that the file MyDSN exists and
that you can access it.
There are 3 buttons on the message box: Cancel, Retr
Hi,
Thanks for that Rob. Looked at the logs and solved that particular issue. The
only issue I have left now is that the Bundle itself appears in the Add/Remove
programs.
Is there a way to hide it? Or should I be thinking about "hiding" the
application and use the bundle as the UnInstaller?
Rob Mensching-7 wrote
>
> The BootstrapperApplication.xml should list all the payloads, so if you
> really want to do this upfront, your BA should be able to it (plus using
> the WixBundleOriginalPath variable).
>
In the temporary folder I found a file BootstrapperApplicationData.xml. I
guess t
Orca just shows only 2 tables in the patch file: MsiPatchMetadata and
MsiPatchSequence. Therefore I wonder why the patch is doing anything.
Here are the steps to create the patch:
"c:\Program Files (x86)\Windows Installer XML v3.5\bin\candle.exe" patch.wxs
"c:\Program Files (x86)\Windows Installe
43 matches
Mail list logo
