I got it fixed using a type 54 VB script custom action triggered on the
DoAction control event
-
Andy
MSI Developer
Schneider Electric:working:
--
View this message in context:
http://n2.nabble.com/Keyboard-Enter-key-press-does-not-validate-the-condition-tp4472158p4559736.html
Sent from the
bootstrapper will install .NET framework only if its not already available
on the system. So On Windows 7, bootstrapper just needs to apply the
respective language transform and launch the MSI.
When i run the MSI from the command prompt using the msiexec /i, it launches
without any problem.
I u
Without MSIUSEREALADMINDETECTION set the user can run the MSI, but
they can't install the application. Once they press the 'Install'
button (with the UAC Shield) they'll be prompted to enter a username
and password to continue. With MSIUSEREALADMINDETECTION set to 1 then
the message will display.
The registry removal is probably occurring in the package being removed. The
upgrading package's properties are not all passed to the packages being
removed.
The package being removed is given a property "UPGRADINGPRODUCTCODE" which
is the product code of the upgrading package. If you add "AND NOT
That's what I ended up doing. Just thought it odd that I couldn't ifdef an
environment variable and that I could define a wix variable named the same
as wix pre-processor syntax...
Cheers...
--
View this message in context:
http://n2.nabble.com/Preprocessor-ifdef-environment-variables-tp455599
Could you try a custom preprocessor extension?
- Original Message -
From: "John Nannenga"
To: "General discussion for Windows Installer XML toolset."
Sent: Friday, February 12, 2010 4:10 AM
Subject: [WiX-users] Preprocessor I think this is kind of odd:
>
>
>
>
>
>
>
>
>
...
The custom actions may require a bit of adjustment to work properly -
I didn't unit test this code.
As to payment ...
I want a bottle of Stubbs BBQ sauce, a fresh copy of the Ugly
Americans CD with Boom Boom Baby, Celis White, Shiner Bock or some
HEB swag .
Thanks for your input. I will try it out.
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Thursday, February 11, 2010 11:49 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] registry info extraction for native COM dll
I've
On 2/10/2010 12:10 PM, Vern Graner wrote:
> On 2/10/2010 12:21 AM, Sascha Beaumont wrote:
>> Without having the source code of those two EXE files you're running
>> and knowing what registry entries they modify there's no benefit to
>> creating an MSI, you might as well stick with the batch file.
In article <11d0172190691a40ac32bae21f609be2047...@exchange2010.wedge.iita>,
"Harvey, John Ctr USAF Warfighter's Edge"
writes:
> The Exit dialog happens at the very end after the InstallExecuteSequence. I=
> s it not part of the InstallUISequence? Or is some of the UI sequence delay=
> ed
Hi all,
I previously used (in Win 2003) this check to ensure that only a user
with admin privileges could run our msi:
Privileged
and that worked fine. However, we've moved to Windows 2008 R2 and now that
check doesn't seem to do anything in a non-admin user attempts to run ->
I've never met a COM Dll where the 64-bit registration was different from the
32-bit, so if there is a 32-bit version just use those. What's the difference
between them??
Phil Wilson
-Original Message-
From: Lian Jiang [mailto:lji...@microsoft.com]
Sent: Thursday, February 11, 2010
I haven't got a rar unzipper here, so I haven't looked at the log but:
I'll assume that there is a database that the user has updated and you want to
keep. So you make sure that the component guid is the same in both old and new,
then you sequence RemoveExistingProducts towards the end of the in
Well wipe that theory off the board then! Thanks for the info.
Phil Wilson
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, February 10, 2010 10:40 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installer hang
>From this post
>http://stackoverflow.com/questions/1628089/wix-3-using-heat-exe-to-add-bulk-files-to-a-new-wix-project-heat5150:
"Are you trying to extract data from x64 DLL's? That doesn't really work..."
-2009/10/28
I made a very simple 64 bit COM dll which heat.exe still complained with t
Hi all,
Is there a way to prevent removal of specific components when removal
is part of a major upgrade, as opposed to just an uninstallation?
My app creates certain registry entries at runtime (not the installer
but the actual software). I would like to keep these during an upgrade
while still
I think this is kind of odd:
Which compiles just fine.
What I want to be able to do is have the preprocessor condition logic based on
whether or not an environment variable is set.
Forexample:
But I cannot use because in the case when
the environ
DLL-based custom UI should be implemented using embedded-UI (which requires
4.5 or higher) or using your own external UI handler. The only other
supported UI is the Windows Installer authored UI you can author completely
inside of WiX. Anything else (like what you are doing) is not supported by
WI.
It is possible that your DLL failed to load some dependency of its own in
order to be harvested. Please check to ensure that your DLL's dependencies
are fully met from the environment you are calling heat.
-Original Message-
From: Lian Jiang [mailto:lji...@microsoft.com]
Sent: Thursday, F
In article <8b05023b1002110645p2eac15fbi79b2b478546cc...@mail.gmail.com>,
Jake Boone writes:
> No, the InstallUISequence.
In order to set properties in the UI sequence through a CA, the CA
must be an immediate CA.
Additionally, if you are setting properties in an immediate CA that is
invo
Ok, looks like i solved the problem in a different way.
The first problem i had was not being able to create a bootstrapper. I actually
found an installer editor that was quite intuitive,
but it had the problem it would not merge the files in a single executable item.
Then using 7zip i made a
Really depends on the bootstrapper and whatever interface(s) it is using to
launch both the framework installer and your MSI package. Do you have access
to the bootstrapper's sources?
-Original Message-
From: Andy.Kruger [mailto:appr...@gmail.com]
Sent: Wednesday, February 10, 2010 9:13 P
The Exit dialog happens at the very end after the InstallExecuteSequence. Is it
not part of the InstallUISequence? Or is some of the UI sequence delayed till
the end?
John Harvey
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, February 11, 2010 4
No, the InstallUISequence.
On Wed, Feb 10, 2010 at 12:38, Wilson, Phil wrote:
> Does "other parts" mean the ExecuteSequence? If they are being passed from
> the UI to the ExecuteSequence they'd need to be in the SecureCustomProperties
> list.
>
> Phil Wilson
>
> -Original Message-
> Fr
Can you restate the problem you are having as I don't understand from the
text below what your question is?
-Original Message-
From: Matteo Nicolotti [mailto:eversor...@hotmail.com]
Sent: 11 February 2010 13:23
To: WixUsers MailingList
Subject: [WiX-users] How to: using the MSBuild to cre
> -Original Message-
> From: wix-users-boun...@lists.sourceforge.net [mailto:wix-users-
> boun...@lists.sourceforge.net] On Behalf Of Pally Sandher
> Sent: Thursday, February 11, 2010 12:37 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] What burn
Following advice from his newsletter i was looking around to find a how to
guide to create a bootstrapper to create a combined installer for my
application and the .net framework. The suggestion also stated to use MSbuild
as the "less pain" choice to do so.
Ok, so I understand that MSBuild
Any ideas???
--
View this message in context:
http://n2.nabble.com/Do-not-remove-some-files-on-major-upgrade-tp4505876p4554525.html
Sent from the wix-users mailing list archive at Nabble.com.
--
SOLARIS 10 is the OS for
Hi,
How would I get a custom dialog(dll) to be on top when it is called
after "InstallFiles" in the InstallExecuteSequence?
Currently it brings up the dialog but it is behind the main one, I need
it to come in front or temporarily replace it until next is clicked
Here's the relevant par
Download WiX 3.5 & take a look. See http://wix.sourceforge.net/releases/
for the latest releases.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental So
How do you register the COM DLL? Heat will pull the information from COM
DLLs which implement the public function DLLRegisterServer (which is
what regsvr32.exe calls). If you're using some custom method like using
rundll32.exe or something you'll likely need to look into using RegSpy2
(see http://w
I am using the WixUtilExtension to register two EventLog sources:
The Registry keys are correctly created, i.e.
HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\MyApp1
HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Applicat
Install WiX 3.0 & run WiXCop.exe on your .wxs files to upgrade them to
the WiX 3.0 schema.
Shouldn't need to do anything more than that although I would recommend
looking at the things WixCop.exe changes as you could potentially clean
up/tighten your code by removing and/or replacing some things.
Thanks for reply.
I tried heat.exe in v3. Similarly, it works for managed COM dll and does not
for a native dll:
heat.exe : warning HEAT5150 : Could not harvest data from a file that was expect
ed to be a SelfReg DLL: c:\TEMP\station.dll. If this file does not support SelfR
eg you can ignore thi
Unless you're pushing out .NET 4.0 Framework betas, you can't install
any earlier .NET Framework on Windows 7, they're already embedded into
it. I suggest looking at what your bootstrapper is trying to do when
it's launching your MSI as it sounds like you're attempting to do
something impossible fi
Hi,
We have our installer created with Wix 2.0.
How easy is that to migrate to Wix 3.0?
Do I need to change all my UI screens and the fragments?
Thanks & Regards,
Srivardhan.
--
SOLARIS 10 is the OS for Data Center
Have you tried using heat.exe in WiX 3.0? The post you're referring to
is 3 years old which is very much pre-WiX 3.0. Unless there's some
requirement which means you can't upgrade to WiX 3.0 I'd strongly
suggest migrating. If you can't you could still try to use heat.exe to
generate the .wxs for yo
InstallUISequence runs before InstallExecuteSequence. If you change something &
don't have a time machine handy would you expect to see it change before you
changed it?
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve
Hi,
Maybe this is an old topic but I did not find much information online.
To install a COM component, I need to extract COM information from the dll
first. In Wix2.0, tallow.exe can extract the information from a managed COM
dll, but it does not work for a native COM dll.
According to post
h
Thanks got it working.
-Original Message-
From: Rob Hamflett [mailto:r...@snsys.com]
Sent: Thursday, February 11, 2010 10:13 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix Property change
Try something like this:
1
Rob
On 10/02/2010 13:22, Alex Wernecke wrote
Hi,
I resolved this myself. It seems there is no mechanism for CodeDomReader to
handle processing instructions. I fixed the issue by:
- Creating a new ProcessingInstructionElement to store the data from the xml
PI.
- Copy & paste source from CodeDomReader and hacking ParseObjectFromElement
s
Try something like this:
1
Rob
On 10/02/2010 13:22, Alex Wernecke wrote:
> Hi,
>
>
>
> How would I change a property's value when a button on a custom dialog
> is clicked? This property is then used to write that value to the
> registry.
>
>
>
> Thanks,
>
>
>
> Alex
>
>
>
> ---
I wasn't intending to actually distribute the mysql database, hence wanting the
installer to check it's a supported version. So it's only the client library
that would ever be included.
My understanding was using an LGPL library was fine as long as it was
dynamically linked, so people could b
43 matches
Mail list logo
