onsdag 31 Oktober 2007 skrev Miguel de Icaza:
We are working on a schedule now, thanks for the feedback on the topics
you want discussed.
Hi Miguel.
For those of us that need to book flights, a rough outline of the _time_ would
be great, e.g. We start every day at 9, stop at 16, friday we
On 31/10/2007, Euan MacInnes [EMAIL PROTECTED] wrote:
This is also better for more lightweight environments and applications, i.e.
casual games and Windows CE devices which have download/space restrictions,
and I'd rather not get into custom forks of the mono build to cope with
those
Euan MacInnes wrote:
I would suggest that, rather than one version, Mono should split up
it's packages differently.
I have to agree. If we are talking about a on size fits all Mono
distribution, no version number can be too descriptive.
My guess is that numbering Mono as either 1.x or 2.x
Ernesto wrote:
Euan MacInnes wrote:
I would suggest that, rather than one version, Mono should split up
it's packages differently.
I have to agree. If we are talking about a on size fits all Mono
distribution, no version number can be too descriptive.
Exactly, so maybe we
Hi Miguel,
Am looking for ideas for topics that developers would be
interested
in hearing about at the Mono Summit.
I've been hanging on to this note while I tried to figure out if I could
swing the trip. As of this morning, I'm happy to say I'm coming!
My interests are around the
Arina,
Test case 44 in RegexResultTests is failing on MS (but passing on Mono). Can
you look into this?
Thanks,
Gert
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Arina Itkes
Sent: zondag 28 oktober 2007 19:28
To: mono-devel-list@lists.ximian.com
Subject:
Speaking completely selfishly, this would be great for me. We're
working on a cross-platform C# app and oddly, the hardest part of the
installation is ensuring that *Microsoft's* .net is installed
properly. If we could just bundle a micro-mono for Windows into our
distribution, we wouldn't
I think the only way to minimise confusion in the developer population
that does not keep up-to-date with the details of development on Mono
is to let at least the major version track full .NET compatibility.
That is, do not move to v2.x.x until at least .NET 2.0 can be fully
supported, do
Hello,
I tried out the tool and aside from some typical path issues, the app
ran great. Kudos to the WinForms developers! Is there any way to get
MoMA to do some Cecil magic and fix path issues? 2 Points for
evaluate, but you really get extra credit for remediate!
I guess we get the two
This week:
-Commited a patch for #335131
-Converted Mareks test into a regression test for #335131, creating it was
harder than I thought.
-Worked on #323747, got I patch sent to Paolo that fixes all soft-float
issues.
-Friday is celebration of death holiday
Next week:
-Fix more soft-float
Hi Miguel,
In the case of nunit, if you run say nunit-console that
will load the 1.0 runtime, and if that later tries to load an
assembly that was compiled with 2.0 it will load it, but it
will later fail when the assembly tries to reference 2.0 features.
FWIW, the next NUnit won't work
The current VMWear player is one of the greatest things Mono has to boost
exploration of Mono. I love it. In fact I love it so much, I want another!
What about a VMWear player setup with Mono source and SVN so one could just
fire it up, update the source from svn and start contributing?
12 matches
Mail list logo
