DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: Tue, 24 Jul 2007 13:18:47 -0600,    posted on: microsoft.public.dotnet.framework.aspnet.security        back       

Thread Index
  1    Nathan Laff
          2    Nathan Laff


Asp membership database question   
I have a SQL Express 2005 db which a WinForm application connects to.
I've chosen to use the ASP SQL Membership provider to manage application 
users and roles.

Currently, I run the aspnet_regsql tool on my existing database. Does it 
make sense to create a seperate database just for users and roles? What is 
the "best practice" scenario in this case?

Thanks
Date:Tue, 24 Jul 2007 13:18:47 -0600   Author:  

Re: Asp membership database question   
Oh, also. What is the recommended use of SQL Server authentication when 
using the asp membership provider?

Should I "mirror" users created with ASP.NET into my SQL Server users? Or 
just create one SQL server user and hard code it into my application for the 
database login?

Thanks for any help!

"Nathan Laff"  wrote in message 
news:F18FAB9E-2CF2-4F14-9338-104CF1A6FDA1@microsoft.com...

>I have a SQL Express 2005 db which a WinForm application connects to.
> I've chosen to use the ASP SQL Membership provider to manage application 
> users and roles.
>
> Currently, I run the aspnet_regsql tool on my existing database. Does it 
> make sense to create a seperate database just for users and roles? What is 
> the "best practice" scenario in this case?
>
> Thanks 
Date:Tue, 24 Jul 2007 13:31:22 -0600   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us