Membership and Roles ASP- Basics Sorely Needed

I am trying to use a MySQL db hosted on a shared server as an ASP.NET
Membership Provider and .net framework 3.5 (visual studio 2008)
I am new to a lot of this and have found the following websites which
offer some degree of help but by no means a complete solution or
uncomplicated explanation of whats involved:

1) http://blog.nolanbailey.com/2008/03/...e-provider/194
Very good but not complete enough for my level eg:
"<add name="MySQLMembershipProvider" autogenerateschema="true" ...."

2)
http://aspnet101.com/aspnet101/tutorials.aspx?id=63
Looks initially promising and the kind of solution simplicity I would
expect in reality but...
the first stage of the proceeedings doesnt work out for me on my vista
machine....
c:\Windows\Microsoft.NET\Framework>aspnet_regsql -W
'aspnet_regsql' is not recognized as an internal or external command,
operable program or batch file.

3)
http://www.codeproject.com/KB/databa...select=2476367
Many credible sources point to this page but running MySQL
Administrator and trying to execute the sql to alter tables I run into
syntax errors the origins of which I dont yet understand.

4) http://www.dotnetsurfers.com/Blog/20...orization.aspx
Not sufficiently detailed.

Can anyone point me to a reasonable set of instructions to SETUP ASP
MEMBERSHIP AND ROLES ON A MySQL db on a SHARED REMOTE SERVER, USING
Visual Studio 2008 and its Login, New Member etc wizards and
templates?

I would really appreciate any help.

Dan

A few hard hours later and I am very frustrated- there seems to be
very little support for MySQL regarding this seemingly basicish task-
is it the case that to use MySQL in this scenario you have to be a
hardcore ASP/SQL/general programmer? I cannot find a single video that
illustrates anything like this concept nor any straigtforward,
complete, relatively up to date guidelines. From an outsiders point of
view it seems like the guys at MySQL have done all the hard work
designing the right stuff- but insufficient support exists to
encourage MySQLs use in this manner.
I want to manage users and roles and get some information such as age
group on a shared server preferably using MySQL. I have now lost 2
days looking in vain through very technical and complicated half-
descriptions of how to build an operating system on a spacestation
from scratch- I am only trying to build a hello world roles and
membership on a shared MySQL server, its like reading Microsoft help
files... Is it really that hard?

On 11 Apr, 11:58, DanWeaver <danofwea...@googlemail.com> wrote:
> A few hard hours later and I am very frustrated- there seems to be
> very little support for MySQL regarding this seemingly basicish task-
> is it the case that to use MySQL in this scenario you have to be a
> hardcore ASP/SQL/general programmer? I cannot find a single video that
> illustrates anything like this concept nor any straigtforward,
> complete, relatively up to date guidelines. From an outsiders point of
> view it seems like the guys at MySQL have done all the hard work
> designing the right stuff- but insufficient support exists to
> encourage MySQLs use in this manner.
> I want to manage users and roles and get some information such as age
> group on a shared server preferably using MySQL. I have now lost 2
> days looking in vain through very technical and complicated half-
> descriptions of how to build an operating system on a spacestation
> from scratch- I am only trying to build a hello world roles and
> membership on a shared MySQL server, its like reading Microsoft help
> files... Is it really that hard?

MySQL is an RDBMS. It implements SQL.

What you are asking about has nothing to do with MySQL per se. It is
like suggesting that the makers of nuts and bolts should document how
to use them to build a car!

> MySQL is an RDBMS. It implements SQL.
>
> What you are asking about has nothing to do with MySQL per se. It is
> like suggesting that the makers of nuts and bolts should document how
> to use them to build a car!

Haha. Quite funny. But it isnt quite like that: it is like wishing
that a kit-car manufacturers, or some enthusiasts
placed their experiences of where to get the right oil in a public
place to encourage others to have a go and not buy a normal one from
the shop (ie SQLserver)! Hehe.

I believe a few steps are necessary and Im not sure of the order or
exactly how to go about them:

A) Create the DB schema on a (shared host) MySQL db... Does anybody
have the SQL already made?

