Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Problems of what categories may arise when porting existing Windows Store applications to enble them running on Windows RT tablets? I’m especially interested in C# XAML games, but other situations are relevant as well (C++, JavaScript).
No porting considerations apply. Managed apps already dealt with processor architecture differences smoothly thanks to the jitter. Which made the difference between a 32-bit and a 64-bit operating system and processor invisible, as long as your pinvoke was kosher and you didn’t have a dependency on an ancient 32-bit component.
The extends to Windows RT the same way, it has an ARM jitter if the machine has an ARM core. WinRT is architecture agnostic. Having trouble with a dependency on pinvoke or COM is eliminated as well, you wouldn’t have been able to get your app published in the Store when you have such a dependency. WACK would have warned you about that early.
It just works. It was designed that way.