[Gtk-sharp-list] Deploying on WIN32 - manifest mismatch

[John D. Hardin]

All:

I'm trying to understand what all is involved in developing GTK# apps
under Linux and deploying them on Windows .NET 1.1 - progress is being
made but it's slow...

I am now stuck on this error:


Unhandled Exception: System.IO.FileLoadException: The located
assembly's manifest definition with name 'gtk-sharp' does not match
the assembly reference.
File name: "gtk-sharp"
   at PrimesUI.PrimesUI.Main()
 
=== Pre-bind state information ===
LOG: DisplayName = gtk-sharp, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=35e10195dab3c99f
 (Fully-specified)
LOG: Appbase = D:\TEMP\c#\
LOG: Initial PrivatePath = NULL
Calling assembly : primes_ui_gtk, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=null.
===
 
LOG: Found application configuration file
(D:\TEMP\c#\primes_ui_gtk.exe.config).
LOG: Publisher policy file is not found.
LOG: Host configuration file not found.
LOG: Using machine configuration file from
C:\WINNT\Microsoft.NET\Framework\v1.1.4322\config\machine.config.
LOG: Post-policy reference: gtk-sharp, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=35e10195dab3c99f


What exactly does that mean? That my WIN32 GTK# package (from
gtk-sharp-0.93-setup.exe) does not match the GTK# package on Linux
that the app was compiled against? That the WIN32 GTK# package does
not match the WIN32 gtk+ .DLLs?

I notice that the public key on gtk-sharp.dll in the Windows GAC is
different from the public key given above, but there's no mention of
a key mismatch in the error message.

--
 John Hardin KA7OHZ    ICQ#15735746    http://www.impsec.org/~jhardin/
 jhardin@impsec.org    FALaholic #11174    pgpk -a jhardin@impsec.org
 key: 0xB8732E79 - 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
  The [assault weapons] ban is the moral equivalent of banning red
  cars because they look too fast.
                                   -- Steve Chapman, Chicago Tribune
-----------------------------------------------------------------------
   67 days until the "Scary-Looking Guns" ban expires