I mostly do Windows Installer packaging for application delivery. I am a novice with packaging Silverlight applications. I had a few questions regarding the structure of a Silverlight 4 app for its delivery using a .msi. Looking for answers to these:

If anyone has packaged a Silverlight app: 1) Most of the sample Silverlight 4 apps that I have seen have a .xap file (having the compiled dlls and other binaries) and an .html as an entry point along with some resource files, this is the web based model. Is it possible to have a locally deployable Silverlight app for an Out of Browser experience with an .exe as an entry point and whatever dlls and resources it needs sitting next to it or installed elsewhere on the system?.

2) Do Silverlight application files install into the 'C:\Program Files\Product Name' directory just like normal WPF/GDI apps?. If not, what is the standard location to place them on the user machine?

3) Can Silverlight applications be installed/uninstalled/updated using standard Windows Installer authoring tools like the Wise Installer Studio or InstallShield Adminstudio, and are there any downsides/limitations in doing so?
0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity