StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>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.</p> <p>Once you solve that, your setup will need to do couple of things:</p> <ul> <li>request admin elevation to access certain file and registry locations</li> <li>deploy all necessary files in %ProgramFiles%\</li> <li>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)</li> <li>create a shortcut in All Programs\</li> <li>do additional stuff like COM registration, file association and so on depending on what features your app provides</li> </ul> <p>Most of these are provided for free by Windows Installer (MSI). You should really use something like <a href="http://wix.sourceforge.net/" rel="noreferrer">WiX</a> to build regular installer, even though it's not going to be as snazzy as WPF can be.</p> <p>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.</p> <p><strong>Update</strong>: Here are couple of links that can help if you still decide to build a WPF UI Setup:</p> <ul> <li><a href="http://msdn.microsoft.com/en-us/library/aa370053(VS.85).aspx" rel="noreferrer">Monitoring and Installation Using MsiSetExternalUI</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/aa370384(VS.85).aspx" rel="noreferrer">MsiSetExternalUI</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/aa369426(VS.85).aspx" rel="noreferrer">Installer Functions Reference</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload