Issue 8 in appleseedapp: Multi DB Support

[apples...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 8 by DVDobrov...@gmail.com: Multi DB Support
http://code.google.com/p/appleseedapp/issues/detail?id=8

I`am new to mvc - still learning howto

As far as I understand user and roles now handled
not by rainbow but by mvc (aspnet_user and so on).

So there is new things appeard - membership, roleManager, profile, siteMap,
caching

All use direct pre-defined Connectstring name in web.config
and this means multidbsuport no longer working
(but exist as a parameter in web.config)

multidb means there is multi connectionstring in web.config
with pattern [portalalias]_Connectionstring

So are you going to continue with multidb support or not?

[apples...@googlecode.com]

Updates:
Status: Invalid

Comment #1 on issue 8 by rams...@gmail.com: Multi DB Support
http://code.google.com/p/appleseedapp/issues/detail?id=8

The current user system in Appleseed is the same that was created for
Rainbow 2.0.

The only difference is that we have bug tested it heavily and fined tuned
it for the portal. ASPNETDB Membership is fully supported.

Multiportal works as it did under Rainbow. You define urls in the
web.config with portal alias and the portal can host multiple portals under
one installation.

Please continue these conversations on our support forum :

http://appleseedapp.com/support/

[apples...@googlecode.com]

Comment #2 on issue 8 by dmitriy....@cetschool.com: Multi DB Support
http://code.google.com/p/appleseedapp/issues/detail?id=8

It doesnot

this section of membership provider
// Initialize SqlConnection.
//ConnectionStringSettings ConnectionStringSettings =
ConfigurationManager.ConnectionStrings[config["connectionStringName"]];

config["connectionStringName"] - this is a connect string names from
web.config
ex

<membership defaultProvider="AppleseedMembershipProvider">
<providers>
<clear />
<add name="AppleseedMembershipProvider"
type="Appleseed.Framework.Providers.AppleseedMembershipProvider.AppleseedSqlMembershipProvider,
Appleseed.Framework.Providers.AppleseedSqlMembershipProvider"
connectionStringName="ConnectionString" applicationName="Appleseed"
enablePasswordRetrieval="true" enablePasswordReset="true"
requiresQuestionAndAnswer="false" requiresUniqueEmail="true"
passwordFormat="Clear" maxInvalidPasswordAttempts="5"
minRequiredPasswordLength="5" minRequiredNonalphanumericCharacters="0"
passwordAttemptWindow="10" passwordStrengthRegularExpression="" />
</providers>
</membership>

so code take "ConnectString" as a connectstring name
not "portalalias_ConnectString"

works then I change it in allprovider to

// Initialize SqlConnection.
//ConnectionStringSettings ConnectionStringSettings =
ConfigurationManager.ConnectionStrings[config["connectionStringName"]];

//if (ConnectionStringSettings == null ||
ConnectionStringSettings.ConnectionString.Trim().Equals(string.Empty))
if (Config.ConnectionString.Trim().Equals(string.Empty))
{
throw new AppleseedMembershipProviderException("Connection
string cannot be blank.");
}

connectionString = Config.ConnectionString;
// !!!!!!!!!!!!!!!!!!

[apples...@googlecode.com]

Comment #3 on issue 8 by rams...@gmail.com: Multi DB Support
http://code.google.com/p/appleseedapp/issues/detail?id=8

Like I said before. Please carry this conversation to the forums where we
can better assist you.

This issue tracker is for bugs only. It seems you are talking about
connection strings with ASPNETMEBERSHIP which IS Supported and NOT a bug.

Perhaps this forum : http://appleseedapp.com/support/#/categories/migrating

[apples...@googlecode.com]

Comment #4 on issue 8 by dmitriy....@cetschool.com: Multi DB Support
http://code.google.com/p/appleseedapp/issues/detail?id=8

I think this is a bug that is why i write here

[apples...@googlecode.com]

Comment #5 on issue 8 by rams...@gmail.com: Multi DB Support
http://code.google.com/p/appleseedapp/issues/detail?id=8

Please state the ways to produce the bug or the issue.

The name Multidb support doesnt give enough info to solve your issue.

It sounds to me that you are trying to do multiple databases with 1
installation. We only support 1 DB with multiple portals. As I see from
your code, yes you easily can do what you are asking . This not a bug but
a feature.

For now, We are simply supporting 1 Database with 1 to unlimited portals.
In the future yes we could do some kind of multidb option but for now that
is overkill.