Re: [Ikvm-developers] Problem with using IKVM-generated DLLs in Visual Basic

[Thomas T. <tho...@gm...>]

Hi Jeroen,

Thanks a lot for your prompt reply!

I downloaded IKVM 7.2.4630.5 and performed the described operations in its
bin directory. When I type ikvm, the program responds with IKVM.NET
Launcher version 7.2.4630.5.

So I'm wondering why is the IKVM.GNU.Classpath.dll generated (if it's
obsolete now, as you say) and why would Visual Studio reference the ancient
IKVM version (and not 7.2)?

Thomas

On Wed, Jul 1, 2015 at 10:01 AM, Jeroen Frijters <je...@su...> wrote:

> Hi Thomas,
>
> The key is in the error:
> > Error 1 Unknown build error, 'Cannot resolve dependency to assembly
> > 'IKVM.Runtime, Version=0.30.0.0, Culture=neutral,
>
> This is a truly ancient IKVM version (0.30). So somehow you are mixing
> some things together that don't go together well.
>
> Also, you mention IKVM.GNU.Classpath.dll, this is also obsolete and not
> part of IKMV 7.2.
>
> Regards,
> Jeroen
>
> > -----Original Message-----
> > From: Thomas Templin [mailto:tho...@gm...]
> > Sent: Wednesday, July 1, 2015 15:17
> > To: ikv...@li...
> > Subject: [Ikvm-developers] Problem with using IKVM-generated DLLs in
> > Visual Basic
> >
> > Dear Mailing-list Subscribers,
> >
> > I have a simple Java program the methods of which I'd like to be able to
> > use in a WPF Application Visual Basic project.
> >
> > I'm using Windows 7 Professional, 64-bit. I compiled the .java file in
> > the Command Prompt using jdk1.7.0_79. Then, using ikvm-7.2.4630.5, I
> > typed the following command in IKVM's bin directory:
> >
> > ikvmc - target:library hexcksum.class
> > ("hexcksum" is the name of the Java program).
> >
> > As expected IKVM produced the files kexcksum.dll and
> > IKVM.GNU.Classpath.dll. However, when I add these two DLLs as references
> > to Visual Studio 2013, I receive the following error:
> >
> > Error 1 Unknown build error, 'Cannot resolve dependency to assembly
> > 'IKVM.Runtime, Version=0.30.0.0, Culture=neutral,
> > PublicKeyToken=13235d27fcbfff58' because it has not been preloaded. When
> > using the ReflectionOnly APIs, dependent assemblies must be pre-loaded
> > or loaded on demand through the ReflectionOnlyAssemblyResolve event.'
> > plus a bunch of other errors.
> >
> > I've been trying to google a solution for this problem, but have not
> > been able to solve it.
> >
> > I was wondering if anybody is able to help me with this problem. I'm
> > happy to provide more information, if necessary.
> >
> > Thanks,
> >
> > Thomas
> >
> >
> >
>
>