Hey all, Silverlight 2.0b2 contains three assemblies that we do not provide yet:
* System.ComponentModel * System.ComponentModel.Web * System.Runtime.Serialization Currently, we have parts of those assemblies implemented in the olive module. We could either: 1) depend on olive, and tune the assemblies there. 2) move those assemblies to the mcs module, and tune them there. According to the discussion we had on IRC, it seems that 1) is a no go, as we don't want to release olive, and we rather avoid to add another dependency to moon. How to do 2) properly then? Should we simply move those assemblies to mcs, and develop there, or continue to develop in olive, and merge changes when we feel confident into mcs? I'd rather simply move them, but then we would have unstable assemblies in mcs. Should we apply the same policy we apply for Cecil, that is not exposing it to the compiler without using a pkg? Also, Atsushi, how complete is our implementation wrt what SL2 ships? -- Jb Evain <[EMAIL PROTECTED]> _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
