How can we improve the Microsoft Edge developer experience?

Run Xaml / c# (like Silverlight) applications inside, without plug-in

Reinvent a way to develop RIA applicationsn without the need of plugin, directly into the browser and bypassing html and javascript.

The use of xaml and c# both sides (client and server) was a good way ... remember Silverlight ;-).

Can't you do something similar, essential for enterprises ?

You have to be a leader not just a follower as the abandon of SilveLight seems to be the sign.

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

    36 comments

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

        Xamarin should take care of iOS and Droid and of course Windows team will take care of Windows Store. The only piece is web, and there is another bigger vote asking for this here:
        https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/10027638-create-a-ubiquitous-net-client-application-develo

        Should take care of web via WebAssembly or transpiled .NET. Should be announced at //build!!!

      • Anonymous commented  ·   ·  Flag as inappropriate

        Now that you bought Xamarin to run XAML apps across different mobiles, extend it also to run in browser and have real universal apps.

      • Some IdiotSome Idiot commented  ·   ·  Flag as inappropriate

        @Anonymous, there are actually quite a few votes that total in the tens of thousands in this matter. I am sure MSFT will get it right in the next year or so. They had better. :P

      • Anonymous commented  ·   ·  Flag as inappropriate

        Universal Windows Platform should run in browser. I hope MS is running some analytics and realize nobody is using Universal Windows Platform or Metro applications from windows store. Neither companies or developers are investing in windows store applications. Windows mobile is such a failure also that MS have to invent a way to run android applications in windows 10 mobile because nobody is developing apps for windows mobile.

        I hope MS realizes there is lot of potential in creating LOBs applications in browsers using XAML/C# and that developers and companies WANT to invest on that as this an other threads show.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        +1000 to open the mind to interoperability :

        we need to have pure web to support current Html/JS pages and pure .net app development in a same environment to interoperate transparently.

        strange ... what is the ".net" extension for ?

      • phpphp commented  ·   ·  Flag as inappropriate

        >Microsoft Edge is focused on web standard
        ???

        What web standard ????

        Flash and Pdf ???? and not Silverlight ???
        Isn't Xaml + c# interoperable with Windows ?

        + With Silverlight we can interoperate with Html Pages in the same context of a Web Browser : Can you do this with UWP ?
        With Silverlight the end-user has not to change from a window to another ...

        And what about interoperate between Windows Platforms : W7, W8 and W10 ? Can you do this with UWP ? "Universal" ???

      • Anonymous commented  ·   ·  Flag as inappropriate

        Silverlight .. Win RT ... UWP ... and after that ?
        How long before Microsoft will shift its strategy for UWP ?

        2016 : "Our strategy with UWP has shifted"

        2017 : After the crash of our Edge Strategy we encourage to develop for our new WebKit Browser "YesMen" that support all the Chrome and Firefox standards ...

      • Anonymous commented  ·   ·  Flag as inappropriate

        And Universal is not universal, even for the Windows Plarform !

        With Silverlight we could continue to support a same application over Windows 10 and Windows 7, 8 ... what can we do with UWP in our enterprise ? Nothing !

      • PhilippePhilippe commented  ·   ·  Flag as inappropriate

        ... UWP is not a solution, until we can use it on the web, without the need of the store nightmare and local installations.

      • PhilippePhilippe commented  ·   ·  Flag as inappropriate

        Reinvent a way to develop RIA applicationsn without the need of plugin, directly into the browser, and without fluctuating incompatibles html and javascript frameworks.

        UWP is not a solution, Silverlight was THE solution until Edge arrived.

        The use of xaml and c# both sides (client and server) was a good way ... remember Silverlight ;-).

        Can't you do something similar, essential for enterprises ?

        You have to be a leader not just a follower as the abandon of SilveLight seems to be the sign.

        PS :
        Why to use Edge if there is no advantage to use it ?

        For pure Html/Javascript we can use Chrome or Firefox or anything else ... perhaps better than Edge in the future.

        Xaml / c# can be this advantage for early adoption of Edge in enterprises.

      • Mike-EEEMike-EEE commented  ·   ·  Flag as inappropriate

        Do you guys even understand your own technology? UWP is NOT the successor to Silverlight! Silverlight was meant and intended to be a C-R-O-S-S P-L-A-T-F-O-R-M runtime for .NET applications, which just so happened to be hosted in a browser. You cannot simply say that UWP is the successor when it cannot even run on a Mac!! Furthermore, this vote is asking you to help R-E-I-N-V-E-N-T a web-standard, interoperable technology that supports MSFT's .NET ecosystem. Otherwise, the cataclysmic developer divide that YOU are helping to foster and perpetuate only widens -- which ultimately hurts YOU!!!

        Seriously. Which intern posted this thoughtless and obviously ignorant refusal? This clearly shows the Edge team is a pack of #unnovative, paycheck-dancing followers and simply do not have the heart for innovation.

        I leave with this: in this thread (which at one point had SIXTEEN THOUSAND VOTES!!!), MSFT tells all 16,000 votes to start building apps for HTML5 instead:
        http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3556619-silverlight-6

        So which is it? UWP or HTML5? Again, do you guys even understand your own company and technologies? You just don't get it it. You should be building a technology that UNIFIES the schism in the .NET developer ecosystem, not separates if further. By providing two paths to build applications, you are causing confusion and wasting your resources! This ends up not only being expensive for the developers (and companies) who loyally follow you, but for the shareholders that invest in your cause -- this WILL hurt your bottom line and the golden handcuffs that bind you to them, team. Very sad precedent.

      • Mike-EEEMike-EEE commented  ·   ·  Flag as inappropriate

        Btw, does anyone actually read the vote? It's to R-E-I-N-V-E-N-T way of providing the functionality that Silverlight provided with the new Edge browser (and other Microsoft technologies).

        @Brandon, if you have used non-web technologies to create an application/system, and then tried to use web technologies, you will most undoubtedly know the difference. The ask here is to provide an IDE experience where C#/Xaml is used to create the applications, and then from there the application artifacts are created so that they can be run in a browser (and viewed/experienced anywhere). Technically, this is not an Edge technology specifically (per se), but the Edge team should most certainly be aware of it and assisting where needed -- as well as accounting for the .NET framework as a first-class citizen of its development experience.

        Also, Brandon, we all know about CSS: http://bit.ly/1NAxEps

        ;)

        As for coupling markup to layout, there are Styles in Xaml that are quite nice and robust, and work much better than CSS. Have you tried them? Also, have you seen the new Xaml layout in Windows 10? Very responsive-friendly. It should be, as Windows 10 is meant to be viewed on many different devices.

        I would also like to challenge you on my "silly" argument about div's. It's not an "element" ... it's a "div" ... conceptually it's an "element" but you wouldn't know it by looking at it. The point here is that it is not tied to any one thing, which is just a sliver of confusion experienced when dealing with a paradigm that is not congruent/consistent like Native/Xaml/.NET/Java.

      • Brandon PaddockBrandon Paddock commented  ·   ·  Flag as inappropriate

        @Michael Desmond -
        On the #WinDev slack, XAML developers are always complaining about things that are trivial to do in modern HTML/CSS. Your complaint about "div" is kind of silly. It's basically the "element" tag. Layout is controlled via CSS, which is actually a huge advantage over XAML. Doing a responsive layout in XAML is a real PITA, or completely impossible. In HTML/CSS, you can have a <div class="message-list"> where .message-list is a grid at >768px width, and a vertical listview at 768 or less. The lack of proper stylesheet support in XAML, and the tight coupling of markup to layout, is a huge weakness. It's weird to see someone tout that as an advantage when it clearly isn't.

      • Brandon PaddockBrandon Paddock commented  ·   ·  Flag as inappropriate

        Why would you want to do this with a proprietary non-web technology in the browser, when you can do the same thing with standards-based web technologies?

      • Mike-EEEMike-EEE commented  ·   ·  Flag as inappropriate

        @Tiago: How do you run ClickOnce on an iOS/Android/Mac/Linux? Clueless C#/WPF/Silverlight developers want to know. ;)

      ← Previous 1

      Feedback and Knowledge Base