7.2.4630.5

Original Release Notes: https://web.archive.org/web/20200926140429/http://weblog.ikvm.net/PermaLink.aspx?guid=926e3554-259e-49a6-82fc-459fbd61ac19. This release originally happened on SourceForge on 2012-12-10.

IKVM.NET 7.2 Released

I've released IKVM.NET 7.2 to SourceForge and NuGet. The binaries are identical to the ones in release candidate 5.

Release Notes

This document lists the improvements, known issues and incompatibilities.

What's New (relative to IKVM.NET 7.1):

• Integrated OpenJDK 7 u6 b24.
• Improved java.util.concurrent performance.
• Removed org.omg.PortableInterceptor.UNKNOWN class, that is not part of [Open]JDK rt.jar.
• Added ZipFile constructor that was added in Java 7.
• Add support for running with headless awt toolkit.
• Changed ikvmc to apply custom attribute annotations on annotation types to the corresponding custom attribute that is generated (and allow AttributeUsageAttribute to override the default AttributeUsageAttribute generated from the @target annotation).
• Added app.config files for executables to allow them to run on .NET 4.5 on Windows 8 without triggering the .NET 3.5 auto download.
• Added (optional) support for building without System.Core.dll dependency.
• Disabled AppDomain.ProcessExit hook to run shutdown hooks when running on Mono to workaround https://bugzilla.xamarin.com/show_bug.cgi?id=5650.
• Several verifier fixes.
• Several metadata reflection fixes.
• Fixed two try/finally block code gen bugs.
• Various other minor fixes.
• IKVM.Reflection: Many minor bug fixes and improvements.
• IKVM.Reflection: Added most new .NET 4.5 APIs.
• IKVM.Reflection: Added experimental support for generating Windows Runtime (.winmd) assemblies.
• IKVM.Reflection: Added missing DefineResource() APIs to ModuleBuilder and AssemblyBuilder.
• IKVM.Reflection: Added co-/contra-variance support to Type.IsAssignableFrom().
• IKVM.Reflection: Added support for using the .NETCore v4.5 aka Metro profile mscorlib.dll.
• IKVM.Reflection: Added UniverseOptions.DisablePseudoCustomAttributeRetrieval to disable returning pseudo custom attributes.
• IKVM.Reflection: Bug fix. Ignore unknown metadata streams.
• IKVM.Reflection: Bug fix. Set AddressOfRawData in IMAGE_DEBUG_DIRECTORY.

Runtime

• Code unloading (aka class GC) is not supported.
• In Java static initializers can deadlock, on .NET some threads can see uninitialized state in cases where deadlock would occur on the JVM.
• JNI
   
  • Only supported in the default AppDomain.
  • Only the JNICALL calling convention is supported! (On Windows, HotSpot appears to also support the cdecl calling convention).
  • Cannot call string contructors on already existing string instances
  • A few limitations in Invocation API support
     
    • The Invocation API is only supported when running on .NET.
    • JNI_CreateJavaVM: init options "-verbose[:class|:gc|:jni]", "vfprintf", "exit" and "abort" are not implemented. The JDK 1.1 version of JavaVMInitArgs isn't supported.
    • JNI_GetDefaultJavaVMInitArgs not implemented
    • JNI_GetCreatedJavaVMs only returns the JavaVM if the VM was started through JNI or a JNI call that retrieves the JavaVM has already occurred.
    • DestroyJVM is only partially implemented (it waits until there are no more non-daemon Java threads and then returns JNI_ERR).
    • DetachCurrentThread doesn't release monitors held by the thread.
  • Native libraries are never unloaded (because code unloading is not supported).
• The JVM allows any reference type to be passed where an interface reference is expected (and to store any reference type in an interface reference type field), on IKVM this results in an IncompatibleClassChangeError.
• monitorenter / monitorexit cannot be used on unitialized this reference.
• Floating point is not fully spec compliant.
• A method returning a boolean that returns an integer other than 0 or 1 behaves differently (this also applies to byte/char/short and for method parameters).
• Synchronized blocks are not async exception safe.
• Ghost arrays don't throw ArrayStoreException when you store an object that doesn't implement the ghost interface.
• Class loading is more eager than on the reference VM.
• Interface implementation methods are never really final (interface can be reimplemented by .NET subclasses).
• JSR-133 finalization spec change is not fully implemented. The JSR-133 changes dictate that an object should not be finalized unless the Object constructor has run successfully, but this isn't implemented.
• Strict class-file checking is not implemented.
• If a class with a finalizer and static initializer allocates instances of itself in the static initializer and the static initializer subsequently fails, the .NET runtime may abort the application when trying to finalize the objects.

