On 10-09-05 8:05 PM, Sohail Somani wrote:
> Hi there,
>
> Is there a way to see why Windows might start MSI repair automatically?
> Perhaps run some kind of integrity check on installed packages?
>
> I've got an issue with some shared files between application versions.
> While I've ensured that th
You can try but it crashes all the time.
On Sun, Sep 5, 2010 at 6:01 AM, Ben Lau wrote:
> Hi Rob,
>
> Thanks for reply.
>
> As 4.0 is not released yet , can I use ClickThrough with 3.5/3.6?
>
> On Sun, Sep 5, 2010 at 1:57 PM, Rob Mensching
> wrote:
> > ClickThrough was moved to WiX v4.0.
> >
>
On 10-09-05 8:05 PM, Sohail Somani wrote:
> Hi there,
>
> Is there a way to see why Windows might start MSI repair automatically?
> Perhaps run some kind of integrity check on installed packages?
>
> I've got an issue with some shared files between application versions.
> While I've ensured that th
Hi there,
Is there a way to see why Windows might start MSI repair automatically?
Perhaps run some kind of integrity check on installed packages?
I've got an issue with some shared files between application versions.
While I've ensured that the components have the same GUIDs, there seems
to be
I've attached a skeleton of my wix file. If you look at the
element, you can see that I've set it to show EULAAgreementDlg after
CostFinalize. However, this is during an admin installation. What would I
need to change for a standard installation?
--
View this message in context:
http://window
I've attached a skeleton of my wix file. If you look at the
element, you can see that I've set it to show EULAAgreementDlg after
CostFinalize. However, this is during an admin installation. What would I
need to change for a standard installation?
http://windows-installer-xml-wix-toolset.687559.n
This is just to let you know that I have released version 1.2 of
SharpSetup. Hightlights of this release include improved translation
support (creating translation templates with just a few clicks) and command
line processing (both generic options such as silent installation and
user-defined option
> No. "*" component guids are stable, not randomly generated.
If they are stable how are they generated and where the actual values
are stored? Can you explain this?
--
This SF.net Dev2Dev email is sponsored by:
Show off
Hi Rob,
Thanks for reply.
As 4.0 is not released yet , can I use ClickThrough with 3.5/3.6?
On Sun, Sep 5, 2010 at 1:57 PM, Rob Mensching wrote:
> ClickThrough was moved to WiX v4.0.
>
> On Sat, Sep 4, 2010 at 11:09 AM, Ben Lau wrote:
>
>> Hi ,
>>
>> I find ClickThrough information from
>> wi
On 02-Sep-10 17:12, Dave DaveLists wrote:
> Thanks for the thought. I checked this out when I started having
> trouble, actually, along with removing the reference and putting it
> back in manually. But it is indeed present on the command line.
Never seen that. It might be a problem with upgradi
On 05-Sep-10 04:36, Tenzen wrote:
> C:\delivery\Dev\wix35_public\src\ext\ComPlusExtension\wixlib\ComPlusExtension.wxs(44,0):
> error LGHT0102: The localization variable !(loc.ComPlusInstallExecute) is
> unknown. Please ensure the variable is defined.
Provide a .wxl file with those strings defin
On 03-Sep-10 04:54, Grigory Petrov wrote:
> 64-bit. The installer GUI for "Install just for you" says thet "you do not
> need local administrator privileges'. But it is not true - local
> administrator priviliges are required. What i'm doing wrong?
See "Single Package Authoring" in the MSI SDK f
On 02-Sep-10 22:29, Gao SuoLi wrote:
> After press Finish pushbutton, one executable app is triggered in one
> CustomAction.
>
> Because the app writes some values to registry, it demands administrator
> privilege.
>
> In fact, the UAC promote dialog is not shown, the app is failed to run.
MSI
On 03-Sep-10 01:59, Andres Juarez wrote:
> Ok, so if I use "*" as component GUIDs, this means that small updates are out
> of the questions for this approach, right?
No. "*" component guids are stable, not randomly generated.
> If a 32-bit component is contained in both a 32-bit installation
I am using version 3.5.2030.0 and I have these 63 errors.
1)
C:\delivery\Dev\wix35_public\src\ext\ComPlusExtension\wixlib\ComPlusExtension.wxs(44,0):
error LGHT0102: The localization variable !(loc.ComPlusInstallExecute) is
unknown. Please ensure the variable is defined.
[..]
63)
C:\delivery\
15 matches
Mail list logo
