Is using the ASP.NET Membership providers in winforms application a bad idea?

.net, winforms

Solution

Using ASP.NET membership providers on a client in a WinForms application is insecure, since a malicious user can replace the provider by one of his own choosing simply by editing the application configuration file.

What exactly are you trying to achieve, and is security important?

Problem

Can anyone think of a reason not use the ASP.NET membership providers in a winforms application? Has anyone have experience doing this?

Original source