Silverlight Feature Requests

Currently, there is not a general location to log Silverlight feature requests (we’re considering adding something on Silverlight.net for this). Given the lack of a central spot, I’ve taken a few threads on the Silverlight forums related to a Silverlight wish list as well as some comments from ScottGu’s Silverlight 2 blog post and Scott Barnes’ blog and aggregated the requests into a single list with frequency counts. I left off things that have already been announced in Silverlight 3 but left on others that have not yet been announced. There are numerous reasons why something will or will not appear in the next version of Silverlight including customer demand, time to implement, business need, security concerns, performance concerns, ability to implement consistently cross browser and cross platform, etc. Therefore, items at the top of the list below won’t necessarily appear in the next version of Silverlight – however, it’s likely we’re engaged in solving those problems in one way or another. Net result is the Silverlight product team does look at these requests and they do have some impact on shaping future Silverlight platforms.



Feel free to continue to make requests and I’ll try and update the counts every month or so. One thing that would help for requests is some insight into the scenario for the request (if it’s not obvious). For example, if you need UDP, include details on your scenario for UDP (e.g. P2P game and if so, we may be able to solve that with a more targeted API). One area to call out specifically for scenarios is requests for WPF and Silverlight compatibility. In general, if you want a WPF feature in Silverlight, call that out as a Silverlight feature request vs. a compatibility request (e.g. want triggers in Silverlight). If you have a need to share resources between Silverlight and WPF, call that out as compatibility and let us know what you’re doing that requires shared resources (to better help us determine how to focus our work in this area).