Static Compiler (ikvmc)

7.1.4532.2

Original Release Notes: https://web.archive.org/web/20201129201033/http://weblog.ikvm.net/PermaLink.aspx?guid=c004201f-a226-4a98-8b12-904378e773d5. This release originally happened on SourceForge on 2012-07-16.

IKVM.NET 7.1 Released

I've released IKVM.NET 7.1 to SourceForge. The binaries are identical to the ones in release candidate 2.

Release Notes

This document lists the improvements, known issues and incompatibilities.

What's New (relative to IKVM.NET 7.0):

• Integrated OpenJDK 7 u4 b22.
• Dropped experimental partial trust support.
• Much improved ikvmc error and warning handling.
• Added ikvmc options: -win32manifest, -filealign, -highentropyva.
• Removed ikvmc -platform:Itanium option.
• Added ikvm.lang.DllExport annotation to export static methods as unmanaged entry points.
• Added ikvm.runtime.Util.getClassFromTypeHandle() overload for classes that represent arrays of remapped .NET types and .NET primitives.
• Added extension methods for (almost) all instance methods in Object, String and Throwable to ikvm.extensions.ExtensionMethods.
• Added support for delegates with ByRef parameters.
• Added support to ikvmc to automatically set the full source path in the debugging info if the source file lives next to the .class file.
• When adding certificates to virtual cacerts file make sure that the aliases that are generated from the certificate subject are unique.
• Many (minor) bug fixes.
• Many IKVM.Reflection fixes and improvements.

Runtime

• Code unloading (aka class GC) is not supported.
• In Java static initializers can deadlock, on .NET some threads can see uninitialized state in cases where deadlock would occur on the JVM.
• JNI
   
  • Only supported in the default AppDomain.
  • Only the JNICALL calling convention is supported! (On Windows, HotSpot appears to also support the cdecl calling convention).
  • Cannot call string contructors on already existing string instances
  • A few limitations in Invocation API support
     
    • The Invocation API is only supported when running on .NET.
    • JNI_CreateJavaVM: init options "-verbose[:class|:gc|:jni]", "vfprintf", "exit" and "abort" are not implemented. The JDK 1.1 version of JavaVMInitArgs isn't supported.
    • JNI_GetDefaultJavaVMInitArgs not implemented
    • JNI_GetCreatedJavaVMs only returns the JavaVM if the VM was started through JNI or a JNI call that retrieves the JavaVM has already occurred.
    • DestroyJVM is only partially implemented (it waits until there are no more non-daemon Java threads and then returns JNI_ERR).
    • DetachCurrentThread doesn't release monitors held by the thread.
  • Native libraries are never unloaded (because code unloading is not supported).
• The JVM allows any reference type to be passed where an interface reference is expected (and to store any reference type in an interface reference type field), on IKVM this results in an IncompatibleClassChangeError.
• monitorenter / monitorexit cannot be used on unitialized this reference.
• Floating point is not fully spec compliant.
• A method returning a boolean that returns an integer other than 0 or 1 behaves differently (this also applies to byte/char/short and for method parameters).
• Synchronized blocks are not async exception safe.
• Ghost arrays don't throw ArrayStoreException when you store an object that doesn't implement the ghost interface.
• Class loading is more eager than on the reference VM.
• Interface implementation methods are never really final (interface can be reimplemented by .NET subclasses).
• JSR-133 finalization spec change is not fully implemented. The JSR-133 changes dictate that an object should not be finalized unless the Object constructor has run successfully, but this isn't implemented.
• Strict class-file checking is not implemented.
• If a class with a finalizer and static initializer allocates instances of itself in the static initializer and the static initializer subsequently fails, the .NET runtime may abort the application when trying to finalize the objects.

Static Compiler (ikvmc)

