using Membership on production server (Copy Web Site tool)

[Louis R.]

Hi!

I read a lot about that and I still cannot figure it out. So. I'd like to
use membership into an web application that will run on a production
server(s). On my dev machine, using Web dev Xpress 2008 and SQL Server
Xpress 2008, all is well. My Aspnetdb.mdf is running fine in my App_data
directory.

When I use the copy website utility to transfer all this on a "test"
production server and try to login or anything, I'm getting the predictable
"Failed to generate a user instance of SQL Server due to a failure in
starting the process for the user instance."

Now, my "test" prod server runs .NET 3.5, IIS 6, SQL server 2000 (Std
Edition) and SQL server Xpress 2008. I could install SQL 2008 Standard if
necessary but for now we were delaying this. I could do the same on real
prod servers when ready.

I have many questions :

1) What do I need to have and to configure on my prod server to use
Membership with Aspnetdb.mdf in a App_data directory ?

2) Is it possible to use many concurrent secure Web app on a production
server, using separate membership structure based on separate Aspnetdb.mdf in
each App_data directory of each app?

3) Do I have to use SSL connection to keep secure "Username /Password" use
during login ?

4) Is it a good rule to use the App_data for other application databases
(Inventory, parts catalog, orders and financial data, ...) and how to connect
safely their use with the Role/membership structure ?

4) Is it possible/suitable to have a "mixed model", using Windows
Authentification to get in the app zone, login in (to identify more precisely
the user) afterward ? And why is it or is not a good way to go ...

Thanks anyway and have a good day !

 

[Norman Yuan]

Do not focus your thought on asonetdb.mdf, the database file. Your
application/website code DO NOT deal directly with that file, deal with SQL
Server/Express instead. You need a bit more knowledge on SQL Server.

Search SQL Server Book Inline for User Instance. "User Instance" is
complicated concept and unfortunately is used by many books' code as default
without much explanation. There is few reason to use USER INSTANCE in a web
application, not to mention it is only supported by SQL Server Express
edition. That means, your production host with SQL Server Std does not have
USER INSTANCE.

So, first stop use user instance on your developing box, unless you know
what it is and you have good reason to use it. Then learn how to transfter
SQL Server database (ASPNETDB in your case) to another SQL Server (the
production one).

The SQL Server membership provider you used in your app comes with .NET2.0
and ready to use, assume you have good understanding of SQL Server. You can
choose not to use it abd roll out your own, so that you do not have to deal
with SQL Server/ASPNETDB

 

[sloan]

Check this:
http://sholliday.spaces.live.com/blog/cns!A68482B9628A842A!160.entry


And this:
http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx

 

[Louis R.]

I do not want to use USER INSTANCE, I knew this. With Membership/Role, I do
not see how it could work anyway.

I know I do not have to use aspnetdb but I would like to (the structure
suits my goals). So I have to configure my prod SQL Server to offer the
membership provider to my web app, but how ? What do I have to do on my SQL
server? What in my WebConfig? Is there a straighforward and reliable way to
implement that ? Can I have many web app with each its own membership
provider using different aspnetdb.mdf it their own web app directory?

I still don't know how much my login process will be secure with that model
: do I absolutely need SSL connection to protect Username/Password ? Can I
use certificates, CardSpace, LiveID along with a Membership Provider ?