如何在Windows 8设备上部署Windows UWP应用程序。请提供准确的步骤
尝试使用Windows应用程序部署工具进行部署时。它搜索XAP文件,但当前版本创建了zip文件,因此不确定如何部署它
- 同时构建Windows构建我遇到错误
Executing: c:\Program Files\Java\jdk1.8.0_60\bin\java -Dretrolambda.inputDir=C:\Users\Shai\AppData\Local\Temp\build7214845896341024238xxx\classes -Dretrolambda.classpath=C:\Users\Shai\AppData\Local\Temp\build7214845896341024238xxx\classes;C:\Users\Shai\AppData\Local\Temp\temp9143287062799870765.jar -Dretrolambda.outputDir=C:\Users\Shai\AppData\Local\Temp\build7214845896341024238xxx\classes_retrolamda -Dretrolambda.bytecodeVersion=49 -Dretrolambda.defaultMethods=true -jar C:\Users\Shai\AppData\Local\Temp\temp554571844756730289.jar Retrolambda 2.0.3
Bytecode version: 49 (Java 5)
Default methods: true
Input directory: C:\Users\Shai\AppData\Local\Temp\build7214845896341024238xxx\classes
Output directory: C:\Users\Shai\AppData\Local\Temp\build7214845896341024238xxx\classes_retrolamda
Classpath: C:\Users\Shai\AppData\Local\Temp\build7214845896341024238xxx\classes;C:\Users\Shai\AppData\Local\Temp\temp9143287062799870765.jar
Saving lambda class: com/iz/service/APIHandler$$Lambda$1
Saving lambda class: com/iz/service/APIHandler$$Lambda$3
Saving lambda class: com/iz/service/APIHandler$$Lambda$4
Saving lambda class: com/iz/service/APIHandler$$Lambda$5
Saving lambda class: com/iz/service/APIHandler$$Lambda$6
Saving lambda class: com/iz/service/APIHandler$$Lambda$7
Saving lambda class: com/iz/service/APIHandler$$Lambda$8
Saving lambda class: com/iz/service/APIHandler$$Lambda$9
Executing: java -Xmx1024m -jar win_xmlvm.jar --in=C:\Users\Shai\AppData\Local\Temp\build7214845896341024238xxx\classes_retrolamda --resource=C:\Users\Shai\AppData\Local\Temp\build7214845896341024238xxx\ZMT\ZMT\res/ --out=C:\Users\Shai\AppData\Local\Temp\build7214845896341024238xxx\ZMT\ZMT\src --target=csharp --app-name=ZMT Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.simontuffs.onejar.Boot.run(Boot.java:306)
at com.simontuffs.onejar.Boot.main(Boot.java:159)
Caused by: com.android.dx.cf.code.SimException: expected type int but found int
at com.android.dx.cf.code.BaseMachine.popArgs(BaseMachine.java:198)
at com.android.dx.cf.code.Simulator$SimVisitor.visitNoArgs(Simulator.java:331)
at com.android.dx.cf.code.BytecodeArray.parseInstruction(BytecodeArray.java:541)
at com.android.dx.cf.code.Simulator.simulate(Simulator.java:99)
at com.android.dx.cf.code.Ropper.processBlock(Ropper.java:678)
at com.android.dx.cf.code.Ropper.doit(Ropper.java:633)
at com.android.dx.cf.code.Ropper.convert(Ropper.java:250)
at org.xmlvm.proc.out.DEXmlvmOutputProcess.processMethod(DEXmlvmOutputProcess.java:958)
at org.xmlvm.proc.out.DEXmlvmOutputProcess.process(DEXmlvmOutputProcess.java:673)
at org.xmlvm.proc.out.DEXmlvmOutputProcess.generateDEXmlvmFile(DEXmlvmOutputProcess.java:423)
at org.xmlvm.proc.out.DEXmlvmOutputProcess.generateDEXmlvmFile(DEXmlvmOutputProcess.java:373)
at org.xmlvm.proc.out.DEXmlvmOutputProcess.processPhase1(DEXmlvmOutputProcess.java:345)
at org.xmlvm.proc.XmlvmProcessImpl.forwardOrProcessPhase1(XmlvmProcessImpl.java:209)
at org.xmlvm.proc.XmlvmProcessImpl.forwardOrProcessPhase1(XmlvmProcessImpl.java:206)
at org.xmlvm.proc.XmlvmProcessImpl.forwardOrProcessPhase1(XmlvmProcessImpl.java:206)
at org.xmlvm.proc.XmlvmProcessImpl.forwardOrProcessPhase1(XmlvmProcessImpl.java:206)
at org.xmlvm.proc.XmlvmProcessor.process(XmlvmProcessor.java:157)
at org.xmlvm.proc.XmlvmProcessor.process(XmlvmProcessor.java:137)
at org.xmlvm.Main.main(Main.java:53)
... 6 more
答案 0 :(得分:0)
错误是Windows 8.x版本的旧XMLVM管道。它总是片状,特别是对于多维阵列,例如如果你有像int[][][]
甚至int[][]
这样的代码可能在旧的管道中无法正常工作。
我们考虑过维持对此的支持,但由于微软即使对于低端Lumias也在推动Windows 10升级,并决定停止使用Skype for Windows Phone,我们认为旧的8.x目标已经死亡。
有关使用UWP部署和构建的完整说明,请查看developer guide。
Windows 8.x / 7.x台式机/平板电脑等较旧的目标可以由我们的桌面/ JavaScript构建目标提供服务,因此针对死平台可能不是我们资源的最佳用途。