Hans Karlsen (talk | contribs) No edit summary |
Hans Karlsen (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
Furthermore the same issue exists for code generated ViewModels and you must call : ClassLibrary1.ViewModelCodeGen_ViewModel1.'''ViewModel1.ReferenceToAllConstructorsToHelpWasmLinker'''(); | Furthermore the same issue exists for code generated ViewModels and you must call : ClassLibrary1.ViewModelCodeGen_ViewModel1.'''ViewModel1.ReferenceToAllConstructorsToHelpWasmLinker'''(); | ||
We will try to make use of the UNO framework together with MDriven in order to bring modeldriven benefits and one source to all the most common platforms: | |||
[[File:Unodiagram.png|none|thumb]] | |||
Revision as of 21:25, 11 May 2020
Update and notes on WebAssembly ( WASM ) status.
The WASM and MONO linkers strip stuff not discovered as important (used) and this has been an issue for MDriven since we do some reflection to discover what to use in runtime (after linker). This has caused exceptions with "missing method" information.
If you add tagged value to package "CodeGen.GenerateConstructorReferences" we will generate use of certain important things that the linker before has stripped. You must add a reference to this new method to tie your code to this and avoid stripping by linker: YourPackage.ConstructorReferatorToAvoidLinkerStripping() .
Furthermore the same issue exists for code generated ViewModels and you must call : ClassLibrary1.ViewModelCodeGen_ViewModel1.ViewModel1.ReferenceToAllConstructorsToHelpWasmLinker();
We will try to make use of the UNO framework together with MDriven in order to bring modeldriven benefits and one source to all the most common platforms:
