WPF Installer

When building a WPF setup, you neet to solve the problem of .Net bootstrapping - if the client does not have .Net, your setup will not work.

Once you solve that, your setup will need to do couple of things:

request admin elevation to access certain file and registry locations
deploy all necessary files in %ProgramFiles%\
create proper entry in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall (if your application is compiled explicitly for x86, you'll need to do it in the Wow6432Node on 64-bit machines)
create a shortcut in All Programs\
do additional stuff like COM registration, file association and so on depending on what features your app provides

Most of these are provided for free by Windows Installer (MSI). You should really use something like WiX to build regular installer, even though it's not going to be as snazzy as WPF can be.

If you really want to be fancy, you could actually build custom WPF UI that's driven by the MSI engine, but the overhead of doing this is probably not worth it.

Look at this thread

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Abhimanyu K Vatsa15y ago
When building a WPF setup, you neet to solve the problem of .Net bootstrapping - if the client does not have .Net, your setup will not work.
Once you solve that, your setup will need to do couple of things:
- request admin elevation to access certain file and registry locations
- deploy all necessary files in %ProgramFiles%\
- create proper entry in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall (if your application is compiled explicitly for x86, you'll need to do it in the Wow6432Node on 64-bit machines)
- create a shortcut in All Programs\
- do additional stuff like COM registration, file association and so on depending on what features your app provides
Most of these are provided for free by Windows Installer (MSI). You should really use something like WiX to build regular installer, even though it's not going to be as snazzy as WPF can be.

If you really want to be fancy, you could actually build custom WPF UI that's driven by the MSI engine, but the overhead of doing this is probably not worth it.

Look at this thread
0