Using the ASP.Net membership provider in a Windows forms application part 4.

thanks

nerio — Fri, 29 May 2009 12:41:24 GMT

everything is working fine like im in asp.net

thanks for your effort

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Sujan — Wed, 25 Mar 2009 13:58:04 GMT

Thanks, Nice code.

http://ghjejrpyupyuptlhy.com ghjejrpyupyuptlhy,mjkl9qi7wqyq@representative.com,Good site

Sun, 13 Jul 2008 10:06:20 GMT

http://ghjejrpyupyuptlhy.com ghjejrpyupyuptlhy,http://ghjejrpyupyuptlhy.com ghjejrpyupyuptlhy

re: Using the ASP.Net membership provider in a Windows forms application part 4.

venky — Wed, 04 Jun 2008 08:17:33 GMT

thanks for uy code

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Jerome_data — Fri, 02 May 2008 17:29:30 GMT

Hi,

I try to implement your code in other example:

- 1) Winform that call a webservice

- 2) Webservice with Custom UserNameToken with protected override string AuthenticateToken( UsernameToken token )

- 3)Sql Server version is Standard version on my Server, but this database is configured by aspnet_regsql.exe.

All works correctly to create user(like your example) in the webservice, but when i try to validate the user (Membership.ValidateUser("Maurice", "Password_1"), i have this error:

The indicator opening session of instant user is not supported in this version of SQL Server.

Do you have a idea?

Thanks

re: Using the ASP.Net membership provider in a Windows forms application part 4.

olli — Fri, 21 Mar 2008 20:33:47 GMT

you need to provide a provider for the roleManager in order to store role information in a database of your choice.

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Maurice — Tue, 26 Feb 2008 16:21:59 GMT

Hi Adam,

If I am not mistaken Membership.GetAllUsers() should return an (empty) collection instead of null or Nothing is everything is configured right. Both the Membership.GetAllUsers() and Membership.GetUser("username") use the same mechanisms and connection string behind the scene.

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Adam Right — Mon, 25 Feb 2008 22:20:03 GMT

Hi Maurice,

I can get user list on web form like that;

-----------

ListBox1.DataSource = Membership.GetAllUsers();

ListBox1.DataBind();

-----------

But it does not work on windows form, the Membership.GetAllUsers() returns NULL.

but for one user;

MembershipUser user = Membership.GetUser("username")

works good.

Do u have any idea to get the user list for a Windows form ?

Thanks...

Adam

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Raymond — Sat, 03 Nov 2007 12:47:43 GMT

Hi Maurice. I'm currently implementing a custom MembershipProvider and MembershipUser class (inherited).

What's the difference with regards to the App.Config file?

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Kevin — Sun, 12 Aug 2007 00:32:38 GMT

Can you give an example of a valid connection string that points to the same database name in a different location?

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Maurice — Tue, 19 Jun 2007 09:27:35 GMT

Are you running a web app? In that case you need to use the HttpContext.Current.User.Identity.Name.

Otherwise you can try AppDomain.CurrentDomain.SetPrincipalPolicy(System.Security.Principal.PrincipalPolicy.WindowsPrincipal) and see if that makes a difference.

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Gary Young — Mon, 18 Jun 2007 17:33:57 GMT

Maurice,

I have a VS.NEt 2002 running on a Windows 2000 server that uses the System.Threading.Thread.CurrentPrincipal.Identity.Name code to capture the user ID. However, it does not work on a Windows 2003 server. Any ideas?

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Maurice — Sat, 02 Jun 2007 10:34:12 GMT

Hi Edison,

There are two easy ways of doing this. Either set the LocalSqlServer connection string to point to your own database. The drawback, or advantage depending on your point of view, is that other providers use the same connection string and are. The other solution is to use a different connection string name in the connectionStringName="LocalSqlServer" line in the app.config. This way you can specify a different database for just the membership provider.

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Edison Costa — Fri, 01 Jun 2007 21:13:19 GMT

Hi Maurice. Great article. Congratulations. How can i use my own data base (e.g., MyApp.mdf) instead ASPNETDB.MDF ?

Thanks,

Edison

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Maurice — Mon, 29 May 2006 13:41:59 GMT

Hi Miquel,

Using the following: System.Threading.Thread.CurrentPrincipal.Identity.Name will do the trick.

Maurice

re: Using the ASP.Net membership provider in a Windows forms application part 4.

Miguel A. Palizada — Tue, 25 Apr 2006 22:44:12 GMT

Hi, do you know how can i get the value of User.Identity.Name when a assigned the RolePrincipal straighforward in Thread.CurrentPrincipal?

Regards