friism on 13 Mar, 2012 06:09 PM
You scenario would require overriding multiple connectionstrings
with different aliases and values. This is not currently supported.
Have you considered using the Entity Framework Membership
provider to unify your data model? If that's not an option, you
could specify the sequelizer connectionstring in a
Web.Release.config, but that's not recommended.