nd their descriptions).
>
> I suspect you'd see the same behavior if you created the shortcuts manually
> in your start menu.
>
> -Original Message-
> From: Kai Peters [mailto:kpet...@otaksoft.com]
> Sent: Friday, July 18, 2014 7:56 PM
> To: General discussion
Among many perfectly fine working shortcut defs I have the one below
(strings modified to protect the innocent, but length of strings is preserved)
When hovering over the menu entry it creates, the hint displayed should be
xx Notification Center
What is displayed, howe
og_reference/wixui_installdir.html
>
> and here:
> http://stackoverflow.com/questions/3296277/wixdefault-directory-in-wixui-installdir
>
> Carter
>
> Quoting Kai Peters :
>
>> Hi,
>>
>> i have built an MSI with WIX (WixUI_INSTALLDIR) which installs just fine
>> except
Hi,
i have built an MSI with WIX (WixUI_INSTALLDIR) which installs just fine except
for one thing:
If a user overrides the default install path, the install still goes to the
default directory.
I have no clue where to even begin looking...
What could be going on?
Thanks for any help,
K
---
Hi,
for every release we create 3 MSIs that install almost identical content but
there are a number of
small differences.
I was quite surprised to see that all three are absolutely identical in byte
size - there must be
some padding of sorts going on.
Is that a valid assessment, and if so,
0700, Phil Wilson wrote:
>>>> Well that means that you put it between InstallInitialize and
>>>>
>> InstallFinalize but before
>>>> InstallFiles, if that's where it's supposed to be. Did you try that?
>>>>
>>>> It'
> happening? You may also need a condition on your copy to prevent it from
> happening during a
> repair or uninstall
>
> Phil Wilson
>
>
> On Wed, Sep 18, 2013 at 5:48 PM, Kai Peters wrote:
>
>> My mistake for not specifying what else I had tried:
>&
always happen
> before any files are
> actually copied. If you need it to run after InstallFiles has physically
> copied files it should
> be marked deferred.
>
> Phil Wilson
>
>
> On Tue, Sep 17, 2013 at 10:45 PM, Kai Peters wrote:
>
>> Hi all,
>>
>> hope
Hi all,
hopefully my last newbie issue for some time (all previous issues have been
resolved thanks to the
great help from this list - thanks again!):
I deploy a CA "CA_CopyMasterIni" to copy a configuration file template from
location A to location B
if my customer's IT dept. has dropped one
Hi,
some of our MSIs spend quite some time on the required space calculating tab
and the question has
come up whether and how it might be possible to give users some indication that
the install is
progressing, say in the form of an hourglass cursor.
As always, thanks for any pointers,
Kai
is-running-from-td3058873.html
>> [2] I find it frustrating that different people can receive different
>> results. *sigh*
>> [3] http://msdn.microsoft.com/en-us/library/aa371857.aspx [4]
>> http://msdn.microsoft.com/en-
>> us/library/aa370562.aspx
>>
>> -
Hi Edwin,
no need to be suspicious of Depth and AssignToProperty (firstly, omitting them
didn't improve
things, nor did I expect it to) as Depth can avoid unnecessary file system
traversal (don't know how
deep the search would go if no Depth is specified but would assume that default
should b
Hi John,
I don't think so - I understand that perfectly. As I wrote in my post "...
where both the MSI & the
inifile reside ..." - the ini file sits right beside the MSI at the time of
execution, yet it is not
found by my Wix code, regardless of how I specify the directory for it;
absolute pa
s, thanks for all suggestions & your time,
Kai Peters
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level det
Hi Marlos,
yes, that's what is happening
BR,
Kai
On Thu, 15 Aug 2013 10:07:33 -0300, Marlos Gottschild wrote:
> Hi Kai,
>
> Is your file deleted if the previous (Wise) installation package is
> uninstalled?
>
> BR,
> Marlos
>
>
> 2013/8/14 K Peters
>
>> Hi all,
>>
>> my problem is this:
>>
>>
Hi all,
my next problem is this:
I have to deal with MSIs that are out in the wild (created with Wise); our next
MSIs will be created
with Wix since Wise doesn't exist anymore.
These old MSIs have installed an inifile that needs to survive a major upgrade
coming from the new
Wix based MSI
Hi all,
we deploy two MSIs to our customers which are almost identical.
The only difference is that 4 executables are slightly different (also named
differently) - all
other files are the same. The 4 executables also differ in their menu & desktop
shortcuts.
Could we use the feature element
On Tue, 30 Jul 2013 21:50:54 -0700, Blair Murri wrote:
> You can use the MajorUpgrade element (use the UpgradeCode you prefer in your
> Product element) and
> use just the offending UpgradeCode in the Upgrade element (to find/remove
> versions using it).
Blair,
I tried that but end up with two
Hi all,
I need to detect if a file with name xxx sits beside the MSI during install and
if it does, copy it
A) over top of a freshly installed file by the same name in the product
directory (in case of a
fresh install)
B) over top of an already existing file by the same name in the product
d
19 matches
Mail list logo
