On 12/13/13, 3:46 PM, Markus Ewald wrote:
> On 12/14/2013 12:18 AM, Edwin Castro wrote:
>> On 12/13/13, 3:07 PM, Markus Ewald wrote:
>>> warning LGHT1076 : ICE69: Mismatched component reference. Entry
>>> 'ApplicationStartMenuShortcut' of the Shortcut table belongs to
>>> component '
On 12/14/2013 12:18 AM, Edwin Castro wrote:
> On 12/13/13, 3:07 PM, Markus Ewald wrote:
>> warning LGHT1076 : ICE69: Mismatched component reference. Entry
>> 'ApplicationStartMenuShortcut' of the Shortcut table belongs to
>> component 'ApplicationShortcut'. However, the formatted str
On 12/13/13, 3:07 PM, Markus Ewald wrote:
> warning LGHT1076 : ICE69: Mismatched component reference. Entry
> 'ApplicationStartMenuShortcut' of the Shortcut table belongs to
> component 'ApplicationShortcut'. However, the formatted string in
> column 'Target' references file 'myappl
On 12/13/2013 11:21 PM, Bevan Weiss wrote:
> I would suggest using two separate components for it.
> Each Shortcut is really a file..
> Then each would get its own HKCU registry entry.
>
> Is your installer PerUser or PerMachine?
> The HKCU entry might not be so appropriate for a PerMachine install
I would suggest using two separate components for it.
Each Shortcut is really a file..
Then each would get its own HKCU registry entry.
Is your installer PerUser or PerMachine?
The HKCU entry might not be so appropriate for a PerMachine install.
Bevan
2013/12/13 Markus Ewald :
> Hi!
>
> I'm try
Phil,
No mention of Preselected in the log. However, I would have expected to see
Installed in the log too and it wasn't. The MSI was run with
Msiexec /l myinstaller.msi /l*vx install.log
The statement "if there any explicit action to force install of another
feature or component then the Cond
On 12/13/2013 5:30 PM, Nicolás Alvarez wrote:
> Is this an upgrade? Are you testing it with an older version of the
> product (containing a single shortcut) already installed?
No, it's a completely new installer and I do not plan to bother with
upgrade installs at all.
Regards,
Markus Ewald
-
It might be an optimization of sorts - if there is no
migratefeaturestate=yes in any upgrade specification then there is no need
for that action to be scheduled anywhere. It seemed to me that migrating
feature states seems to be the behavior you want from an upgrade based on
the scenarios you supp
2013/12/13 Markus Ewald :
> Hi!
>
> I'm trying to add a second start menu shortcut to my installer, but it
> just doesn't add the second shortcut. I can't find any message
> indicating why in msiexec's install log either.
>
>
>
>
>
> Id="ApplicationStartMenuShortcu
Hi!
I'm trying to add a second start menu shortcut to my installer, but it
just doesn't add the second shortcut. I can't find any message
indicating why in msiexec's install log either.
I've tried creating two components (
Yes I understand the difference between /t and /tr. They are two different
methods of getting the time stamp which means that comodoca (and each of the
other time stamp vendors) actually have two timestamp servers (authenticode
and rfc3161). I was just pointing out that for me when I tested it a
It might be removed on a reboot. If you had folder open, then windows
installer can't uninstall it. But I think it marks it for removal. I know for
sure files have this behaviour but I'm not sure about folders.
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.i
If you are going to dive into the source code there is another wix mailing
list, Wix-devs, you might want to sign up for. You are lucky thought as
someone just recently asked a similar question on wix-devs.
Here was one response:
1) Read this:
http://wixtoolset.org/documentation/manual/v3/wi
This was an issue but I resolved it by using:
/tr http://timestamp.comodoca.com/rfc3161
/tr Specifies the URL of the RFC 3161 time stamp server and is somehow
different than /t (I didn't dig into the differences)
It appears the problem I was encountering was due to the Crystal Report MSM
(see my
I think the behavior could be implemented easily in WixStdBA using a BA
Function (in Wix 3.8 or in Wix 3.7 with WixExtendedBA). I went down that
route before I, for other reasons, decided to implement a mba. I actually
prefer the wixStdBA and BA Functions, but the business wants XAML in a mba.
h
It's under src/ext/BalExtension/wixstba.
You don't need to change the dll. There's a theme file (theme.xml) and a
corresponding culture file (has a .wxl extension). You can change the .wxl
file to Chinese. Although if you look under Resources/1028 under the wixstba
folder you see the Chine
I just noticed that:
http://timestamp.comodoca.com/rfc3161
is returning:
000.0% #Bad request format or system error.
I do not know if this is related to your issue.
Using /t "http://timestamp.comodoca.com/authenticode";
seems to work for me.
--
View this message in context:
http://wi
You can use heat.exe (harvest tool provided by WiX Toolset) to generate a
wxs source file from your source folder.
For example, heat dir ".\My Files" -gg -sfrag -template:fragment -out
directory.wxs
Or you may write a tool yourself to do that work.
-邮件原件-
发件人: badrul [mailto:badruls...@yah
18 matches
Mail list logo
