By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,652 Members | 1,337 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,652 IT Pros & Developers. It's quick & easy.

ASP.NET 2.0's Membership, Roles, and Profile\Client Server

P: n/a
I have an application that is mostly client-server but also will have web
modules as well.

I need the whole authentication, roles, etc. Pretty much exactly what the
asp.net 2.0 sql membership provider, provides.

Is it a reasonable concept to take the asp.net concept and bolt it onto the
client server apps? granted, there is no gui for the client server parts,
but that is ok. There is still the authentication and passwords and things
that are useful and time savings.

Thanks,
jeff
May 24 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a

I've flirted with that idea myself.

I think its a good idea to implment your own version of the abstract class.

Make sure its a true business layer object, and then you're safe for the
winforms and web.

...

I think the biggest reason its "linked" to asp.net .. is that the built in
implmentation that microsoft provides, .... includes the web gui to add
users/roles.

This was all for "Rapid Development" in 2.0.


"Jeff Jarrell" <jj************@yahoo.com> wrote in message
news:ee**************@TK2MSFTNGP05.phx.gbl...
I have an application that is mostly client-server but also will have web
modules as well.

I need the whole authentication, roles, etc. Pretty much exactly what the
asp.net 2.0 sql membership provider, provides.

Is it a reasonable concept to take the asp.net concept and bolt it onto the client server apps? granted, there is no gui for the client server parts,
but that is ok. There is still the authentication and passwords and things that are useful and time savings.

Thanks,
jeff

May 24 '06 #2

P: n/a
On Tue, 23 May 2006 22:45:27 -0400, "Jeff Jarrell"
<jj************@yahoo.com> wrote:
I have an application that is mostly client-server but also will have web
modules as well.

I need the whole authentication, roles, etc. Pretty much exactly what the
asp.net 2.0 sql membership provider, provides.

Is it a reasonable concept to take the asp.net concept and bolt it onto the
client server apps? granted, there is no gui for the client server parts,
but that is ok. There is still the authentication and passwords and things
that are useful and time savings.

Thanks,
jeff


Take a look at what Juval has done with web services to make this
happen.
http://msdn.microsoft.com/msdnmag/is...5/04/Security/
Peter Kellner
http://peterkellner.net
May 24 '06 #3

P: n/a
Ok, i will give it a read and see where it goes.

thanks,
jeff

"PeterKellner" <pk**********@73rdstreet.com> wrote in message
news:l9********************************@4ax.com...
On Tue, 23 May 2006 22:45:27 -0400, "Jeff Jarrell"
<jj************@yahoo.com> wrote:
I have an application that is mostly client-server but also will have web
modules as well.

I need the whole authentication, roles, etc. Pretty much exactly what the
asp.net 2.0 sql membership provider, provides.

Is it a reasonable concept to take the asp.net concept and bolt it onto
the
client server apps? granted, there is no gui for the client server parts,
but that is ok. There is still the authentication and passwords and
things
that are useful and time savings.

Thanks,
jeff


Take a look at what Juval has done with web services to make this
happen.
http://msdn.microsoft.com/msdnmag/is...5/04/Security/
Peter Kellner
http://peterkellner.net

May 24 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.