Hi,
Thanks for the response but this does not solve my issue...
On Tue, Mar 2, 2010 at 4:12 PM, Jonathan Pryor jonpr...@vt.edu wrote:
On Tue, 2010-03-02 at 12:21 -0500, Jacques Beaurain wrote:
... The issue that we face is
that this assembly is not signed and we need to be able to place the
Hi,
On 03.03.2010 11:44, Jacques Beaurain wrote:
YOU have sources and a compiler toolchain. If you need a strong-named
assembly, fold it into your own assemblies and strong name *those*, so
that responsibility for maintaining API compatibility is clear.
This is exactly the issue, the
For starters some background info:
http://www.mono-project.com/I18nGettext -- Show how to use GetText# which
exposes an Gnu.GetText namespace and thus presumably should package such a
Gnu.GetText.dll as discussed in this thread.
Perusing the released sources of gettext (gettext-0.17.tar.gz),
Hi,
Thanks for all the replies. Signing the assembly and making the
private/public key available was one option we were considering, but I
think the final and easiest solution is writing our own assembly with
native interop to libintl.
Interestingly the gettext documentation does not state the
On Wed, 2010-03-03 at 10:16 -0500, Jacques Beaurain wrote:
I think the final and easiest solution is writing our own assembly with
native interop to libintl.
We already have such a thing: Mono.Unix.Catalog, in Mono.Posix.dll,
which is MIT/X11 licensed (no LGPL worries) and is already
Hi All,
We are looking at using one of the assemblies from the Mono release
under the terms of the LGPL license in a commercial closed source
application. My understanding is that this is allowed as long as we do
not modify the compiled assembly in any way. The issue that we face is
that this
On Tue, 2010-03-02 at 12:21 -0500, Jacques Beaurain wrote:
... The issue that we face is
that this assembly is not signed and we need to be able to place the
assembly in the GAC of Microsoft Windows systems. What is the
recommended way to handle this situation?
In particular we are
