[Mono-dev] Using Mono.Options in MS.NET

[Petit Eric]

2008/10/17 Avery Pennarun <apenwarr at gmail.com>:
> On Thu, Oct 16, 2008 at 8:33 PM, Miguel de Icaza <miguel at novell.com> wrote:
>>> Now that Mono.Options is included in Mono 2.2, will it still be
>>> available separately?  If not, it will be hard to build
>>> Windows-compatible programs that use it, unless people go digging
>>> throug the mono sources and extracting the libraries they like.  I
>>> think it might be helpful to separate "mono libraries that add
>>> functionality to any .Net application" and "mono libraries that
>>> implement the MS class library" into two different projects.
>>>
>>> Am I missing something?
>>
>> You can always pull the code using the AnonSVN user interface from the
>> web, it can produce tarballs of just the things that you need.
>>
>> Our todo list includes "Make it easier to release components
>> independently", would love to do it, we just need the spare cycles to
>> make it happen in a general way for everything that we need.
>>
>> I think the tarball solution is pretty good, and we could just bundle
>> solutions or files for the more complicated modules (Mono.Options is
>> really easy to use).
I don't know if Mono.Option made P/Invoke, but if not you can simply
set , assembly property to "Locale copy" as it, the dll will folow the
.exe and so ...
>
> Thanks, that answers my question.
>
> Avery
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>



-- 

Cordially.

Small Eric Quotations of the days:
---------------------------------------------------------------------------
If one day one reproaches you that your work is not a work of
professional, say you that:
Amateurs built the arch of Noah, and professionals the Titanic.
---------------------------------------------------------------------------

Few people are done for independence, it is the privilege of the powerful ones.
---------------------------------------------------------------------------

No key was wounded during the drafting of this message.