|
|
microsoft.public.dotnet.framework.aspnet |
C) Change the ASP.NET Web Site Administration Tool to 'know' that I believe the WSAT tool is only available locally.....I learnt this the hard You probably don't want to hear this, but I'll give you the advice anyways. Go here: And take a hour or so ... and get the crappy Access Membership Provider You'll learn the key items needed to swap out to a custom one. .. Then approach the MySql version with that knowledge. .. I did this (a year and half ago) and that little exercise still sits with This might help as well. > I believe a few steps are necessary and Im not sure of the order or > A) Create the DB schema on a (shared host) MySQL db... Does anybody > B) Set up the asp project to have a reference to the correct provider > C) Change the ASP.NET Web Site Administration Tool to 'know' that > D) Any other mystical steps involving importing namespaces etc... > Any takers?
we're now using a remote provider...
way.
Thus my opinion is that is is a hobbyist tool, and not worth the effort.
http://aspnet.4guysfromrolla.com/demos/printPage.aspx?path=/articles/...
working.
Try not to just look at the code setup/config setup, but actually get it
working.
Once you get one working..the others seem easier.
I suggest the Access one becaue at least you have one that differs
signficantly from Sql Server...but is decently documented.
me....as I can swap out to a custom one quickly now.
http://www.devx.com/asp/Article/29256/0/page/3
> Later still and...
> exactly how to go about them:
> have the SQL already made?
> ie do something in web.config relating to <providers> and <connection
> string>...
> we're now using a remote provider...