@JohnAskew: LOL! Thanks for trying.
Then why question if anyone really used it?
The fact that a large project caused it to choke is proof that it was a very niche product, meant to fit in somewhere between Excel/Access and a real .NET desktop app.
That was my understanding of Lightswitch as well. I mention the project to underscore the fact that people are using it.
Since the latest Lightswitch was built on HTML5 and Entity Framework, it shouldn't be too difficult to move the projects to Windows Store apps or WPF.
Yeah everything is easy since "skills transfer" and all. :S Based on the demographic you sited it's pretty clear the target audience for Lightswitch isn't developers that could easily make such a port to WS or WPF.
I think this move comes from a renewed focus at Microsoft on providing a few good solutions rather than throwing everything at the wall and seeing what sticks.
And I'm all for that. I'm so tired of the "lost decade" followed by the fail that was WP and W8/WinRT. And yes there was a W7 intermission between the two where it looked like Microsoft was getting is act together but alas WP/W8...
Read the comments of the blog post. Clearly there were more than zero users. Some appear to have built substantial projects with it -- large enough that it caused VS/Lightswitch to choke.
I don't think the MS fees are the problem so I am not sure that any change to them would help.
the key issue is that a lot of stuff is developed for the iPhone and the Android and the developers have no reason to bother with the windows phone, they do not see any money in it.
in some cases a developer is contracted to write an app and is only asked / paid to make the app for the iPhone and android so they have zero reason as the contract says what they must do to get paid.
the only thing I can see that might change this might be for Microsoft to offer to pay for apps to be ported to windows phone.
Yeah that would cost and be tricky to do but if a bunch of apps and the ads for them started including windows phone then that should over time generate more interest in more apps and so on...
That's the real problem here and one of the main reasons why these two Microsoft pundits dumped their WPs.
Writing for WP is kind of like writing a native app for Linux desktop. Even Microsoft picks and chooses what OS it's targeting native apps for and right now that includes Windows, iOS, and Android -- Linux desktop no where to be found. I'm not suggesting that's a bad thing; it's just the same problem WP faces -- market share rules the day.
I'm certainly not against furriners 'stealing our jorbs'; I'd love to see more talented competition. We (the US) has proven pretty conclusively, however, that if we can get workers in country and use undue force to keep their wages low, we'll do it. The only thing more efficient than a 3rd world sweatshop is the one in your backyard.
This is all about profit folks. Pick an industry and you find corporations all do it. And this is where we start talking about government regulations my friends...
I'm just happy the H1B limits that are in place today are helping to keep food on the table in my house. If those limits were gone our wages would quickly spiral downward.
That same could be said for the super successful "Telecommunications Act of 1996" that deregulated telecom and cable.