On Tue, Apr 12, 2011 at 5:58 PM, Keidrick Pettaway <[email protected]> wrote: > Creating your own membership class would be the best option. It may be more > painful upfront, but in the long run you will be able to reuse this class > for any other application that will need to use role-based authentication. --------------------------
Why go through all of that? M$ has it already done to be used in a multi business server or a multi application one. -- Stephen Russell Unified Health Services 60 Germantown Court Suite 220 Cordova, TN 38018 Telephone: 888.510.2667 901.246-0159 cell -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
