Create a Ubiquitous .NET Client Application Development Model
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:
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)
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)
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:
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!
this request has been commented on theregister:
Garry Lowther commented
Having been left out in the cold after our investment in .Net when Microsoft released Windows RT - a version of windows which did not run .Net apps (or even win32 apps) at all, I seriously doubt that Microsoft would reverse their decisions. We, like many other ISV's, have been gradually re-architecting our .Net code base to target non-Microsoft platforms, so Microsoft should take note of this suggestion to try and stem the exodus.
David Jeba commented
Microsoft should create a universal filesystem which is compatible to x64 and Ext and HFS
Developers Win! commented
What you have suggested can be easily achieved as soon as MS makes typescript.net (a .net language on the server side that compiles to .net IL). please see link below. And I recommend you all go vote for the idea.
Most important thing I would probably ever want from MS as soon as possible!
Developers Win! commented
That's the idea, Mike. :) At least for web-based scenarios. That is what JSIL/CSHTML5 uses for their rendering, at least. You can see its support matrix here:
Thank you for your input!
Perhaps use WebGL as the rendering surface;... with asm.js as CIL