Jerome Haltom
Jerome Haltom
It's the new SDK version: 10.0.26100.0
Not without seeing your project file, no.
Seems to fail for other reasons for me. Missing text files in my home directory. Also, is there a converted IKVM DLL uploaded to NuGet.org? Bad mojo.
Well, our guidance is definately to not do so. You will conflict with other usages of IKVM, and the produced DLL that you are distributing is not guarenteed to work...
Would hav eto dig into the code and understand what it's tryting to do. I do not know.
There are two sides to this issue: the runtime support for modules, and the static compilation support for modules. On the runtime side, we're going to have to implement tracking...
So, for IKVMC, I'm going to propose we work in at least two steps. Step 1 will be to implement the surface/loading interface of IKVMC ontop of a new C#...
IKVM generated assemblies are currently decorated with a JavaModuleAttribute, which expresses that their code originates from IKVMC, and enables the runtime support to load them 'specially', treating various other attributes...
Named modules can't read from unnamed modules. Automatic modules can't read from unnamed modules. So this seems to be pretty similar to strong naming in .NET: if you strong name...