Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > SQLMembershipProvider

Reply
Thread Tools

SQLMembershipProvider

 
 
Ryan
Guest
Posts: n/a
 
      01-18-2007
Hello,

I have a question on the default: AspNetSqlProvider. I know that, by
default, this looks for a database created locally in the appdata
directory. Although I have learned how to change the connection, it
involves modifying the web.config file manually, which made me wonder:

-Is the default connection stored anywhere globally? If not, is it
simply a part of the object?

Next, I see that when you go to select the provider in the ASP.Net
Configuration tool, you will get a message (should the local DB not
exist yet) that you should use the aspnet_regsql tool at the command
line. While this tool CREATES the database whereever you want, it does
not change the settings of the ASPNetSQLProvider connection string (at
least for me).

-Is that normal behavior?

I guess I am just trying to get an understanding of where the values of
these things are stored, whether in some global config file somewhere,
in the objects themselves, or elsewhere AND making sure that my GUI is
working properly. I saw a lot of things talking about how the GUI
could really assist in creating the web config file, but perhaps some
things need to be done by hand???


Lastly, I upgraded from Visual Studio 2003 and have IIS 4.0. I do not
see any of my 2005 web projects.

-Is that normal? Do I need to upgrade to IIS 5.0 or higher in order to
fully manage by .net 2.0 apps?

Thanks,
Ryan

 
Reply With Quote
 
 
 
 
sticky
Guest
Posts: n/a
 
      01-18-2007
hi ryan

read through this article

http://aspnet.4guysfromrolla.com/articles/040506-1.aspx

it explains the provider model in detail

Ryan wrote:
> Hello,
>
> I have a question on the default: AspNetSqlProvider. I know that, by
> default, this looks for a database created locally in the appdata
> directory. Although I have learned how to change the connection, it
> involves modifying the web.config file manually, which made me wonder:
>
> -Is the default connection stored anywhere globally? If not, is it
> simply a part of the object?
>
> Next, I see that when you go to select the provider in the ASP.Net
> Configuration tool, you will get a message (should the local DB not
> exist yet) that you should use the aspnet_regsql tool at the command
> line. While this tool CREATES the database whereever you want, it does
> not change the settings of the ASPNetSQLProvider connection string (at
> least for me).
>
> -Is that normal behavior?
>
> I guess I am just trying to get an understanding of where the values of
> these things are stored, whether in some global config file somewhere,
> in the objects themselves, or elsewhere AND making sure that my GUI is
> working properly. I saw a lot of things talking about how the GUI
> could really assist in creating the web config file, but perhaps some
> things need to be done by hand???
>
>
> Lastly, I upgraded from Visual Studio 2003 and have IIS 4.0. I do not
> see any of my 2005 web projects.
>
> -Is that normal? Do I need to upgrade to IIS 5.0 or higher in order to
> fully manage by .net 2.0 apps?
>
> Thanks,
> Ryan


 
Reply With Quote
 
 
 
 
Ryan
Guest
Posts: n/a
 
      01-18-2007
Thanks. I am still not clear about a few things. Per that article, It
does look like the only way to over ride the default database setting
is by editing the web config file by hand. I have done this and it
seems I was successful, BUT I notice that when I navigate to the
Provider selection page under ASP.NET configuration, the provider name
that I created in my application's web.config file does not appear.
Only the default ASPNetSQLProvider appears (unchecked). I seem to be
connecting to a database other than ASPNEWSQLProvider, but am wondering
why the name of the membership provider I setup does not appear as an
option in the list.

Thanks,
Ryan

sticky wrote:
> hi ryan
>
> read through this article
>
> http://aspnet.4guysfromrolla.com/articles/040506-1.aspx
>
> it explains the provider model in detail
>
> Ryan wrote:
> > Hello,
> >
> > I have a question on the default: AspNetSqlProvider. I know that, by
> > default, this looks for a database created locally in the appdata
> > directory. Although I have learned how to change the connection, it
> > involves modifying the web.config file manually, which made me wonder:
> >
> > -Is the default connection stored anywhere globally? If not, is it
> > simply a part of the object?
> >
> > Next, I see that when you go to select the provider in the ASP.Net
> > Configuration tool, you will get a message (should the local DB not
> > exist yet) that you should use the aspnet_regsql tool at the command
> > line. While this tool CREATES the database whereever you want, it does
> > not change the settings of the ASPNetSQLProvider connection string (at
> > least for me).
> >
> > -Is that normal behavior?
> >
> > I guess I am just trying to get an understanding of where the values of
> > these things are stored, whether in some global config file somewhere,
> > in the objects themselves, or elsewhere AND making sure that my GUI is
> > working properly. I saw a lot of things talking about how the GUI
> > could really assist in creating the web config file, but perhaps some
> > things need to be done by hand???
> >
> >
> > Lastly, I upgraded from Visual Studio 2003 and have IIS 4.0. I do not
> > see any of my 2005 web projects.
> >
> > -Is that normal? Do I need to upgrade to IIS 5.0 or higher in order to
> > fully manage by .net 2.0 apps?
> >
> > Thanks,
> > Ryan


 
Reply With Quote
 
