Re: [Gtk-sharp-list] Tinymail DotNet bindings update
- From: "Mike Kestner" <mkestner gmail com>
- To: "Philip Van Hoof" <spam pvanhoof be>
- Cc: j <j bitron ch>, gtk-sharp-list lists ximian com, tinymail-devel-list <tinymail-devel-list gnome org>
- Subject: Re: [Gtk-sharp-list] Tinymail DotNet bindings update
- Date: Wed, 30 Jan 2008 10:56:47 -0600
On Jan 30, 2008 4:47 AM, Philip Van Hoof <spam pvanhoof be
Tinymail's -sharp install directory doesn't have these .config files
installed. I'm not really immediately finding what in the build of
gtk-sharp is installing them (I kept the Makefile.include identical for
that part of the build Makefile code afaik).
I'm guessing these config files are necessary for the .dll->.so mapping?
Something like that is what they seem to contain as XML data. Obviously
I mimicked them as good as possible using gtk-sharp's code.
gacutil installs .dll.config files if they are present. They support different dll/so/dylib naming conventions across various platforms. The convention is to use win32 dll naming in the DllImport statements in the generated code, so that assemblies work on the MS runtime on win32. We use dllmap entries in the .config file so that mono can map them to the appropriate nomenclature on *nix and mac.
Also, what is this policy.$(API_VERSION).config file for by the way?
Policy assemblies are the backward compatibility mechanism on .Net. A program built against assembly version 220.127.116.11
requires that specific assembly version be available at runtime. One way to satisfy that requirement is to install a policy.2.4 assembly which "links" to a newer assembly version that provides all of the API exposed by 18.104.22.168
] [Thread Prev