哪些具體步驟在Windows Phone應用程序部署

Question

• 如何部署在Windows 8設備的Windows應用程序UWP。請提供具體步驟

• 當試圖部署Windows應用程序部署工具。它的搜索爲XAP文件，但目前的版本會創建壓縮文件，所以不知道如何部署它

- 也建設使用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 

Answer 1

錯誤是用於Windows 8.x的舊版XMLVM管道。特別是對於多維陣列，它總是片狀的。如果您有像int[][][]甚至int[][]這樣的代碼，可能無法在舊管道中正常工作。

我們認爲要維持這種支持，但由於微軟針對低端Lumias推的Windows甚至10升級和決定停止Skype的Windows Phone的假設老8.x的目標是死的。

有關部署，並與UWP建設檢查出developer guide完整說明。

如Windows版8.x/7.x的桌面較早目標/片劑可以通過我們的臺式機提供服務/ JavaScript的建設目標，以便針對一個死的平臺可能不是我們最好的資源使用情況。