• Some subtle differences with ikvmc compiled code for public members inherited from non-public base classes (so called "access stubs"). Because the access stub lives in a derived class, when accessing a member in a base class, the derived cctor will be run whereas java (and ikvm) only runs the base cctor.
• Try blocks around base class ctor invocation result in unverifiable code (no known compilers produce this type of code).
• Try/catch blocks before base class ctor invocation result in unverifiable code (this actually happens with the Eclipse compiler when you pass a class literal to the base class ctor and compile with -target 1.4).
• Only code compiled together during a single compilation fully obeys the JLS...

7.0.4335.0

Original Release Notes: https://web.archive.org/web/20201129195404/http://weblog.ikvm.net/PermaLink.aspx?guid=692505a6-f9e7-45ec-90b9-ec7a75d3b509. This release originally happened on SourceForge on 2011-12-05.

IKVM.NET 7.0 Released

I've released IKVM.NET 7.0 to SourceForge. The binaries are identical to the ones in release candidate 0.

Release Notes

This document lists the improvements, known issues and incompatibilities.

What's New (relative to IKVM.NET 0.46):

• Integrated OpenJDK 7 b147.
• Implemented Java 7 JVM changes.
• Java annotations on statically compiled code are now returned as java.lang.reflect.Proxy objects for compability with broken code that assumes this is always the case.
• Added delegate conversion for java.lang.reflect.InvocationHandler to ikvm.runtime.Delegates.
• Various remap file improvements.
• Changed build and JNI code to use different names for the Windows x86 and x64 versions of the native dll.
• Retain reflection field ordering for ikvmc compiled code (not required by spec, but to improve compatibility with broken code).
• Various AWT fixes.
• Interop between java.lang.AutoCloseable and System.IDisposable.
• Various build system improvements.
• Added ikvmc -warnaserror option.
• Fixed java.io.FileOutputStream in append mode to use atomic append.
• Various performance improvements.
• Added -Xnoglobbing option to ikvm.exe.
• Various minor fixes.
• Implemented dual stack sockets (Windows Vista and up only).
• Implemented platform MBean server.
• Implemented SocketChannel.sendOutOfBandData().
• Implemented DatagramChannel multicast methods.
• Removed mapping of System.Security.VerificationException to java.lang.VerifyError.
• IKVM.Reflection: Massive enhancements to support a very large portion of the managed PE capabilities (much more than System.Reflection.Emit).

Runtime

• Code unloading (aka class GC) is not supported.
• In Java static initializers can deadlock, on .NET some threads can see uninitialized state in cases where deadlock would occur on the JVM.
• JNI
   
  • Only supported in the default AppDomain.
  • Only the JNICALL calling convention is supported! (On Windows, HotSpot appears to also support the cdecl calling convention).
  • Cannot call string contructors on already existing string instances
  • A few limitations in Invocation API support
     
    • The Invocation API is only supported when running on .NET.
    • JNI_CreateJavaVM: init options "-verbose[:class|:gc|:jni]", "vfprintf", "exit" and "abort" are not implemented. The JDK 1.1 version of JavaVMInitArgs isn't supported.
    • JNI_GetDefaultJavaVMInitArgs not implemented
    • JNI_GetCreatedJavaVMs only returns the JavaVM if the VM was started through JNI or a JNI call that retrieves the JavaVM has already occurred.
    • DestroyJVM is only partially implemented (it waits until there are no more non-daemon Java threads and then returns JNI_ERR).
    • DetachCurrentThread doesn't release monitors held by the thread.
  • Native libraries are never unloaded (because code unloading is not supported).
• The JVM allows any reference type to be passed where an interface reference is expected (and to store any reference type in an interface reference type field), on IKVM this results in an IncompatibleClassChangeError.
• monitorenter / monitorexit cannot be used on unitialized this reference.
• Floating point is not fully spec compliant.
• A method returning a boolean that returns an integer other than 0 or 1 behaves differently (this also applies to byte/char/short and for method parameters).
• Synchronized blocks are not async exception safe.
• Ghost arrays don't throw ArrayStoreException when you store an object that doesn't implement the ghost interface.
• Class loading is more eager than on the reference VM.
• Interface implementation methods are never really final (interface can be reimplemented by .NET subclasses).
• JSR-133 finalization spec change is not fully implemented. The JSR-133 changes dictate that an object should not be finalized unless the Object constructor has run successfully, but this isn't implemented.
• Strict class-file checking is not implemented.

Static Compiler (ikvmc)

