Please fill a bug report with a test case and we'll work on it. Thanks, Rodrigo
On Thu, Dec 10, 2009 at 7:21 PM, Mad Fish <[email protected]> wrote: > > It behaves differently from the one in Microsoft .NET. > > When Mono loads several different assemblies that contains class, which is > named the same for all of them (fully-qualified name is the same: > Namespace.ClassName), it thinks that all these classes are equal. There is > no way to create instance of any class except the first one (from classes > with the same name). > > Am I right? > > However, Microsoft .NET allows that. This problem arised when porting > application from Microsoft .NET to Mono. That application used plugins. And > some plugins had similar class names, but in fact they were different. > > How can I solve this (or, maybe, workaround?) > -- > View this message in context: > http://old.nabble.com/System.Reflection.Assembly.Load-question-tp26713004p26713004.html > Sent from the Mono - General mailing list archive at Nabble.com. > > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list >
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
