03 June 2014
This might seem silly to point out because of course Microsoft is going to use their own browser as the basis for their own development technology. But, it is worth mentioning that your application will be running in a version of IE11. For developers who work on internal applications where IE tends to be the primary browser, this might not be an issue. But, for developers who write for the larger web, IE seems to always be the problem that needs to be worked around. Obviously, it is not as bad as the days of IE6. But, the IE legacy continues and has caused troubles more than once on our project. That being said, if you are having HTML/CSS issues, you will want to think of it in terms of IE11.
Your Presentation Framework Determines Your “Back-End” language
This certainly put a damper on my project at first. Coming into the project, not knowing anything, we had an expectation of a more ASP.NET MVC-like environment. For normal Windows Store applications, this might not be an issue because ideally you should put very little (if any) business logic into a tablet/phone application and let “the cloud” do most of the heavy lifting. However, in an industrial setting such as ours, network connectivity simply is not an option. And, most everything needs to be built into the tablet application.
Do Not Judge WinJS Based on the VS Project Templates
Some of the tags that are unsafe are a little funny. For example
/>. I am not sure why that is still a thing, and I would love to find
someone who can tell me why it is a security risk. But, others are
<applet />). I found the Microsoft documentation
to be really confusing on this subject and the restrictions to be
inconsistent. But, after quite a bit of experimenting, it makes some
sense and follows only a few patterns.
is licensed under a Creative Commons Attribution 4.0 International License