Silverlight Feature Suggestions
Welcome to the Silverlight feature suggestion forum. Please vote or submit a feature suggestion. If it is not a product feature request it might be moderated.
Please note this is a helpful tool in helping planning of ideas and understanding how developers use Silverlight. It may not always represent the actual priority list for the product team.
-
161 votes
-
Add IsDefault property to button
Add IsDefault() property to button, so that say for a login page, when the user enters data in textbox press enter key, the button click can be triggered. Similarly a cancel button is desired which is triggered on pressing escape.
157 votes -
Secure the future of Silverlight.
The future of the Silverlight must be secured by Microsoft.
Here are the "musts" to achieve:
* It needs to be bundled with C# and VB.Net so that as long as C# and VB.Net exists, Silverlight must exist too. This needs to be secured by Microsoft so that companies can invest on it.
* A tight integration with HTML 5 is also needed. The core abilities of HTML 5 must be able to be used in Silverlight projects. On top of it non-core abilities shall also continue.
* There must be a "light silverlight project style" which uses only HTML…151 votes -
Add Serialization Libraries to Silverlight
To support saving objects and states of objects better in Isolated storage without having to write cuttom code for all objects to store them in IS. Preferably Binary Serilization.
149 votes -
Make a Silverlight app render to HTML5 / SVG / CSS / JS
This is maybe something for the longer term. With the advent of HTML5 and rich features, Silverlight as a plug-in will become obsolete, because all functionality that is needed will be provided by browsers.
But that doesn't mean we want to start fiddling around with JavaScript, CSS, HTML and image sprites again.
The brand "Silverlight" can and should remain, as a framework for creating rich web applications with the tools we use today. We use the designer tools and/or define XAML and write code in C# like we do today, and at compile time, it all will be rendered to…
144 votes -
Is not enough property a TextBackground in class TextElement.
With the release RichTextArea, is not enough property a TextBackground in class TextElement.
144 votes -
Distribute Microsoft.Xna.Framework.dll for Silverlight 4
Making Microsoft.Xna.Framework.dll available in Silverlight for Windows Phone makes writing games in Silverlight easier but taking advantage of things like Vector2, Matrix, and SoundEffect makes it harder to share code between Silverlight for Desktop and Silverlight for phone.
Please release a version of Microsoft.Xna.Framework.dll for Silverlight for desktop so that we can share more code and more easily take advantage of XNA based open source libraries like physics engines.
143 votesA good bit of XNA is making it into Silverlight 5
-
SSL sockets / Support SslStream
SLL is only supported on HTTP sockets.
141 votes -
Support for Type properties in XAML
Allow controls to expose properties of Type Type, that can be specified declaratively in XAML.
Just like Style.TargetType...
136 votes -
Enhanced audio control
* The ability to detect/discard gaps in audio files;
* Easy features to set start/end point to play idle loops;
* Adjust audio pitch, ie play stream faster for higher tones and slower for lower tones;
* Enable events on sound filters - ie to build a visual equilizer134 votes -
Provide support for gzip compression when using Client network stack
It would be nice if the Silverlight Client network stack (vs. Browser Stack) supported gzip or deflate compression (content-encoding) for HTTP transmissions.
Currently, if one wants to take advantage of tuned, native compression for HTTP traffic, we must use the browser stack.
However, the browser stack can't be used for Out of Browser (OOB) apps.
This plays a role when sending large amounts of data between the client and the server using WCF. Compression/decompression of the WCF payload could of course be done in user code, but this will run slower than native code, and Silverlight doesn't expose any compression…
133 votes -
131 votes
-
Make DrawingContext available.
If you try to port WPF applications to Silverlight you will come to the point where you draw your Visuals by code via the Render method of DrawingContext. Unfortunatelly Silverlight does not support drawing by code. This feature is required for easily porting WPF applications.
130 votes -
122 votes
-
invest more resources in moonlight for realistic support in linux
invest more resources in moonlight for realistic support in linux
119 votes -
Add a DataContextChanged event
We often need to know when the DataContext on a Framework element has changed. We have the DataContextChanged event in WPF but not Silverlight. This leads to workarounds like the clever MyDataContext Dependency Property in this blog post : http://msmvps.com/blogs/theproblemsolver/archive/2008/12/29/how-to-know-when-the-datacontext-changed-in-your-control.aspx
It would be much better just to have the event in the first place.
118 votes -
XBOX 360
Silverlight on xbox 360 via xbox live.
118 votes -
android support is the first priority
android support is the first priority
115 votes -
115 votes
-
Support binding to dynamic objects
In WPF, we can bind to properties in dynamic objects. In Silverlight 4.0, we have the ability to use C# 4.0, but dynamic properties cannot be bound to. This is also true of objects that come from Ruby, making IronRuby much less attractive in Silverlight.
114 votes
- Don't see your idea?
