One .NET Framework for One Microsoft
Proposal is to create a “One Framework” project at Microsoft to encompass both technology development and a consistent message for customer engagement. A developer should be able to fire up Visual Studio and use C# and Xaml to target Windows Desktop, Windows Store Apps, and Xbox One along with a cloud deployed “click once” option to all these targets. There should be clear guidance that all of these will be both supported and enhanced for a long time to come. It would be a nice extra to have a fully supported by Microsoft targeting of C# to Android and IOS for which a Xaml runtime is seriously needed. If there is a battery life and performance issue on small devices by using this sophisticated programming technology then that should become a tooling issue and not a “pull the rug out from under the developer” issue. The .NET framework is at the heart of this and needs to be the driving force since all possible solutions flow upward from a solid cross-platform framework. The PCL effort leads to the LCD which feels like a return to .NET 1.0. Instead each platform needs the full 4.5 framework either native or via extension DLL exported by tooling. Persistent data is vital to any serious application and every target needs a universal System.Data or new cross-platform data core to cover common always offline scenarios along with cached scenarios to Azure etc. It creates a cognitive breach when developing a Windows Store App and a Windows Desktop Application becomes cross-platform programming! “One Framework” would restore the beauty of C# Xaml development for millions of developers and restore confidence in enterprise investment in the Microsoft development stack. The WPF in .NET 4.5 should be harmonized with the WinRT Xaml runtime via either a O/S update or tooling extensions that could create a harmonized virtual “One Framework” layer. The Blend tool needs improved promotion to the developer community and could be extensively enhanced for the One Framework. The Entity Framework could be enhanced with both fundamentals and tooling to support all targets, and also NoSQL and Object Graph serializations as a universal One Framework Data Persistence.Currently disenfranchised Silverlight LOB developers can be given a clear upgrade path to this single One Framework target particularly if tooling for Android and IOS targets are added. The scope implied by this proposal will hopefully not be a deterrent to consideration of the technical enhancements listed here.
Stephen Cohen commented
too much work they won't do it, but nice idea.
Andrew Stanton commented
EF needs to either die or have its relational complications fixed.
Trying to get to the "one" by rewriting netfx as netcore seems like a waste of time. I don't get the choice to not just start rewriting sections of netfx that needed xplat.
.Net standard and XAML standard is doing this
Kirill Illenseer commented
I'd like to see that. Right now, there seem to be 4 platforms. .NET, .NET Core, Xamarin & UWP with neither of them providing the full set of features. .NET Core, for example, is portable, but lacks a GUI framework and serial ports. .NET is not portable and UWP is even more so limited. Xamarin looks nice as it's portable and offers a GUI framework, but doesn't work on the desktop. Or the Raspberry Pi.
It's quite ironic that I get better service with a third-party platform (Mono) than from Microsoft.
Ces ventes peuvent être atteintes à partir des liens ci-dessus. robes habillées zara est devenu l'un de l'élément très classique et populaire qui zara femme solde attire un grand nombre de Jupes consommateurs désireux de l'acheter. Nous devons admettre que authentique produit magasins zara home peut également vous fournir une vie de luxe sans besoins du budget de rupture. Lors de l'achat en ligne, les bottes homme zara sont en la synchronisation avec les toutes dernières tendances et pour conserver votre rouge à lèvres ainsi que miroir. Depuis plusieurs décennies, le chaussures zara femme seul endroit pour obtenir des zara pret a porter de créateurs était à détaillants haut de gamme de vente au détail qui ont été traditionnellement qu’à partir des grandes régions métropolitaines. Le sac surdimensionné offre une grande stockage pour des choses qu'ils ne peuvent pas partir sans.
Certains doudoune zara femme matériaux de sont fantastiques, y compris les pierres précieuses et les métaux. Raisons femmes affluent vers ce zara international. Regard tentant de zara homme doudoune va certainement vous obliger à avoir votre 1 parce que les modèles matelassés offrent une visualisation particulière à ces dames qui sont à la rechercher de quelque chose et obtenir inventive inhabituel.Il y a beaucoup d'endroits pour trouver des fournisseurs de sac à main à la fois localement et en ligne. Toutefois, si vous êtes intelligent et que vous voulez la pleine valeur pour votre argent, alors il y a quelques façons dont vous pouvez identifier un sac original. Il existe deux modèles convertibles tours qui font de la plante grâce à la recherche de nombreux sites web qui est certainement amovibles.
Ils vendent des vetement à main uniques et authentiques. Rose mélangé à l'automne et la zara homme magasin saison d'hiver, et la laine laineux, comme l'ajout de fruits guimauves général, les gens ne peuvent vetement fille 12 ans zara pas se laisser aller. Probablement l'affaire d'un bon accepté manteau camel femme zara a grandi pour devenir l'archétype de, ce qui était vrai autochtones présenté à vetement zara fille si affligé critiques apparence, Blogueurs, rédacteurs en chef de grands magazines et les icônes de l'architecture qui instantanément acquit la poursuite à l'intérieur du principal, le parfum homme zara. Cependant, encore aujourd’hui, les gens ne peuvent pas trouver des ingrédients artificiels dans des vetement. Pour un zara le magasin noir, il veut être particulièrement difficile de la coupe. Personne dans leur aperception appropriée serait la promotion d'un sandales femme zara si elle est apte au travail plus, à moins qu'il ne soit affectée est ou volés.
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.
Developers Win! commented
If anyone is interested, this vote has been added and is being tracked with the Weekly Voting Reports on Developers Win. Along with 5 other votes that are related to creating a ubiquitous .NET client application model, it is responsible for a vote count totaling over 21,000 total votes at present.
You can see this week's report here:
Future weekly reports will be found here:
Please feel free to visit and share. Thank you for your consideration and support!
the solution is already here, it's called WPF, it already work great on high DPI, in Windows 10,
it can scale GUI elements independently with VSM, its a clear and straight forward path, for all the silverlight/ligthswicth and RT devs, handles touch beautifully and is the top GUI framework on the planet, having tested on 7 inch tablets, which is close enough to phone and yoga 2 pro 3200x1800, its the only thing that works, its time to wake up to the reality that Intel is #1, the top tablet is the intel based andriod samsung galaxy 5, x86 phones, and the solution is One,
give me a break! I need to target Phone/Tablet/Notebook/Desktop, I doesn't matter what brand,
I make software that's compelling enough to create demand for whatever target is required,
Modern Web stacks provide maximum reach already, what you are this is suggesting is so pointless, native apps rule, there are no Xamrin apps in the top 10,000 in Google play or Apple store, if is not going to be better than native , what is the point, if you know WPF learn VSM and say adios to your designer friend(they can go make bootstrap templates), MS has no way of stopping X86 Win phone, not that the remaining MetroMuppits aren't going to get what would appear to be exactingly what this suggest, they will call it OneCore Universal or some ****,
One code for all the things in your life on any size screen in your life, finally you can focus on creating the great new experience of the future. if your one of these designer diselopers, stay away from WPF, please find something productive to do elsewhere.
"he Blend tool needs improved promotion" spoken like a Blend MVP,
"One .NET Framework for One Microsoft."
One Microsoft, ..sigh.............wasn't that the baboons babble?
it's azure/WP world while it last, get your messaging straight, esp in your flaming headline,
do something that is good enough to be successful on any platform, then you'll have the resources to pursue any platform you choose, but the weak whining , I just know a little C# , can MS please make a solution so I can be a big boy too, please,
whaT A BURNETT
Md. Rashidul Hasan Masum commented
Need .Net runtime for OSX,iOS,Android, Linux. So that .net developers do not worried about cross platform development.
Stop spamming your stupid decompiler all over these posts, idiot. This is a place to improve Visual Studio, not your wallet. ****.
Is your competitors application written in .NET. Would you like to see how their code is written to better your program. Try This: http://architects.dzone.com/articles/decompiling-net-applications
Hi don, I agree that html would lead to a bad experience for the user but equally I think a common xaml framework would lead to a bad experience. If cost overrides quality then I go for HTML over xaml as I would also get a website for my money. Besides I feel that the variation of screen size on mobile devices would make it difficult to share the same code across all different screen sizes. Especially for a lob app. I also wonder how much embedding a xaml stack and all of the supporting rendering stack would increase the application size and decrese performance. I can't see apple or Google allowing Microsoft to install a shared os component on their platforms. It might prove very difficult to optimize the performance of a rendering stack that is not a integral part of the operating system. If you know pascal or c++ then I recommend you try embarcadero firemonkey who took the write once run anywhere approach which in my opinion ends up being bad on all devices.
Having said that it is just my opinion and by the number of votes you have for this you might get lucky. I wouldn't hold my breath thoiugh as this would be a challenge for any company to pull off.
martin - One of my ideas behind Cross-Platform XAML is to remove some barriers to universal uptake of .NET technology. If for example you show your enterprise management a prototype LOB App and then show it running right out of the box on everything, the dollar savings and time to market savings will make for an overwhelming case.
I think it's actually important to have a quick and dirty Bad UI on IOS and ANdroid (for example) just tin order to get the App working. After that, you can provide hooks in the framework to make it as Native feeling as you want, similar to how you move things in and out of the "shared" category in Universal Apps.
Right now, that idea that XAML prevents Native UI across platforms is blinding everyone to the obvious.
Let's enable developers with the choice to decide what is best for them!
The first part of this (common winrt/phone/xbox) seems to be solved with the latest release of visual studio and with the next addition to win 8 you will get store apps on the desktop (ala modernmix) for win 8 so at least for the latest versions of windows/phone/xbox we will get what I feel we need on those platforms.
It's a start at least and as programmers I guess we are all used to the idea of ship dates. The last one went well for us so fingers crossed for the dot net v next.
Here's hoping we get an MS supported C# on iOS and droid that wont cost $2000 dollars a year (Xamarin) on top of VS.
I am not sure about the idea of xaml support for iOS and droid. If it was a xaml wrapper around the existing iOS/droid user interface objects it would be acceptable - especially with the data binding features but trying to replicate the windows rendering stack on iOS/droid would in my opinion lead to apps that did not feel right on those devices.
Anyway success for the first part is not a bad thing. Thanks to all involved for their hard work...
DirectX 12 has been announced for 4Q of 2015.
"DirectX 12 will be supported across phones, tablets/PCs and Xbox One. The Direct3D 12 piece, which is what Microsoft disclosed today, will be supported in "Holiday 2015 games," meaning games delivered in the Q4 2015 timeframe."
Missing from all that is any plan to address XNA, or a translation layer for XNA.
And also missing is IOS and Android.
If DirectX 12 could have an optional translation layer on OpenGL, then One .NET could use a properly designed DirectX 12 as it's rendering layer.
Then XAML can be directly targeted to DirectX 12 for a nice performance bump and also a great universal UI for 3D Apps and Games.
XAML could have reach and impact as a supported UI for DirectX and would permit "native" 3D data visualization Apps etc.
Another possible part of the One .NET architecture diagram.
My update on the Xamarin purchase was deleted here. Now that the news is a bit older, I will try again.
Some sources for you:
Great first step! Now guys, please go buy Unity 3D so you can complete the cross-platform story with 3D. Next you need (and you can do it (and don't overthink it)) a seamless XAML across all the platforms including UI layer for Unity 3D. It is so so vital moving forward for your potential customer to download Visual Studio Express, open a template, hit F5 and it runs Everywhere. Let it get tweaked for native by the developer with various extra libs etc. Microsoft is in a very unique position to turn things around with tech nobody else can match. All you need is vision and unrelenting desire... Please bring One .NET to life!
I think this is a marvelous idea. However, given MS's history of treating developers like garbage "This time is different!" Riiiiight, Lucy.
MS is a marketing-driven company, not a technology company per se, IMO.
There have been comments here and there that claim this proposal is too ambitious. I think it is achievable by addressing 4 technologies: 1. Improved ability to tailor code generation for each target which may be part of Rosyln. 2. assign serious human power to .NET library creation so that each platform can have both platform generic and platform specific support to create a superset layer on top of the base code. 3. Improve MS Build to handle the custom assembly DLL packaging and wrappers for each platform and 4. Generate an adaptive XAML compiler and runtime to support a full common user experience across platforms as a common denominator with extention points for users to add "Native App UI" as they need it. i.e. Fast generation of your starter template app that has a Windows 8 look and feel on Windows, Xbox, Win Phone, Win WPF, Android and IOS just by default. The developer custom tailors it as needed for each platform. Many Enterprise LOB applications will be quite happy to stick with a Windows 8 look on their iPads and this can be sold as the new runs the same everywhere Silverlight replacement. What a great story! Anyone in Microsoft marketing out there want to tell this story?