I suggest you ...

Open source Silverlight

Blog post at http://davidburela.wordpress.com/2013/11/22/is-it-time-to-open-source-silverlight/

For all intents and purposes Microsoft now views Silverlight as “Done”. While it is no longer in active development it is still being “supported” through to 2021 (source).

However there is still a section of the .Net community that would like to see further development done on the Silverlight framework. A quick look at some common request lists brings up the following stats:

* 5,720+ votes to release Silverlight 6 https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3556619-silverlight-6
* Feature requests for Silverlight http://dotnet.uservoice.com/forums/4325-silverlight-feature-suggestions
* Microsoft connect list of active Silverlight feature requests: http://connect.microsoft.com/VisualStudio/SearchResults.aspx?KeywordSearchIn=2&SearchQuery=%22silverlight%22&FeedbackType=2&Status=1&Scope=0&SortOrder=10&TabView=1
Rather than letting Silverlight decay in a locked up source control in the Microsoft vaults, I call on them to instead release it into the hands of the community to see what they can build with it. Microsoft may no longer have a long term vision for it, but the community itself may find ways to extend it in ways Microsoft didn’t envision.
Earlier this year Microsoft open sourced RIA Services on Outer Curve http://www.outercurve.org/Galleries/ASPNETOpenSourceGallery/OpenRIAServices, it would be great to see this extended to the entire Silverlight framework.

