Gert, thanks for a great copyright infringement. It'd be even nicer
if you didn't omit the entire first mail that you sent me.
For my private favor (such as Yes, I prefer POX much over SOAP and
Yes I'm not a fan of already-failed compatiblity by Microsoft itself),
I'll reply to you privately.
-Original Message-
From: Atsushi Eno [mailto:[EMAIL PROTECTED]
Sent: woensdag 8 februari 2006 10:55
To: Gert Driesen
Cc: 'mono-devel mailing list'
Subject: Re: [Mono-dev] RE: FW: [PATCH] Enum XML
(de)serialization fixes
Gert, thanks for a great copyright infringement.
How could you read my message like publicate my private favor
in the mailing list ? What I said to you was please post
patch-related stuff to public mailing list, not me.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Atsushi Eno
Sent: woensdag 8 februari 2006 11:31
To: Gert Driesen
Cc: 'mono-devel mailing list'
Subject: Re: [Mono-dev] RE: FW: [PATCH] Enum XML
(de)serialization fixes
How could you read my
I did send all patches to the mailing list. All I asked (privately) was if
you could take a look at it.
Again, I'll copy my email in, so please tell me what is S wrong with
this (that it justifies this lengthy discussion):
As the message I sent to Gert tells, the comment on this matter was
Hi,
I think that at this point we should stop discussing this issue and
spend our time in more productive work.
First of all, the correct place for reporting bugs and providing patches
for those bugs is bugzilla. If the patch is big, splitting it will ease
the work of the reviewer (that is,
-Original Message-
From: Lluis Sanchez [mailto:[EMAIL PROTECTED]
Sent: woensdag 8 februari 2006 12:50
To: Gert Driesen
Cc: 'Atsushi Eno'; 'mono-devel mailing list'
Subject: RE: [Mono-dev] RE: FW: [PATCH] Enum XML
(de)serialization fixes
Hi,
I think that at this point we
Many many guys had experienced it ;-) (it is not only about
Windows build). For those who are not aware of what the build
(make) does, just try make clean under mono.
For those who know a bit more, it would go away if you cleanup
System.dll and System.Configuration.dll both in 2.0.
In general,
There is a problem with the implementation of this
library.
Mono implementation of DirectoryServices uses a
library provided by Novell (C# LDAP Library).
Getting the objectSID of a user or a group, I've
seen that the Microsoft Framework library (DirectoryServices.dll) returns the
SID as
Brian Crowell wrote:
When linking a file in the /mono/metadata directory, the following error
occurs:
More info:
Near as I can tell, libmonoos.a is being built without any sources. It's empty.
It should have the source from the /unix subdirectory. What controls this?
This occurs on both
Brian Crowell wrote:
When linking a file in the /mono/metadata directory, the following error
occurs:
It's not so much that libmonoos.a is empty-- it's that there's two of them, and
the wrong one is empty.
mono/os/.libs/libmonoos.a is empty, but mono/os/unix/.libs/libmonoos.a has the
right
When compiling the attached file, I get the following compilation
error (using mono 1.1.13):
error CS0277: Accessor `ProtectedSetter.DerivedClass.Name.set' must be
declared public to implement interface member
`ProtectedSetter.BaseClass.Name.set'
Is this a bug in the Mono compiler?
Thanks,
I'm working on a database application that uses Crystal reports. I took all
the CR managed DLL's and added them to the cache on my Linux install of mono.
I ran the app, which did start up, and displayed the report control But when
I tried to invoke the report, I got a nasty crash:
[EMAIL
Joshua,
I'm fairly certain that Crystal Reports will not run on linux, as the managed
DLL's are mostly just wrappers around CR's win32 and COM api's.
This most likely includes both the front end GUI and back end to generate the
reports themselves.
Hence is why we are now using iTextSharp
(
I notice that there is already a UnixDriveInfo. I'm implementing a
System.IO.DriveInfo that currently just reflects on UnixDriveInfo.
I've noticed some issues though.
UnixDriveInfo currently doesn't do any DriveType detection -- is there a
reliable POSIX way of detecting the type of a disk
Could somebody check this out and evaluate the importance of the
underlying issue?
http://bugzilla.ximian.com/show_bug.cgi?id=77446
--
Lev
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
16 matches
Mail list logo
