No, not easily nor recommended.
1-3 in the MSI would be under the InstallUISequence, 4-7 would need to be under
the InstallExecuteSequence which would be elevated (and ran non-interactivly)
which breaks 6a.
If a rollback on invalid credentials is feasible, then you could prompt for
credentials
I think the only way you could do this (if you can)
Is once the app is installed run a custom action to call your application with
the credentials entered in Step 3 (assign them to properties) depending on the
return code handle the error code, and continue on.
I am not really sure how you will
We had a similar goal and we were unable to do what you want. Our solution was
to write a program that periodically ensures the credentials are valid, and if
they aren't, display a window that prompts for them. We then run this program
as a custom action in the WiX package.
If you find some sol
I am checking with my team if the entire log can be shared. Meanwhile, here are
the information that you had asked for - 1. Condition for the CA is REMOVE AND
Privileged. I have verified on other machines that the CA runs during
uninstalltion. we also have automated tests to verify that the mach
Hi,
Let me try to be as clear about this as possible. We're using WiX to create
our MSI. We are looking to make a flow like this:
1. Welcome
2. EULA
3. Credentials
4. Install (directories, copy files)
5. Run app with creds on command line (our app has no GUI)
6. Handle return code from app
6a.
You should probably post the entire log. For example, we can't see the
custom action type to verify that it really is a (deferred?) call to that
Dll at that path, and that the folder property is referring to the correct
path, and maybe more around the point where the CA failed . A perhaps
unlikely
Does this link help?
http://blogs.msdn.com/b/astebner/archive/2011/05/16/10165211.aspx
Quoting Steven Ogilvie :
> Open up the MSI in ORCA and goto InstallExecuteSequence element.
> Sort the sequences in numeric order and see where your custom action
> is being called now, perhaps it has been
Open up the MSI in ORCA and goto InstallExecuteSequence element. Sort the
sequences in numeric order and see where your custom action is being called
now, perhaps it has been moved before the removefiles sequence (which is
sequence order 3500)?
Steve
-Original Message-
From: Suryadeep
Hi,
During uninstallation path, Our MSI executes a custom action
say RemoveXX which executes RemoveYY method from the dll MyDLL.
This custom action is scheduled before “RemoveFiles” in Install Execute
sequence. The MSI been tested many times over the past 6 months and has always
worked without
Thanks for that
Does that prevent the user from selecting another folder?
Thanks again
On 24 October 2013 17:10, santhosh yalamuri wrote:
> We have to set InstallFolder variable in burn bootstrapper.
>
> Example: Type="string"
> Value=""/>
>
>
> On Thu, Oct 24,
Download the Original Installer, attempt to repair the install, finish
the repair, and do a clean uninstall. Otherwise, download your new
installer, and this tool:
http://www.piriform.com/ccleaner
Use Tools > Uninstaller > Remove from Registry.
Out of curiosity, which step is failing? You
A shortcut would be to use Orca or similar tool and modify the MSI to disable
the CA (assuming it's a CA that's failing) and re-cache it as Phil suggests.
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Thursday, October 24, 2013 11:49 AM
To: General discussio
Thanks, I'll investigate both.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-do-you-bind-a-version-number-to-a-binary-with-an-autogenerated-wix-component-id-tp7589937p7589961.html
Sent from the wix-users mailing list archive at Nabble.com.
-
The safe way is to do a build with the same ProductCode that fixes the
issue (which may be as simple as removing the call to a failing uninstall
custom action) and installing it:
msiexec /I REINSTALL=ALL REINSTALLMODE=vomus
Or a patch that provides the same fix.
Other solutions (such as fiddlin
Hello,
The problem was the "test" server. In my opinion to many
tests,compilations, try & retry ...
With a new server, it uninstalls as expected, even with a different user.
Thanks a lot for your time.
Regards.
2013/10/24 Hoover, Jacob
> Is the same user installing and uninstalling? Do you
Is the same user installing and uninstalling? Do you have uninstall logs?
-Original Message-
From: BGINFO4X [mailto:bginf...@kztsoftware.com]
Sent: Thursday, October 24, 2013 10:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Bug or wxs problem?
Hello
We have to set InstallFolder variable in burn bootstrapper.
Example:
On Thu, Oct 24, 2013 at 3:31 PM, John Ludlow wrote:
> Hi all,
>
> We have an MSI for a client application which, if you have the server
> installed on the same system, must be installed in the same directory as
> the server
If the EXE is installed by the MSI, then you would need burn and a fake Exe
package later in the chain in order to be able to interact with the installed
exe. From there, you could interpret the return code.
If this is simply for installing and configuring the service, I would avoid the
exe al
Hello,
I have a big problem with W2008 R2:
The menu shortcuts aren't removed after uninstalling my aplication ... but
...
If I uninstall the same .msi with Windows7, ALL the shortcuts are correctly
removed, so the aplication is unistalled correctly. I'm using Wix3.8.
Is this a bug or a problem w
FWIW, be careful to back these changes out before doing upgrades. I don't
want to be somehow responsible for servicing issues resulting from the
baseline being in a non-standard state. There is already a WiX 3.8 weekly
release that supports VS2013 so these procedures should be for the most
p
I followed this procedure and it worked for me. I use the older WiX v3.6 so
I just copied the mentioned files over to my Visual Studio 2013.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-WiX-3-7-Votive-with-VS2013-RC-tp7589257p7589953.html
http://www.joyofsetup.com/2013/10/12/wix-v3-8-acceleration/
-Original Message-
From: Ronald Kanagy [mailto:ron.kan...@gmail.com]
Sent: October-24-13 10:18 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX v3.8 RTM release date
Hello,
What is the projected RTM release date
Hello,
What is the projected RTM release date for WiX v3.8?
Thanks,
Ron Kanagy
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, a
So you are using MSI? If you are using burn you can use ExePackage element.
Have burn run your MSI using MsiPackage to install service/etc and then run
your exe using ExePackage. Not an expert in what you're trying to do but a
thought.
Wes
-Original Message-
From: Rob Emanuele [ma
Hi,
On one of our machines, an uninstallation step fails
resulting in rollback of the entire process. I am looking for a way to force
uninstall a MSI (it would be okay if some of the MSI bits remain after the
uninstallation).
Is anyone aware of a way (or a tool) to do such force
uninstallat
Hi all,
We have an MSI for a client application which, if you have the server
installed on the same system, must be installed in the same directory as
the server.
During the MSI install wizard for the client application, we use AppSearch
to detect whether the server component is installed. If it
Hi Blair,
I wish it was that simple. It isn't a GUI application, it is a service (which
you can control from the command line). It has no GUI. We can write one, but
hoped we could just use the easy to develop GUI in the installer using WiX to
configure the service's config file. On top of t
27 matches
Mail list logo
