Originally posted by ciplogic
View Post
Originally posted by ciplogic
View Post
Originally posted by ciplogic
View Post
Originally posted by ciplogic
View Post
1. You have to make sure all libraries you're using in .NET is implemented and fully functional
2. If you must use anything that is not part of .NET (new HW,new OS features,...) your smoked and has to do special solutions on each platform
3. For performance problems, you do not have just one setup to work around, you will have different problems on different platforms, just with .NET alone
THe rule I learned is, the more baggage you drag with you, the more possible problems you face and .NET is the biggest black sheep of them all out there.
If you really want to be multi-platform, use C and as many standard components as you can. Every platform I know have a well tested and fully functional C library. Of course, on platforms where some components are not available you have to implement additional support anyway. WP7 should be the last thing to implement for since WP8 is going to target C++/js/html5 as their prime platform anyway and .NET will then fade away. The market for WP7 is pretty marginal to begin with and is most likely only people whos only interested in mail, facebook,etc and not 3rd partt applications (if they were they would have gone for iOS or Android).
Comment