I'm not having a whole lot of luck with anything I am trying. No matter
what the certificate uninstall action keeps running (and breaking).
One thing that I don't understand is that I created an MSI built with 3.5
and then did a /fv to replace the cached MSI . This allows the uninstall to
occur, b
When I last regasmed anything, I was using Wix2 and the tallow tool but the
process should apply to heat too.
Regasm /regfile doesn't create type lib, so use tlbexp to create a type lib.
Use elements to register the type lib.
Use regasm /regfile to create a registration file.
Use heat to conver
If you are only wanting to register these DLL's for your own private usage
within a single application, I'd strongly suggest using registration free COM
and deploy them with the application. This allows the OS to load the info into
the activation context at application start, and would allow you
To answer my own question it does seem to copy file from the SourceFile to Name
attributes only if Compresses="no" (I had the same package reference twice and
one was set to "no").
Neil
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 29 August 2012 13:29
To:
Hello folks,
me again :-D
The next problem I must solve requires some experience that I do not have, so I
hope I can get good advice as usual from here :)
Base problem is quite easy: I need to register some DLLs during installation
process.
But my initial situation is like this:
I do not inst
Ok, finally I just implemented a custom action, that performs the string
manipulation and sets a new property to the session. This property value I can
grab easily from within my product.wxs:
After that I can refer to the propery named ``FOOBASEPATH`` where
No I don't think so, looks like using the merge module is your best option.
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 29 August 2012 14:34
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Install the Visual C++ re
On 29/08/2012 16:08, Natalie Carr wrote:
> As I said in my original question I can't use merge modules as I've been
> asked to use this one EXE file. Trying to figure out a way to use it.
I think this is one of those cases where you have to ask "why". Why are
they requiring you to use the .exe in
Hi,
As I said in my original question I can't use merge modules as I've been
asked to use this one EXE file. Trying to figure out a way to use it.
Thanks
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: 29 August 2012 15:43
To: wix-users@lists.sourceforge.
Are you saying you need the path to the MSI in order to be able to deduce a
path to the EXE files outside of the installer that you want to create
shortcuts to? If so, have you looked at this from the MSI side as far as
SourceDir and/or MsiGetProductInfo (
http://msdn.microsoft.com/en-us/librar
including merge module of vcredist_x86 in your installer is the another way.
On 8/29/2012 7:03 PM, Natalie Carr wrote:
> Neil, I only have the one prereq. Burn has their own UI and I know you can
> add yours from the MSI but it still shows the burn one. Is there any other
> way than using burn?
>
Do you guys think it will be feasible to start on my own bootstapper
application implementation rather than using burn for installing multiple
prerequisites?
Kind regards,
Christoffel le Roux
-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sen
Neil, I only have the one prereq. Burn has their own UI and I know you can
add yours from the MSI but it still shows the burn one. Is there any other
way than using burn?
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 29 August 2012 12:27
To: General discussio
I have attempted to rename the dll I built in the wixstdba directory to be
WixBalExtension.dll and copied it into my Wix3.6 Toolset directory. When I try
to build my bootstrapper it gives me an error that the dll could not be loaded.
What do I need to do to properly build a new WixBalExtension.d
Dario, did you ever find a resolution to this issue?
On Wed, Sep 22, 2010 at 8:52 PM, Bob Arnson wrote:
> On 22-Sep-10 20:15, Dario Amiri wrote:
> > So it looks like no one has any advice for this issue. Is there any way
> > I can submit this as a bug?
>
> The WiX home page has links to the bu
Hi guys, Is it possible to install multiple prerequisites using burn?
You can only specify one WixMbaPrereqPackageId element according to the schema
and I also tried
And
But
What causes burn to copy a package from the source folder to the location
pointed to be the Name attribute when you build a bundle?
I find that sometimes this happens but can't figure out the logic. It makes
sense that it does this for non-compressed packages but I am also seeing it
happen for
Those are the search element for use with burn in 3.6+. I have found that the
burn searches are capable of detecting if a key exists or not. However,
these won't be useful to you if you aren't using burn (they won't execute in
an MSI).
--
View this message in context:
http://windows-installer-x
I think you should use merge module of VCResdist.
On 8/29/2012 3:56 PM, Natalie Carr wrote:
> Hi, Hope someone can help me. I'm trying to install the Visual C++
> redistributables file vcredist_x86.exe
>
>
>
> I can't use merge modules as I've been asked to use this one EXE file. I
> added it t
I would if you need to install prereqs. (I think the release is only a few days
away.)
Neil
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 29 August 2012 12:11
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Install
Thank you very much, I'm using WIX 3.5 at the minute, Would u recommend
moving to 3.6?
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 29 August 2012 11:54
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install the Visual C+
Hi guys, isn't doing installers FUN? LOL
I know from the previous versions of WIX that you could not verify if a
registry key exist using a RegistrySearch you had to create a custom action to
do so.
But I found this is the schema documentation v3.? of RegistrySearch:
Result Enumeration
I'd suggest using burn to do this; this is the code I am using to install
vcredist.
http://download.microsoft.com/download/d/d/9/dd9a82d0-52ef-40db-8dab-795376989c03/vcredist_x86.exe
?>
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
Hi, Hope someone can help me. I'm trying to install the Visual C++
redistributables file vcredist_x86.exe
I can't use merge modules as I've been asked to use this one EXE file. I
added it to a bootstrapper using this code:
Microsoft Visual C++ Redistributables
But thi
Sorry but I can't really help - that is quite an odd requirement and I am not
sure how burn will work on upgrade and repair as the code won't be running from
your folder.
Neil
-Original Message-
From: Christian Hausknecht [mailto:chauskne...@beracom.de]
Sent: 29 August 2012 10:58
To: G
Ok, I try to explain the background:
The installer will be located in a remote folder in which most executables of
the client are located. The Clients are practically not really installed on the
local machine, only Shortcuts with the path to the executables on the remote
folder are generated (b
Just stepping back at bit but why do you need the source of the burn install
passed into your MSI?
Neil
-Original Message-
From: Christian Hausknecht [mailto:chauskne...@beracom.de]
Sent: 29 August 2012 10:39
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-us
Ok, my idea was good, but there is a problem with it. Burn does not support
searching *during* the installation process. So even if I have the correct
sequence in my chain, the RegistrySearch is always done at the beginning before
any packages are executed :-( Therefore my little helper program
I hadn't noticed that in Windows 8. You could call dism in the same way - see
my post "Installing Windows Features with Burn". As far as I am aware you don't
need internet access or the original media, .NET 3.5 is just a feature that
needs enabling.
Neil
-Original Message-
From: Neil H
I think this probably sums it up, fail deployment until the .NET Framework 3.5
is installed, or deploy without it and rely on the shim prompting for
installation.
http://msdn.microsoft.com/en-us/library/windows/hardware/hh975396.aspx
Neil
---
Hi thanks for all the help, I resolved my issue by just reverting the custom
action back to .net 2 and specifying the correct framework version in my custom
action configuration file.
This was the simplest way to support the older installer code. As stated by
Jacob there wasn't any reason for
Interesting
Windows 8 say's (ocsetup /? ) OCSETUP has been deprecated. Please update your
scripts to use DISM.exe to add or remove optional components from your system.
I see this being a serious problem in deploying software timeously, before I
could just install the .NET Framework, now i
32 matches
Mail list logo