B) Set up the asp project to have a reference to the correct provider
ie do something in web.config relating to <providers> and <connection
string>...

C) Change the ASP.NET Web Site Administration Tool to 'know' that
we're now using a remote provider...

D) Any other mystical steps involving importing namespaces etc...

Any takers?

On Fri, 11 Apr 2008 06:16:06 -0700 (PDT), DanWeaver wrote:
>
>> MySQL is an RDBMS. It implements SQL.
>>
>> What you are asking about has nothing to do with MySQL per se. It is
>> like suggesting that the makers of nuts and bolts should document how
>> to use them to build a car!
>
> Haha. Quite funny. But it isnt quite like that: it is like wishing
> that a kit-car manufacturers, or some enthusiasts
> placed their experiences of where to get the right oil in a public
> place to encourage others to have a go and not buy a normal one from
> the shop (ie SQLserver)! Hehe.
>
> I believe a few steps are necessary and Im not sure of the order or
> exactly how to go about them:
>
> A) Create the DB schema on a (shared host) MySQL db... Does anybody
> have the SQL already made?
>
> B) Set up the asp project to have a reference to the correct provider
> ie do something in web.config relating to <providers> and <connection
> string>...
>
> C) Change the ASP.NET Web Site Administration Tool to 'know' that
> we're now using a remote provider...
>
> D) Any other mystical steps involving importing namespaces etc...
>
> Any takers?

So, you're basically asking us to do you your project for you. Great.
I'll tell you the same thing I tell coworkers that want things done that
I don't want to do. I'll handle step A, and it'll be done two days after
I get a complete set of requirements, exactly as documented in those
requirements.

--
71. If I decide to test a lieutenant's loyalty and see if he/she should be
made a trusted lieutenant, I will have a crack squad of marksmen standing
by in case the answer is no.
--Peter Anspach's list of things to do as an Evil Overlord

DanWeaver wrote:
>> MySQL is an RDBMS. It implements SQL.
>>
>> What you are asking about has nothing to do with MySQL per se. It is
>> like suggesting that the makers of nuts and bolts should document how
>> to use them to build a car!
>
> Haha. Quite funny. But it isnt quite like that: it is like wishing
> that a kit-car manufacturers, or some enthusiasts
> placed their experiences of where to get the right oil in a public
> place to encourage others to have a go and not buy a normal one from
> the shop (ie SQLserver)! Hehe.
>
> I believe a few steps are necessary and Im not sure of the order or
> exactly how to go about them:
>
> A) Create the DB schema on a (shared host) MySQL db... Does anybody
> have the SQL already made?
>
> B) Set up the asp project to have a reference to the correct provider
> ie do something in web.config relating to <providers> and <connection
> string>...
>
> C) Change the ASP.NET Web Site Administration Tool to 'know' that
> we're now using a remote provider...
>
> D) Any other mystical steps involving importing namespaces etc...
>
> Any takers?
>
>
>

I would agree with Peter. You are asking enthusiast [and professionals]
to create an application design, database design and then do all of the
programming and database creation and implement it on the tools you
think you want. Do we get a cut of the profits? My hourly rate for such
is probably a lot more than you want to pay.

Shared host is irrelevant. Get a local development box and go to town...

No, Peter, that's not it at all. Michael; I wasn't asking for "...an
application design, database design" etc; merely advice on starting
points/ info sources from those with more experience.
I shant lecture overly on the unuseful nature of cynical sarcasm (save
when its genuinely funny!) when it comes to pedagogy: I am interested
in others experience as a means to educate myself, save time and not
reinvent the wheel. I hope and believe that's roughly what these
groups are for.
Fortunately, I received some useful advice here if anyone is following
this thread looking for the same stuff:

http://groups.google.co.uk/group/mic...1987f59cb8b7f#

From a few days poking around and trying things out it seems that the
(low) level of plain- english support makes a MySQL db for use with
asp.net a tricky proposition for anything other than a very
experienced programmer. I'm going to try and use MS SQLServer.

Good luck all.
Dan