• Some subtle differences with ikvmc compiled code for public members inherited from non-public base classes (so called "access stubs"). Because the access stub lives in a derived class, when accessing a member in a base class, the derived cctor will be run whereas java (and ikvm) only runs the base cctor.
• Try blocks around base class ctor invocati...

0.46.0.1

Original Release Notes: http://weblog.ikvm.net/PermaLink.aspx?guid=94934445-9b06-4a81-b76b-fcd23d4f6ec2. This release originally happened on SourceForge on 2011-03-24.

IKVM.NET 0.46 Released

I've released IKVM.NET 0.46 to SourceForge. The binaries are identical to the ones in release candidate 1.

Release Notes

This document lists the improvements, known issues and incompatibilities.

What's New (relative to IKVM.NET 0.44):

• Integrated OpenJDK 6 b22.
• Added -Xreference: option to ikvm.exe and ikvm.runtime.Startup.addBootClassPathAssemby() API.
• The binaries zip now includes lib/ikvm-api.jar to avoid having to run ikvmstub to get access to the IKVM Java APIs.
• Ported parts of fdlibm to C# to use for StrictMath methods tan, cbrt, floor, pow, hypot, expm1 and log1p.
• Add support for serializing .NET exceptions in Java. We don't serialize the actual object, but a placeholder instead, to avoid having to implement full .NET serialization interop.
• Added IL optimization step to code generator.
• Added SynchronizationContext for AWT event thread.
• Many IKVM.Reflection improvements and bug fixes.
• Many Swing/AWT/font/graphics/printing improvements.
• Implemented IPv6 support (.NET only) for java.net package APIs.
• The sun.boot.class.path system property now points to VFS to allow javac to work (although a bit slow, because the stub class files are dynamically generated on demand).
• Resource and generated stub classes are now projected into the virtual IKVM home directory, to make code that assumes that resources live in jars happy.
• Improvements to @ikvm.lang.Internal handling.
• Many minor improvements.

Runtime

• Code unloading (aka class GC) is not supported.
• In Java static initializers can deadlock, on .NET some threads can see uninitialized state in cases where deadlock would occur on the JVM.
• JNI
   
  • Only supported in the default AppDomain.
  • Only the JNICALL calling convention is supported! (On Windows, HotSpot appears to also support the cdecl calling convention).
  • Cannot call string contructors on already existing string instances
  • A few limitations in Invocation API support
     
    • The Invocation API is only supported when running on .NET.
    • JNI_CreateJavaVM: init options "-verbose[:class|:gc|:jni]", "vfprintf", "exit" and "abort" are not implemented. The JDK 1.1 version of JavaVMInitArgs isn't supported.
    • JNI_GetDefaultJavaVMInitArgs not implemented
    • JNI_GetCreatedJavaVMs only returns the JavaVM if the VM was started through JNI or a JNI call that retrieves the JavaVM has already occurred.
    • DestroyJVM is only partially implemented (it waits until there are no more non-daemon Java threads and then returns JNI_ERR).
    • DetachCurrentThread doesn't release monitors held by the thread.
  • Native libraries are never unloaded (because code unloading is not supported).
• The JVM allows any reference type to be passed where an interface reference is expected (and to store any reference type in an interface reference type field), on IKVM this results in an IncompatibleClassChangeError.
• monitorenter / monitorexit cannot be used on unitialized this reference.
• Floating point is not fully spec compliant.
• A method returning a boolean that returns an integer other than 0 or 1 behaves differently (this also applies to byte/char/short and for method parameters).
• Synchronized blocks are not async exception safe.
• Ghost arrays don't throw ArrayStoreException when you store an object that doesn't implement the ghost interface.
• Class loading is more eager than on the reference VM.
• Interface implementation methods are never really final (interface can be reimplemented by .NET subclasses).
• JSR-133 finalization spec change is not fully implemented. The JSR-133 changes dictate that an object should not be finalized unless the Object constructor has run successfully, but this isn't implemented.

Static Compiler (ikvmc)

• Some subtle differences with ikvmc compiled code for public members inherited from non-public base classes (so called "access stubs"). Because the access stub lives in a derived class, when accessing a member in a base class, the derived cctor will be run whereas java (and ikvm) only runs the base cctor.
• Try blocks around base class ctor invocation result in unverifiable code (no known compilers produce this type of code).
• Try/catch blocks before base class ctor invocation result in unverifiable code (this actually happens with the Eclipse compiler when you pass a class literal to the b...