[Gtk-sharp-list] Integrating GTK# classes/namespaces into
MS Visual Studio .NET
richard_staff@bankone.com
richard_staff@bankone.com
Wed, 21 Apr 2004 16:27:28 -0400
Somehow list address got scrambled. List only resend.
----- Forwarded by Richard Staff/MI/ONE on 04/21/2004 04:25 PM -----
Richard Staff
To: gtk-sharp-list@listsatximian.com
04/21/2004 cc: steve@citygroup.ca
04:23 PM Subject: Re: [Gtk-sharp-list] Integrating GTK# classes/namespaces
into MS Visual Studio .NET(Document link: Richard Staff)
libgtk-win32-2.0-0.dll is calling libiconv_set_relocation_prefix, which is
supposed to reside inside iconv.dll.
libgtk-win32-2.0-0.dll appears to be calling a lot of things during startup
that support GtkButton.exe.
There were a lot of not found DLL's that I was able to track down and fix,
but this iconv.dll appears to be missing a method that
libgtk-win32-2.0-0.dll wants to use. Oh well.
Rick
P.S. What are #mono or #monodevelop?
= = = = = = = = = = = = = = = = = = = = =
"Steve
Deobald" To: richard_staff@bankone.com
<steve@citygro cc: gtk-sharp-list@listsatximian.com, steve@citygroup.ca
up.ca> Subject: Re: [Gtk-sharp-list] Integrating GTK# classes/namespaces
into MS Visual Studio .NET
04/20/2004
10:45 PM
Please respond
to steve
richard_staff@bankone.com said:
> P.S. I tried using the mono GTK# iconv.dll as an assembly reference, MS
> Visual Studio .NET protested that iconv.dll was not a valid assembly.
I had a similar problem with (if I remember correctly) gdl-sharp.dll. I'm
not at my XP box at the moment, so I can't look to see how I resolved
that, but I'll get back to you.
What is it that requires iconv.dll? The file doesn't ring any bells for me
- is it required for the code snippet you sent earlier?
.steve
PS: If you hang around #mono or #monodevelop after midnight CST, I can try
to help you out with vs.net handy.
This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.