On Mon, 2005-05-09 at 09:07 +0100, Dick Porter wrote:
> > + accept_thread = Thread.CurrentThread;
> > + try {
> > + sock = Accept_internal(socket, out error);
> > + } catch (ThreadAbortException the) {
> > +
Hi,
> Since many people as well as me feel that MiniParser is difficult
> to fix, I created another small xml parser for corlib. I attached
> the patch for corlib (mostly for SecurityParser and
> RemotingConfiguration). It should fix bug #74203 (and #74799), and
> will fill the n
Hello,
> 2. Lots of existing code don't care about the framework version. In that
> case it's easier to use code that will work on both versions, like:
>
> using System;
>
> class Program {
>
> static void Main ()
> {
> int p = (int) Environment.OSVersion.Platform;
>
Hi Everybody,
When using ApplicationHost.CreateApplicationHost, are the values set using
AppDomain.SetData the same as on MS.NET?
Also, is it possible to host ASP.NET in the same appdomain as the main entry
point procedure is ran?
Greets,
Matthijs
BEGIN:VCARD
VERSION:2.1
N:ter Woord;Matthijs
> I was wondering whether there is any effort or interest in porting
> mono to the Itanium2 architecture?
Yes. We are getting the hardware now.
> I would also be interested to hear from people who ported mono to the
> opteron, how much work was involved, how effective if mono on 64 bit
> archit
Hi, Atsushi.
This is what I've got so far. It's not ready for commit, but you can
start playing with it. Here is the list of testids that regressed. May
be a part of them pass on mono - then it must be a bug in our mscorlib.
Thank you
Andrew Skiba.
FormatNumber_FormatNumberWithPattern.00
FormatN
Hello,
The original frameworks (both 1.0 and 1.1) didn't have a value to
identity Unix (and Unix-like) operating systems. Mono has been using the
value 128 up to now to identity them.
The framework v2.0 introduce a new Unix enum value (4) in PlatformID,
but this isn't compatible with the existing
Ok. Things are looking better and I am now a few steps from monodevelop 0.6
However :(, I got this last sniggly problem on the monodevelop compile.
# make
./src/SharpAssembly/AssemblyReader.cs(177) error CS0104: `MethodBody'
is an ambiguous reference (System.Reflection.MethodBody or
MonoDevelop.Sh
Hi
This attached patch corrects the following problem.
byte[] bytes = System.Web.HttpUtility.UrlDecodeToBytes ("%5c");
Console.WriteLine (bytes[0].ToString ("x2"));
Actual Results: 05
Expected Results: 5c
Please review it.
Best regards.
Kazuki OikawaI
Ok. Things are looking better and I am not a few steps from monodevelop 0.6
However :(, I got this last sniggly problem on the monodevelop compile.
# make
./src/SharpAssembly/AssemblyReader.cs(177) error CS0104: `MethodBody'
is an ambiguous reference (System.Reflection.MethodBody or
MonoDevelop.Sh
Hi,
mint does not work on ia64.
Zoltan
On 5/9/05, Pierre Brunet <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've downloaded the 1.1.7 version of Mono. I've installed it on a
> redhat without any pbs, but
Hi,
Since many people as well as me feel that MiniParser is difficult
to fix, I created another small xml parser for corlib. I attached
the patch for corlib (mostly for SecurityParser and
RemotingConfiguration). It should fix bug #74203 (and #74799), and
will fill the need shown
Hi,
I've downloaded the 1.1.7 version of Mono. I've installed it on a
redhat without any pbs, but when I search for mint in "MonoDir/bin"...
there nothing.
I tried to compile it "manually" by launching "make mint" in
"mono-1.1.7/mono/interpreter" directory but il fails :
interp
On Sat, 2005-05-07 at 02:22 -0400, Gonzalo Paniagua wrote:
> Modified:
>trunk/mcs/class/System/System.Net.Sockets/ChangeLog
>trunk/mcs/class/System/System.Net.Sockets/Socket.cs
> Log:
> 2005-05-07 Gonzalo Paniagua Javier <[EMAIL PROTECTED]>
>
> * Socket.cs: see bug #74842, which is f
14 matches
Mail list logo
