Re: Help with ASP.NET Memberships

Dear Jonathan

The ASPNETDB database that is created can support multiple
applications. It has been designed to act as a common resource. One of
the fields in the tables is "Application ID"

It is not true that only Windows and Passport modes of authentication
are supported. It does indeed support Forms mode, in fact there are
special web controls for it e.g. the Login control which is available
in the toolbox of the VS2005 designer.

If you want to integrate the membership database with your application
database then the easiest way is to add your own tables etc to the
ASPNETDB database. The latter can be renamed to something else but you
will need to ammend the web.config file accordingly.

I'm afraid it's all too complicated to deal with here, I suggest you
study it further and give yourself a chance to absorb it all before
trying to implement it in an actual project. There are a lot of other
issues that need to be addressed, not the least is whether you can use
the default mode of access via so called "User instances" where
the .mdb file is attached "on the fly" to the SQL server, or whether
you set it up as a permanently attached database (SQL 2005 Express
edition will support it).

Having said that it's a great tool for controlling who can do what and
the various views that different users can have of the site and its
resources. It's well worth persevering with.

HTH



On 15 Oct, 20:37, "Jonathan Wood" <jw...@xxxxxxxxxxxxxxxx> wrote:
I'm taking my first stab at using ASP.NET memberships and could use some
help.

I'm following along in a book, which recommends I use the Web Application
Administration Tool in VS 2005.

A couple of problems:

1. The only choices it gives me for the authentication method are Windows
and Passport. Based on what I read, forms is what I need. Can anyone tell me
why this option isn't available?

2. I see it generated a complete, new database to store the membership
information in. That's okay I guess but doesn't it have the option of
storing those tables in my main database? Is it the standard to create a
separate database? Most of the data I need to store will be associated with
the users and so I assume I'd want to combine database and be able to extend
the user information that ASP.NET created. Am I off-track here?

Thanks for any help.

--
Jonathan Wood
SoftCircuits Programminghttp://www.softcircuits.com


.

Relevant Pages

  • Re: What so special about PostgreSQL and other RDBMS?
    ... That's exactly the link the licence agreement for the database points to when it ... comes to what wecan expect for paying support. ... > "Oracle may provide additional releases or versions of its programs ... If the requirements are volatile I'd do a long term contract detailing what ...
    (comp.lang.php)
  • Re: What so special about PostgreSQL and other RDBMS?
    ... > the porting to another database won't be significantly eased. ... not terribly significant and the abstraction can be kept very light ... >> If they where a credible provider of support and development for this ... >> services, exactly like Oracle does, but without trapping you into a ...
    (comp.lang.php)
  • RE: Repairing / modyfing Exchange
    ... Customer Service and Support for more immediate assistance. ... This service gives you access to Microsoft technical support engineers who ... database by using the old Server's database files, ... >> up with the First Storage Group, so you would like to delete it and then ...
    (microsoft.public.windows.server.sbs)
  • Re: we substitute the monthly war
    ... Hey, go obtain a database! ... Mohammad! ... in support of it. ...
    (sci.crypt)
  • Re: Unisys OS/2200 DMS / TIP / COBOL Migration
    ... support the legacy system api's that the application is using. ... differences in COBOL compiler dialects. ... What DBI does is to provide legacy database (DMS) ... the legacy database to the COBOL applications. ...
    (comp.sys.unisys)