Wix installer custom action which runs a WPF application

Question

0.00/5 (No votes)

See more:

Hi
I have an existing installer based on Visual Studio Installer Setup project. The installer on install phase executes a custom action which opens a WPF application which allows the user to configure the application being installed(changes to configuration file, create / modify SQL server databases...). Since the Visual Studio Installer is no longer supported in Visual Studio 11, I need to re-implement the installer with Wix. I managed to create an installer but I am having difficulties with custom action which runs a WPF application. The WPF application used as a custom action is installed together with an actual "target application".
If a user cancels a custom action the install process has to be canceled.
Any ideas will be appreciated.

Uroš

Posted 1-Nov-12 7:59am

koleraba

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

barneyman · Answer 1 · 2012-11-01T12:22:00

Solution 1

Couple of suggestions ...

- just because vs2011 is the new kid, doesn't mean you have to throw the old kids away? Our build system still supports some 2003 builds
- Have a look at what the previous MSI was doing with Orca[^] - pay particular attention to the CustomAction[^] and InstallExecuteSeq[^] tables - review the docs for Custom Actions[^] and apply to WiX[^]

Posted 1-Nov-12 12:22pm

barneyman

Comments

koleraba 2-Nov-12 23:47pm

I wouldn't be thinking of re-implementing the installer, just because their is a new version of VS. The problem is the application for which I need the installer is still under development. The development team is swithing to the new version of VS and along with it to the new version of .net framework. This is why I think it would be best to re-implement the installer. Thank you for the links. I will check them out and see if they can help me. Do you maybe have some more concrete ideas?