6,178 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    David Burela shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    82 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anon commented  ·   ·  Flag as inappropriate

        Perhaps we should focus on asking that they bring XAML as an option to Blazor.

      • Rashad Rivera commented  ·   ·  Flag as inappropriate

        Come on!!! DO IT!

        Microsoft owe it to the developer community to release the code to open source. In addition, MS should do the same for other products that id buries by pulling its support. Products like Windows Phone 7, 8, 8.1 and 10 as well as Microsoft Accounting.

      • BR commented  ·   ·  Flag as inappropriate

        Not happening. Once MS puts a product in coma life support, it's on its way to the graveyard.

        MS will say, 'You've had 10 years to move off SilverLight, we're not supporting it and not providing a browser based plugin/desktop plugin anymore'

        My local auto dealer will not have oddball car parts for a car they sold 30 years ago. Why should MS?

      • birbilis commented  ·   ·  Flag as inappropriate

        If one also considers Silverlight-based UIs for Windows Embedded (for POS etc.), there must be more apps out there. MS never seems to have counted apps used in intranets, nor RIA apps, just treated Silverlight as if it was for Flash-style website animations and effects. It would be nice if they could eventually offer a .NET Core + XAML -> WASM solution, however it would still need some work to port stuff like SMF/MMPPF media framework

      • [Deleted User] commented  ·   ·  Flag as inappropriate

        There are lot of people who are thinking the Silverlight platform is only for the World Wide Web.
        There are billions of applications for intranet. I'm thinking to our large application to visualize the status of industrial processes (status of motors,valves, instrumentation, sensors and so on) in which each process item can be monitored as ui control with the capabilities of communicate with its proper service everywhere in the plant network using wcf. The designer who makes the visualized page of the process have only to drag the items from a toolbox and drop them on the page, then set its properties. Where is a technology which allow you to develope a similar framework (ui controls/design capabilities/communication infrastructure) in a reasonable slice time? Something is moving up, yes, but is experimental. So stop to tell "hey, Silverlight is superseeded",from this point of view it is not true. 6182 people who vote this idea are not stupid.

      • birbilis commented  ·   ·  Flag as inappropriate

        Well, we want .NET in the browser with XAML UI, it's not about Silverlight itself.

        When Microsoft decides to build it (on WASM or integrated as they do with Flash in Edge) we'll be happy to catch up

      • Matt Anderson commented  ·   ·  Flag as inappropriate

        There are people who actually want Silverlight to continue!? Why? Silverlight was doomed from the start and never really seemed to catch on. This seems to be like asking for IE6 support to continue. As developers, we see new tech come and go - that's life in the tech industry. Find newer technologies that are actually supported. Silverlight was so minutely used that almost nobody had the installation. MS tried this but the world didn't buy in on it. If they are allowing support until 2021, those of you using it have until 2021 to remove all dependencies. I think this is very generous of MS to allow support so your ancient projects still compile and to give you time to find and test new technologies that are widely supported.

      • jams commented  ·   ·  Flag as inappropriate

        They are spending all this effort on Blazor...running Mono in a browser with WebASM, when what they should have done, was port the Silverlight engine to run on WebAssembly....and retarget Silverlight to use NET Standard/NET core

      • Henry commented  ·   ·  Flag as inappropriate

        No. Microsoft will not spend millions of dollars vetting all of the Silverlight source code and releasing it as open source.

        Pretending that it costs $0 is a non-starter.

      • David "Einstein" Burela commented  ·   ·  Flag as inappropriate

        YAAAAS! What a great Idea. I love silverlight almost as much as I love writing VB macros for MS Access. While they're at it, I hope they open source Internet Explorer 4 and Microsoft BOB too so I can relive the glory days

      • Marc commented  ·   ·  Flag as inappropriate

        If MS won't open source the VB6 programming language they are unlikely to open source SilverLight.

      • James Chorlton commented  ·   ·  Flag as inappropriate

        @"S Collis" they have pulled support for Silver Light from VS2017. What makes you say that WPF is dead?

      • S Collis commented  ·   ·  Flag as inappropriate

        If Silverlight (and by extension WPF) are genuinely over, then they should just pull support from Visual Studio and let them die.

      • Anonymous commented  ·   ·  Flag as inappropriate

        The problem is Microsoft.

        Microsoft abandon developers.
        They abandoned Silverlight developers
        They abandoned LightSwitch developers
        They abandoned VB6 programming developers

        If you use Microsoft you just know they will abandon you too.

      • Anonymous commented  ·   ·  Flag as inappropriate

        The problem is Microsoft.
        Microsoft abandon developers.
        They abandoned Silverlight developers
        They abandoned LightSwitch developers
        They abandoned VB6 programming developers
        If you use Microsoft you just know they will abandon you too.

      • Jonathan Wilson commented  ·   ·  Flag as inappropriate

        It wouldn't surprise me if there are bits of Silverlight that Microsoft cant open up even if they wanted to (the media playback and copy protection bits in particular)
        That said, open sourcing all the bits that they CAN open source would be a good thing.

      • Christian Findlay commented  ·   ·  Flag as inappropriate

        I agree with this completely. But, I perhaps think that the goal post is shifting slightly. Silverlight fell out of favour basically because browser plugins fell out of favour. It now seems as though the tide will turn. Web Assembly will probably reverse the entire trend away from browser plugins (http://webassembly.org/). Web Assembly will allow binaries to be deployed through a browser in a properly sandboxed environment safely. I recommend that Microsoft open source Silverlight, and hopefully provide a pathway for Silverlight to be deployable over Web Assembly instead of as a browser plugin.

        I started this thread here so please make your voices heard:
        https://social.msdn.microsoft.com/Forums/silverlight/en-US/0d1d2e04-7092-4f38-8bc1-4365c808f873/silverlight-over-webassembly?forum=silverlightgen

        The Avalonia project (https://github.com/AvaloniaUI/Avalonia) looks as though it will eventually take over where Silverlight left off, but Silverlight is already a developed product. Why not port the graphics library to .NET Core so that it can be deployed over Web Assembly? We can't wait for a product like Avalonia which is only a community based project that is not officially produced by Microsoft.

        Please make noise about this. There is a future for the Silverlight graphics engine, or Avalonia if Microsoft put their weight behind it.

      ← Previous 1 3 4 5

      Feedback and Knowledge Base