Re: [Mono-dev] Patch for some obscure cases in Dictionary (small)
Hi Lionel,
I'm not sure whether the current implementation of Dictionary is
supposed to be binary compatible with .Net. Could you file a bug report
for case 2, along with a small test program that generates the .bin
file?
I'm not very familiar with the serialization features of .net, but I
think using SoapFormatter instead of BinaryFormatter will give you
results with much more information.
- Juraj
On Tue, 2008-06-17 at 18:49 +0200, Lionel Cuir wrote:
> Hello gentlemen,
>
> Since you're working on the Dictionary class, maybe you could help me
> debugging this.
> I have seen recent posts and patch to make the Dictionary more binary
> compatible between Mono and .Net (ie serialized data being compatible
> for serialization on one platform and deserialization on the other).
>
> I've done a couple of tests and what surprises me is that the binary
> form looks different in many cases but can still be deserialized by the
> other platform... in most cases only (see the example below).
>
> => What's the status for the Dictionary class. Are Mono and .Net
> officially binary compatible for the Dictionary or not yet?
>
> Examples:
> - Case 1: I have a Dictionary. Even if different, the
> binary serialized forms can be deserialized by the other platform (!).
> (see dico1_dotnet.bin and dico1_mono.bin).
> - Case 2: I have a Dictionary DateTime>> where Triplet is a simple triplet struct (see below) and
> ManagementState a basic enum.
> Here, neither Mono not .Net is able to deserialize a dico serialzed by
> the other (see dico2_dotnet.bin and dico2_mono.bin).
>
> Thanks for your advice!
> Lionel
>
> Here's the Triplet struct:
> [Serializable]
> public struct Triplet
> {
> TX _X;
> TY _Y;
> TZ _Z;
>
> public Triplet(TX x, TY y, TZ z)
> {
> this._X = x;
> this._Y = y;
> this._Z = z;
> }
>
> public TX X
> {
> [DebuggerStepThrough]
> get { return _X; }
> }
> public TY Y
> {
> [DebuggerStepThrough]
> get { return _Y; }
> }
> public TZ Z
> {
> [DebuggerStepThrough]
> get { return _Z; }
> }
> }
>
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [PATCH] Mono DTrace provider v3
Am 22.06.2008 um 19:58 schrieb Miguel de Icaza: >> Another thing to consider is whether to distribute the mono.d >> provider >> file for reference. Valgrind's mono.supp file is apparently being >> distributed, but that is more portable than DTrace I assume. > > Yes, it must be distributed. Please do that as well. Done, in r106413. If I understand correctly, "distributing" it is necessary for building from a tarball. Should we also install the file and, if yes, where to? To $prefix/etc/ mono like the other two files in data/? Or maybe to a new $prefix/lib/dtrace? (But how?) Andreas ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [PATCH] Mono DTrace provider v3
> Should we also install the file and, if yes, where to? To $prefix/etc/ > mono like the other two files in data/? > Or maybe to a new $prefix/lib/dtrace? (But how?) prefix/lib/dtrace Just use the standard automake process for it, there are samples in place in the mono/data directory. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] System.Deployment
Hi, I have a number of VB.NET programs from students that work fine under Win32, but fail when I try to build using MD. They are all calling System.Deployment which according to the docs is in mscorlib. I've added mscorlib to the references and removed System.Deployment (it's not available) and the code fails to build. What do I need to do to get a VB.NET app which calls System.Deployment to work? TTFN Paul -- Sie können mich aufreizen und wirklich heiß machen! signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] System.Deployment
The System.Deployment namespace is in the System.Deployment.dll Assembly, not in mscorlib. The docs (e.g. http://msdn.microsoft.com/en-us/library/system.deployment.application.applicationdeployment.aspx) state this, too. Greetings A.Nahr > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:mono-devel-list- > [EMAIL PROTECTED] Im Auftrag von Paul > Gesendet: Montag, 23. Juni 2008 23:56 > An: mono-devel > Betreff: [Mono-dev] System.Deployment > > Hi, > > I have a number of VB.NET programs from students that work fine under > Win32, but fail when I try to build using MD. They are all calling > System.Deployment which according to the docs is in mscorlib. > > I've added mscorlib to the references and removed System.Deployment > (it's not available) and the code fails to build. > > What do I need to do to get a VB.NET app which calls System.Deployment > to work? > > TTFN > > Paul > -- > Sie können mich aufreizen und wirklich heiß machen! ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
