3 ms·
Forget silverlight, .net itself has a questionable future on windows client. WinRT went back to C++. .NET is being positioned a server side technology.
by jeswin 15y ago
Forget silverlight, .net itself has a questionable future on windows client. WinRT went back to C++. .NET is being positioned a server side technology.
- kenjackson 15y agoIt depens on what you consider .NET. The CLR? The .NET metadata schema? C#/VB? The only thing that isn't incredibly important in WinRT is the CLR proper. But the other aspects of .NET play a huge role in WinRT. They even went and largely reimplemented the BCL. And the API design guidelines across the board are .NET based. WinRT looks a million times more like .NET than Win32.
- AndrewDucker 15y agoWinRT works just fine with .net.
- MatthewPhillips 15y agoWinRT supports .NET applications. But to your point, I'd wager that .NET is already used more on the server side than on clients apps as its use in enterprise line-of-business is massive.