We managed to solve the problem, so for anyone who might run into the problem, the following information may be useful.
1) Modify the File.cs files as described in the blog post: http://mikaelkoskinen.net/durandal-phonegap-windows-phone-8-tutorial/
2) In addition to the above change, we found that it is also necessary to change the parameters read from the parameter into the readResourceAsText method in File.cs, as follows from the fact that PhoneGap does not require other parameters and it seems that it doesnβt pass them:
string[] optStrings = getOptionStrings(options); string pathToResource = optStrings[0];
3) For some reason, the combination of Windows Phone, PhoneGap and Durandal is also very fussy about the folder structure of the application. Initially, we tried to use our own folder structure, which made sense to us. (That is, do not use the "app" subfolder, which is used in the example with the Durandal bullet set, and also have the main.js, viewmodels and views folders in the www root directory.) As stated in this question, this was not a problem for any to another platform or in debug mode, so weβre not sure what the main problem is, but the folder structure must exactly match what Durandal for Windows Phone comes with in release mode.
For more information, we also got this job in PhoneGap 3.1. (The same modifications may apply as above, including a modification to the File.cs plugin.)
We also tried the PhoneGap assembly, which now supports PhoneGap 3.0, but the application crashes. This is due to changes that are required for File.cs that are not used in the assembly. Until this is fixed, it is not possible to use the PhoneGap assembly using the Durandal application for Windows Phone 8.
Brad
source share