 |
|
|
|
Making Silverlight Stand-alone Client
|
|
|
 |
|
Location: Blogs Andy's Blog |
|
| Posted by: host |
9/3/2008 10:47 AM |
One of the limitations of a Silverlight application is that it requires a browser and internet connectivity. What if you create an application that users put on their notebooks and take into the field where wireless access is unavailable?
Undoubtedly we will see many solutions to this connectivity problem, and Blendables has just released a beta of one such solution:
http://blendables.com/labs/Desklighter/Default.aspx
Desklighter is a little utility that creates an EXE file for hosting and launching a Silverlight .XAP file. You just point the utility at a .XAP file and it creates a hosting EXE which you can package with your XAP file into a ZIP.
Currently, Desklighter only generates a Windows EXE (no Mac or Linux yet) and requires the .NET Framework 2.0 on the host client. |
|
| Permalink |
Trackback |
Comments (3)
Add Comment
|
Re: Making Silverlight Stand-alone Client
|
By Anonymous on
9/4/2008 1:02 AM
|
Actually, the final EXE created by Desklighter holds the Silverlight content. So you don't have to package the XAP file while distributing it.
Sameer C Thiruthikad.
|
|
|
Re: Making Silverlight Stand-alone Client
|
By Anonymous on
9/6/2008 7:15 AM
|
|
Why not just make a WPF application in these scenarios?
|
|
|
Re: Making Silverlight Stand-alone Client
|
By Anonymous on
9/6/2008 8:21 AM
|
WPF requires .NET 3.0 or 3.5 which are still not widely distributed. On the other hand, .NET 2.0 has been around awhile.
And, _if_ Desklighter (or another distribution solution) releases a Mac and Linux (Moonlight) version, then this will have the added cross-platform bonus that WPF cannot provide.
Also, even though it is feasible to directly port a Silverlight app to WPF, there are still some incompatibilities.
|
|
|
|
 |
|
 |
|
|