sticky
Guest
Posts: n/a
 
      01-29-2007
im not sure why the provider that you have specified is not showing up
in the config tool. I never use it so i cant really comment.

if your site is using the provider that you have specified, then it
must be a problem with the config tool.
they show up when i look at them through the config tool
make sure your membership provider declaration looks something like
this

<membership defaultProvider="SqlMemProvider">
<providers>
<add name="SqlMemProvider"
connectionStringName="SystemConnection"
applicationName="BookingSystem"
type="System.Web.Security.SqlMembershipProvider"
enablePasswordRetrieval="false"
enablePasswordReset="true"
requiresQuestionAndAnswer="true"
requiresUniqueEmail="true"
passwordFormat="Hashed" />
</providers>
</membership>



On Jan 18, 8:21 pm, "Ryan" <(E-Mail Removed)> wrote:
> Thanks. I am still not clear about a few things. Per that article, It
> does look like the only way to over ride thedefaultdatabase setting
> is by editing the web config file by hand. Ihavedone this and it
> seems I was successful, BUT I notice that when I navigate to the
> Provider selection page under ASP.NET configuration, the provider name
> that I created in my application's web.config file does not appear.
> Only thedefaultASPNetSQLProviderappears (unchecked). I seem to be
> connecting to a database other than ASPNEWSQLProvider, but am wondering
> why the name of the membership provider I setup does not appear as an
> option in the list.
>
> Thanks,
> Ryan
>
> sticky wrote:
> > hi ryan

>
> > read through this article

>
> >http://aspnet.4guysfromrolla.com/articles/040506-1.aspx

>
> > it explains the provider model in detail

>
> > Ryan wrote:
> > > Hello,

>
> > > Ihaveaquestionon thedefault:AspNetSqlProvider. I know that, by
> > >default, this looks for a database created locally in the appdata
> > > directory. Although Ihavelearned how to change the connection, it
> > > involves modifying the web.config file manually, which made me wonder:

>
> > > -Is thedefaultconnection stored anywhere globally? If not, is it
> > > simply a part of the object?

>
> > > Next, I see that when you go to select the provider in the ASP.Net
> > > Configuration tool, you will get a message (should the local DB not
> > > exist yet) that you should use the aspnet_regsql tool at the command
> > > line. While this tool CREATES the database whereever you want, it does
> > > not change the settings of theASPNetSQLProviderconnection string (at
> > > least for me).

>
> > > -Is that normal behavior?

>
> > > I guess I am just trying to get an understanding of where the values of
> > > these things are stored, whether in some global config file somewhere,
> > > in the objects themselves, or elsewhere AND making sure that my GUI is
> > > working properly. I saw a lot of things talking about how the GUI
> > > could really assist in creating the web config file, but perhaps some
> > > things need to be done by hand???

>
> > > Lastly, I upgraded from Visual Studio 2003 andhaveIIS 4.0. I do not
> > > see any of my 2005 web projects.

>
> > > -Is that normal? Do I need to upgrade to IIS 5.0 or higher in order to
> > > fully manage by .net 2.0 apps?

>
> > > Thanks,
> > > Ryan


 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
SqlMembershipProvider and Hashed Passwords Glenn ASP .Net 0 06-28-2007 03:29 PM
Encrypted Password with SqlMembershipProvider Glenn ASP .Net 0 06-21-2007 04:24 PM
Want to create a custom membership provider, but use SQLMembershipProvider functionality Mwob ASP .Net 0 10-19-2006 03:13 PM
SqlMembershipProvider question anon2005@comcast.net ASP .Net 3 03-05-2006 09:20 PM
allow username update/change with SqlMembershipProvider ibiza ASP .Net 0 01-24-2006 04:10 PM



Advertisments