[Mono-winforms-list] Still can't get winforms to work
Tue, 28 Sep 2004 10:42:43 -0700
Have you followed the instructions to build the managed windows forms
found here: http://www.mono-project.com/contributing/winforms.html ?
By default the old System.Windows.Forms.dll is built. You need to follow
those instructions to build the new System.Windows.Forms.
The 1.0/2.0 directory doesn't have anything to do with it.
On Tue, 2004-09-28 at 20:30 +0100, Paul wrote:
> > > Unhandled Exception: System.TypeInitializationException: An exception
> > > was thrown by the type initializer for System.Windows.Forms.Control --->
> > > System.TypeInitializationException: An exception was thrown by the type
> > > initializer for System.Windows.Forms.Win32 ---> System.
> > > DllNotFoundException: winelib.exe.so
> > This error is not in current CVS. Either you have not compiled and
> > installed current CVS mono OR you have two mono's installed. Try 'which
> > mono' and make sure it is the same as your --prefix when building.
> which mono shows /usr/bin/mono, which is correct as that's where I set
> it for the prefix.
> I originally thought I had not removed the original rpms, but I had. CVS
> was fresh built this afternoon.
> > > in <0x00050> (wrapper managed-to-native) System.Windows.Forms.Win32:
> > > WineLoadLibrary (string)
> > > <in 0x00390> System.Windows.Forms.Win32:.cctor ()
> > >
> > > Is it likely that I have something somewhere which is causing mono to
> > > bork when being called? I can't see anything in /usr/local/lib which
> > > would cause the problem.
> > What about in /usr/local is there a mono in there?
> No. I thought that was the problem.
> One thing I did notice when running strace was that mono was
> accessing /usr/lib/mono/1.0. When I looked, there was a 1.0 directory
> (with symlinks to gac/1.0) and a 2.0 directory. Is this correct?