There are a couple of issue with sharing information. The first is where the
info is persisted. While I see no problem with personalization being used
across mutliple apps, as it is persisted in a DB, I do not know the exact
mechanics.
The second issue is session state. You can set up multiple web apps to use
the same session state, at least partially. By setting the machine keys to
the same on both servers (encrypt and decrypt - there are articles on this,
so google), you can share the session ID and the basic user info carried in
state (who are you? type of info). This does not mean you can set session
variables and have them transfer, however.
As for personalization , it is likely both have to act as the same app. I
would have to peek underneath the hood at the tables and mechanism to
confirm this, but I am fairly confident that it can be done by acting as if
the plethora of apps are a single app, as far as personalization and
membership go.
If not, you can create your own provider, as the feature set uses a provider
model to allow extensibility.
--
Gregory A. Beamer
*************** *************** *************** ****
Think Outside the Box!
*************** *************** *************** ****
"Tony Jones" <to*******@hotm ail.com> wrote in message
news:eO******** ******@TK2MSFTN GP03.phx.gbl...
Can I have two ASP.NET site using the same membership provider settings?
For this to happen, the applicationName would have to be the same, but
what about the configuration of the <properties> within the <profile>
section? In the web.config's for both sites, do these config sections have
to be identical? Could I actually fully define the <properties> section
in one application and not in the other?
Do the <profiles> section of each site have to be identical?
Any "gotchas" to watch out for?
The reason I have the sites seperate is because they will have a different
code base and I would like to manage them in that aspect.
Any experiences in doing this would be appreciated.
Thanks.
TJ
