[Gtk-sharp-list] Gtk# 0.10 installer for Windows (aka. Gtk# Runtimeand Development Environment for Windows)

Timothy Parez Timothy Parez" <timothyparez@linux.be
Thu, 26 Jun 2003 20:28:43 +0200


Hi,

I've also been thinking about this problem

>Gtk# assemblies are now strongly named, compiled with ngen and copied to
>the assembly cache during installation. This solves the first part of
>the long known ".NET-Framework-cannot-find-Gtk#" problem. Second part of
>the well known problem is gtksharpglue.dll not being found. Best
>solution for this so far: Manually tweaking the PATH environment
>variable. The Gtk# Runtime and Development Environment introduces a more
>elegant solution:

How did you solve that ? Because I tested a few things and I came to the
following conclusion
Lets say assembly X is an open-source assembly, your installer installs
assembly X into the GAC

Then I recompile assembly X from cvs (which is then unsigned) and compile my
application Y against assembly X
In my experience my application Y will never run against the version of
assembly X which is located in the GAC
because my application doesn't expect a signed assembly X (strong named)

As long as people compile against the strong named assemblies in the GAC
(from your installer) their application will work
fine, but if they compile against GTK# on mono it may not always work as
expected.

Unless I'm missing something, which I think is the case,
could you give me some more information.

Btw, I'm sure many people (including me) are very happy with your installer
:)

Tim.


----- Original Message -----
From: "Mathias Hasselmann" <mathias.hasselmann@gmx.de>
To: <gtk-sharp-list@lists.ximian.com>
Sent: Thursday, June 26, 2003 4:12 PM
Subject: [Gtk-sharp-list] Gtk# 0.10 installer for Windows (aka. Gtk#
Runtimeand Development Environment for Windows)


> Hi,
>
> Still wondering for not raising any reaction with my previous posting
> I'm proud the present the second edition of my Gtk# Installer for
> Windows.
>
> Gtk# assemblies are now strongly named, compiled with ngen and copied to
> the assembly cache during installation. This solves the first part of
> the long known ".NET-Framework-cannot-find-Gtk#" problem. Second part of
> the well known problem is gtksharpglue.dll not being found. Best
> solution for this so far: Manually tweaking the PATH environment
> variable. The Gtk# Runtime and Development Environment introduces a more
> elegant solution:
>
> public static void Main()
> {
> GtkSharpRuntimeEnvironment.Init();
> Gtk.Application.Init();
> ...
>
> Well. What does this magic GtkSharpRuntimeEnvironment.Init? It checks
> the current platform. If Windows is identified the registry is scaned in
> order to find the Gtk+ and the Gtk# Runtime Environment. When they are
> found the application's PATH is adjusted. When not an exception verbosly
> explaining the problem is thrown. Feel free to show it your user. Of
> course you'll have to link against the GtkSharpRuntimeEnvironment
> assembly if you wish to use this magic function.
>
> So with this package deployment of Gtk# based applications on Windows
> should have become quite trivial: You just ask your users to install the
> .NET Framework, the Gtk+ Runtime Environment
> (http://www.dropline.net/gtk/) and my Gtk# Runtime Environment
> (http://taschenorakel.de/mathias/archive.en.html#gtk-sharp *)). Once
> those packages have found their way on the user's computer, Gtk# based
> applications can be copied arround and renamed as randomly as the user
> wishes.
>
> Ciao,
> Mathias (aka tbf)
>
> *) Hopefully it is possible to move the package to
> http://gtk-sharp.sourceforge.net/ soon?
>
>
> _______________________________________________
> Gtk-sharp-list maillist  -  Gtk-sharp-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/gtk-sharp-list


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.491 / Virus Database: 290 - Release Date: 18/06/2003