A little menu:"JSB | Compile Cs to Js "
Main outputs: Streamingassets/javascript/sharpkitgeneratedfiles.javascript, all your logic codes are here.
Other outputs:
Temp/allinvocations.txt: Logging all logical code calls to the framework code (1)
Temp/allinvocationswithlocation.txt: Ibid., but also record the file name and line number of each call (2)
Temp/yieldreturntypes.txt: Record logic code, all types of objects followed by yield return (3)
(1) No use, just to see.
(2) Useful for subsequent steps to check that each call is valid. This can check 90% of cases. If this shows 0 errors, basic can run. But it is still possible to run the error, after all, Cs and Js there are many differences. In general, with this check, it is much more relieved.
(3) useful, with a similar effect (2). Since the monobehaviour process is driven by the JS handwriting implementation (since the conversion to JS, unity can no longer push your co-process), the full yield return object type is not supported. Currently this file is only used for viewing, not for the time being checked. If you want to know more about going to see Streamingassets/javascript/manual/unityengine_monobehaviour.javascript.
Back to: Unity Code Hot Update Scenario jsbinding + Sharpkit Home
Jsbinding + sharpkit/compile Cs into Js