I don't understand...do you mean: <typeAlias alias="Book" assembly="DomainTwo.Book, DomainTwo" />
or: <typeAlias alias="Book" type="DomainTwo.Book" assembly="DomainTwo" /> The first example isn't very .NET-ish. When .NET people talk about dynamically loading a Type, they talk about it in terms of its "fully qualified type name"...that's the attribute is named "type" and not "assembly". The second example is too verbose. The Type.GetType(string) method understands the namespace-dot-class-comma-space-assembly notation. --- Clinton Begin <[EMAIL PROTECTED]> wrote: > Ah ha! I see. I was looking for something like that. > > Just out of curiosity, why not just have an assembly="" attribute on > the > <typeAlias> element? > > Cheers, > Clinton > > On 7/16/06, Gilles Bayon <[EMAIL PROTECTED]> wrote: > > > > > > Just to to clarify, > > > > > > <alias> > > <typeAlias alias="Document" type="DomainOne.Document, DomainOne" > /> > > <typeAlias alias="Book" type="DomainTow.Book, DomainTow" /> > > </alias> > > > > Where DomainOne and DomainTow are 2 projects which compile in > DomainOne.dll > > and DomainTow .dll > > > > Is it OK ? > > > > > > >
