Class RedbSchemeNameConflictException
Thrown when two CLR types claim the same explicit scheme name. Both types are named in the
message — the whole point is that neither is more "correct" than the other, and the developer
has to pick.
Only conflicts involving an explicit Name are fatal. Alias collisions have always been
resolved last-write-wins and stay that way, so projects that predate explicit names are unaffected.
public class RedbSchemeNameConflictException : Exception, ISerializable