Why are app developers waiting for Windows 8 before committing to Windows Phone?
I reached out to softpauer, the creator of the official 2012 F1 app on Blackberry, Android and iOS in the hope of some news on a Windows Phone port of their stunning app.
They were kind enough to reply with this short email…
Currently we’re not on Windows Phone 7, and probably won’t be. This is because only .Net codebases are supported by .Net, meaning we must maintain a completely separate version of everything. Another important consideration is this situation will probably change with the release of WP8, allowing us to use what we have already developed. We will still have to consider market share etc, but we hope this helps you understand why we’re not there at present. I expect many developers probably feel this way at the moment.
I thought oh well and hunted on ebay for a cheap iphone or droid ???
Nope! I instead researched how it would be possible to use a .Net codebase on WP7 as it would (hopefully) educate developers that may have been misinformed.
Quickly I found a few contradictory articles that read Windows Phone only runs C# and does not run VB.Net code, even official support forums are very misleading.
On the official MSDN WP7 forums I found the following quote:
“Windows Phone 7 currently is supported only for C#, which is why VS Express 2010 for WP7 only supports it.
At present, the product team has no immediate plans to develop, test and support VB.NET, for use with the Windows Phone.”
On the official Silverlight WP7 forums I find many questions asking about WP7 VB.net support with numerous questions and answers like:
Q: “Can I develop applications with VB.NET for Windows Phone 7?”
A: “No, You can’t.”
The truth of the matter is WP7 will run .Net codebase with a small amount of C# code additions.
Q: So, why are developers waiting? You decide.