Next version of pb !

[Danilo]

So it seems there are way too many requests, all at the same time (Android, Raspberry Pi, .NET, ...)
and all for the next version.

[TI-994A]

ALL modern applications on Windows use a safe Environment and .NET/C++.NET/C#/Windows Runtime.

Not quite accurate, Danilo. Unless developed in a CLR environment, the .NET framework is not a requirement. And although some of its functions are available to native desktop apps, the WinRT layer is only required for Metro/Modern apps.

No single MS AppStore application uses Win32 API, running on Win 8.1 Laptops/Tablets or HoloLens goggles.

That too is technically incorrect. Even though the Win32 API may not be exposed to the developer, it is still very much in use by the WinRT layer. And the .NET framework as well.

Old Win32/Win95-style applications can only be linked to in the AppStore. They are not safe and un-checked apps.

Depends on your definition of safe.

The Microsoft Store: A wretched hive of scams and fake apps (ZDNet)

[Danilo]

My Windows Phone 7, Windows Phone 8, Surface 2 Windows 8.1 Tablet don't need Win32.
Everything is sandboxed .Net Apps there, and it works. They change the details with every
generation, but it's basically the same. They already said HoloLens will run Win10 Apps,
so it will be the same as the products listed above. Sandboxed, safe environment. No need to
care about the underlying processor. No GDI, GDI+, everything hardware-accelerated DirectX.

Still Windows developers mainly refuse to use all that stuff and simply ignore it,
so the AppStore gets not filled with good stuff, compared to other platforms.

The concept of AppStores is how computing should be. Search, Browse, Click [Install] or [Buy].
No boring Install and Updating like we know for decades. Works nicely with Apple platforms,
Android, etc.
Microsoft is trying for years, but on Windows desktop it is still not good enough.
Maybe that will change with Win10, when Apps don't need to be fullscreen anymore.
Not sure, we are watching all that for years already...

[TI-994A]

My Windows Phone 7, Windows Phone 8, Surface 2 Windows 8.1 Tablet don't need Win32.

Yes, it does. The only difference is the abstraction layer that is utilised in developing a particular app. Take a look at this, and notice the Win32 API in play:

Windows Phone API reference

Even when building atop the WinRT or .NET layers, the Win32 layer is never bypassed.

The concept of AppStores is how computing should be. Search, Browse, Click [Install] or [Buy].
No boring Install and Updating like we know for decades.

Actually, besides the increase in managed code, the architecture has not changed that much. The installation and updating processes remain exactly the same; only now, it's being done through a centralised repository, with a better degree of automation. That's all.

[Danilo]

My Windows Phone 7, Windows Phone 8, Surface 2 Windows 8.1 Tablet don't need Win32.

Yes, it does. The only difference is the abstraction layer that is utilised in developing a particular app. Take a look at this, and notice the Win32 API in play:

Windows Phone API reference

Even when building atop the WinRT or .NET layers, the Win32 layer is never bypassed.

Thanks for the link. So this is what got added with the Win8 "Going Native" campaign.

MS is still pushing .NET development across devices, this time using Xamarin:
- Developing Native iOS, Android, And Windows Apps In C# With Xamarin And Visual Studio 2015
- Native Mobile Application Development for iOS, Android, and Windows in C# and Visual Studio Using Xamarin
- Understanding XAMARIN – Create iOS, Android, Mac and Windows apps in C#.

The concept of AppStores is how computing should be. Search, Browse, Click [Install] or [Buy].
No boring Install and Updating like we know for decades.

Actually, besides the increase in managed code, the architecture has not changed that much. The installation and updating processes remain exactly the same; only now, it's being done through a centralised repository, with a better degree of automation. That's all.

The Automation is the key, compared to manual Install and Updating by using classic Installer dialogs with , [Next], [Next], [Next], [Next], [Finish].
Use less time for Installing and Updating stuff. I like it, and on Mac I prefer AppStore apps because of this Automation, especially for App updates.

[Fred]

To answer the first question, it's still in development

[Kiffi]

To answer the first question, it's still in development

[skywalk]

Cool.
Is this trailing the SpiderBasic release or independent?

[TI-994A]

...this is what got added with the Win8 "Going Native" campaign.

MS is still pushing .NET development across devices, this time using Xamarin:
- Developing Native iOS, Android, And Windows Apps In C# With Xamarin And Visual Studio 2015
- Native Mobile Application Development for iOS, Android, and Windows in C# and Visual Studio Using Xamarin
- Understanding XAMARIN – Create iOS, Android, Mac and Windows apps in C#.

Hello Danilo. Just FYI, none of the three speakers, James Montemagno, Anuj Bhatia, or Bruno Terkaly, are from Microsoft. In its desperation to expand the developer-base of its mobile platforms, Microsoft is jumping onto the coattails of such cross-platform tools in a hope to woo iOS and Android developers. Although a side benefit may be an increase in C# adoption, the apps themselves are not coded on standard Visual Studio libraries. The syntax may be purely C#, but the development is based heavily on Xamarin's libraries. As of recently, even the UI code is no longer native. Regardless of the platform, everything is built on bloated, third-party libraries (from 3 - 16 MB in size, after linking), which need to be shipped with the final product. Even worse, for Windows mobile apps, this is built atop .NET, and not directly on the Win32 API.

So, technically, even if Microsoft may like to tout this approach as Going Native, it is far from native. They are simply interested in increasing market share; at any expense. It's even been rumoured that they're interested in acquiring Xamarin.

[Danilo]

So, technically, even if Microsoft may like to tout this approach as Going Native, it is far from native.

Sorry, the comment about "Going native campaign" was ment to be a response/comment about your Windows Phone 8 link.
I tried some coding things on Windows Phone 7 few years ago, and there wasn't any native stuff. Just XNA and Silverlight stuff.
That changed with Windows Phone 8, but I never did something with it.

They are simply interested in increasing market share; at any expense. It's even been rumoured that they're interested in acquiring Xamarin.

Of course that's external Xamarin guys promoting their product. But MS itself promoted it heavily in my opinion.

I get some MSDN Newsletters (MSDN Flash, MS TechNet NewsFlash, Microsoft UK Limited, etc.) and had the feeling
that MS promoted Xamarin itself extensively. Quick search for "Xamarin" in my MSDN e-mails gives me 39 results
over the last 2 years, so Microsoft speaks about it very often in their newsletters.

There is also stuff like: Visual Studio for free... .NET an open source project? Yep, it's all true... (Microsoft on GitHub)
to be found in such newsletters. As you can see: Microsoft and Xamarin Expand Global Partnership.

[TI-994A]

...MS itself promoted it heavily in my opinion.

That's Microsoft for you, trying to conquer the world. In any case, it would always be better to go truly native.

Depending on the complexity of the intended application, Xcode, Android Studio and VB.Net are all pretty easy to use; and they're free too. With a little help from their respective online documentation, the good folks at StackOverflow, and step-by-step video tutorials on YouTube, it's quite possible to master them in no time.