I suggest you ...

Create a Ubiquitous .NET Client Application Development Model

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/351412/create-a-ubiquitous-net-client-application-develop.html
This vote is for developers who wish to see the idea of a ubiquitous .NET client application development model created by Microsoft and the Visual Studio team.

A ubiquitous .NET client application development model is a model that is defined in .NET-based technologies and is able to run in a multitude of runtime environments -- both native-compiled (store-hosted) and web-hosted.

A *very* rough image of the vision can be found here:
http://i0.wp.com/blog.developers.win/wp-content/uploads/2015/09/Vision.png

The goal is to enable *one* .NET Client Application Project to build deliverables for the following platforms:
1) Windows 10
2) Legacy Windows
3) *nix (Unix/Linux)
4) Droid
5) iOS
6) Macintosh
7) HTML5
8) ??? (Extendible to different, future platforms)

In order to achieve the above, a ubiquitous .NET client application development model should strive to possess the following qualities:
1) Native Cross-Platform Capable - For native-compiled/store-hosted scenarios (iOS/Droid/Windows Store)
2) HTML5-Compliant - For web-hosted scenarios, via .NET-to-JavaScript transpilation
3) Consistent User Experience - For brand recognition, reinforcement, and optimal usability across all known scenarios
4) Cross-Boundary Accessibility - For shared code/assemblies between server and client boundaries
5) Xaml-Powered - Harnessing one of the greatest inventions in Microsoft's great history
6) Object Serialization Congruence - Markup used to describe serialized objects is what is created in memory
7) Holistic Development Consistency - The same guidelines and conventions are used in both client and server scenarios

For more information around this idea and the qualities above, a series of articles has been created to discuss the notion of a ubiquitous .NET client application development model at length. You can view that series here:
http://blog.developers.win/series/bridge-to-dotnet-ubiquity/

Finally, this is intended to be a starting point for discussion, and not a final solution. THAT is meant for the experts there at Microsoft. :) Thank you for any support, dialogue, and feedback around this idea!

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

    499 comments

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

        I hear a lot of you speak about the UI.... Here's the deal. The UI/UX at this moment is owned by Angular 2,3,4,5,6,,, and React. You build your service for the backend and then you use frontend technologies. As an expert in frontend technologies I am not sure I am getting what this question is even striving for... It is quit ridiculous actually. The point is that front Razor templates or Java beansprouts or whatever is ridiculous... You cannot build a rich environment that way. Microsoft isn't going to bring about some white horse frontend technology that everyone will use. Remember Silverlight and flash? You can't do it. Javascript wins end of story. Now, can native platforms work. Yep, IOS and Android. or Middle ground... Xamarin or Cordova/Ionic... and again Javascript Wins. Get with the times gentlemen. I am pretty sure the ladies aren't confused as you all are.

      • Joseph commented  ·   ·  Flag as inappropriate

        “You cannot escape the responsibility of tomorrow by evading it today.” ~ Abraham Lincoln

      • Mike-EEE commented  ·   ·  Flag as inappropriate

        LOL @Marc ... negative but funny AF. ;)

        Also, @Anonymous 100% agree. Don't forget this issue has been "under review" for over 2 full years now. Without any remark whatsoever from admins. Pretty impressive. I still think someone got drunk one day and accidentally hit the wrong button. Either that or they are no longer working for MSFT. Maybe both. :P

      • Marc Roussel commented  ·   ·  Flag as inappropriate

        @FilipiVC Welcome to the unubiquitous world of finding the right solution in a time frame for which the technology is changing rapidly. In a nutshell, right now it's called MVC and a ton of frameworks with a not so powerful foundation.

        We still have to wait.....Waiting since a long time now....Meanwhile it's a pain in the...Blazor ? Hmmm not so sure. No GUI to develop UI UX We are still again at the age of the Autocad LISP

        A negative post sorry...

      • FilipiVC commented  ·   ·  Flag as inappropriate

        my biggest question is about web development and how to make client side interaction easy to develop and with a good look and feel like desktop softwares without tons of frameworks and code.

      • Anonymous commented  ·   ·  Flag as inappropriate

        @Mike-EEE
        The fact MSFT is setting up poll after poll instead of just tackling the 10 most voted UserVoice items tells a lot: They hate the answers they get. Stupid as we are, we keep refusing the rewrite all our UI in JS/CSS/"JS generator of the day" and keep asking to fix the mess they created with 3 (!) incompatible XAML dialects. Silly-us.

      • Mike-EEE commented  ·   ·  Flag as inappropriate

        @Антон, the problem with Bridge.net is that it does not support .NET Standard 2.0 or PCLs, so you ultimately end up with 2 separate codebases that results in twice the total cost of ownership to develop and maintain. Right now the only viable choices or approaches for a ubiquitous .NET are Blazor (as you mentioned) and Ooui:
        https://github.com/praeclarum/Ooui

      • Anonymous commented  ·   ·  Flag as inappropriate

        With this @Microsoft reorganization, with @Azure Cloud First, AI first and Quantum, I think that they will allow XAML to go where previous politics did not alow, ie. the Web. and cross-platform. Silverlight 6, with Universal XAML C# F# support.

        I fear we dump XAML and go a javascript, html and react like way, or some json way, or even a ELM F# way. This will a big retrocess, in my opinion. The engineers should go and fix all these issues in upcoming Universal XAML. and also adopt reactiveness and immutability on it.

      • Mike-EEE commented  ·   ·  Flag as inappropriate

        For those who have voiced their displeasure with Xamarin Forms, there's a nice thread on their very own repo with developers talking about its shortsighted issues and other well-deserved criticisms. It is also talking about ubiquitous technology in general. Nice read, IMO... that's why I am sharing it! ;)
        https://github.com/xamarin/Xamarin.Forms/issues/1789

      • Mike-EEE commented  ·   ·  Flag as inappropriate

        @Oliver ... i have had problems before with certain words triggering a block. No warning/indication/nothing. This was on Visual Studio's blog and not .NET's, however. Try doing a simple post and seeing if it works, with a message saying that you are having trouble as described.

      • Oliver Shaw commented  ·   ·  Flag as inappropriate

        Keep trying to post a comment on the calling all desktop developers, but nothing appears to show. Any one else had this problem?

      • birbilis commented  ·   ·  Flag as inappropriate

        ...and if he means for Canvas support (for rendering), there are some fallbacks for it too (using Flash etc.). Not sure if one uses WebGL for rendering if there are any decent fallbacks

      Feedback and Knowledge Base