Summary: This article covers about how to deploy a WPF application when its ready to release.
Introduction:After WPF application is built be it a Stand alone or Browser Based, it has to be deployed. Lets see what are the different deployment methods available and which type of method is suitable for different application type.
Elaboration:
Hosting:
WPF applications are hosted in a stand-alone window, much the same as a traditional Windows application or in a Web browser as a browser-hosted application, also known as XAML Browser Application (XBAP).
Deployment:
You can deploy installed applications from a server by using either ClickOnce or Windows Installer. You can also install an application from media such as a CD. You should test your application to ensure it works properly in your target deployment environment.
Security:
Applications installed by using the Windows installer run with the full set of code access security permissions, which enables them to access all system resources, subject to operating system security.
ClickOnce deployed applications will also run with full permissions because they are an installed application; however, because the installation is web based, the user will be prompted with a security dialog box, requiring them to accept the conditions for installing the application.
Installation:
Desktop WPF applications are installed on the user's system until they choose to uninstall it. This type of application appears on the Start menu and in the Add or Remove Programs control panel application.
Browser Applications:
- Hosted in a browser
- Must use ClickOnce for deployment
- Runs in a sandbox
- Use .xbap file for deployment
Installed Applications:
- Hosted in a stand-alone window
- Appears in the Start menu
- Can use ClickOnce or MSI deployment
Custom Control:
- Must use MSI for deployment
- Packaged into a DLL file
- Hosted inside an application
post a message... 
