[nobody31415]

Porting pure .Net apps should be trivial - if you also believed that Java was "build once and runs everywhere"!

But how many real world (especially corporate in-house) .Net apps don't also assume a windows file structure, or a keyboard, or a mouse or 8.3 names, or .......

So the problem is, do you sell it as "Windows" and deal with all the tech support and returns because it doesn't run Grandmas scrapbook app. Or do you run a massive ad campaign to tell everybody it's "Windows but not really Windows" !

edit: sorry won't let me reply to you -------------

That's rather the point - just porting the .Net runtime to ARM isn't the whole story. Can you have a single Windows8 design that does corporate desktops and smartphones?

If Windows8 for tablets has to have apps in "c:\program files", have 12 function keys, have a mouse with a wheel etc, for backwards compatibility then they are going to have quite a task to deliver iPad type tablet experience as well.

[dpark]

> But how many real world (especially corporate in-house) .Net apps don't also assume a windows file structure, or a keyboard, or a mouse or 8.3 names, or .......

I don't understand your arguments here. W8 is still Windows. The file system is still there. The keyboard is there if you plugged it in, and you can use the on-screen keyboard if not. Your app shouldn't be expecting 8.3 filenames unless it was written before 1995.

There might be complexities porting your app to ARM, but not because of the stuff you mentioned.