When attaching a custom CollectionTypeFactoryClass to a configuration object, that CollectionTypeFactory becomes used with all configuration objects. On the other hand, if one uses a default CollectionTypeFactoryClass first, and then tries to use another in a different configuration, one gets an 'collection factory in use - can't change it' exception.
This is evident from the test case.
Environment
None
Attachments
8
Activity
Alex Hummel
July 26, 2011 at 12:54 PM
Instead of Shared.uNhAddIns.WPF.Collections.WpfCollectionTypeFactory one can use just the uNhAddIns.WPF.Collections.WpfCollectionTypeFactory, it is the same.
Minor
Discussed in this thread: http://groups.google.com/group/nhusers/browse_thread/thread/80b78c62ebdbc2ed
When attaching a custom CollectionTypeFactoryClass to a configuration object, that CollectionTypeFactory becomes used with all configuration objects.
On the other hand, if one uses a default CollectionTypeFactoryClass first, and then tries to use another in a different configuration, one gets an 'collection factory in use - can't change it' exception.
This is evident from the test case.