K
Kirk
Hello,
I am a somewhat experienced VS 2005 user who is trying to us the
ASP.NET Web Site Administration Tool for the first time. I have
experimented with it on my local IIS and it seems to be an excellent
tool for security administration. However, I have some long term
questions.
Where does the W.S.A.T. store its information? In my local SQL Server
2000, I can see a database called "aspnetdb" - however none of the
tables contain any data (despite the fact that I have created a couple
of users & roles). Is it storing them in the local instance of SQL
Server 2005 Express that was installed with VS 2005? If so, I suppose
I need to install that "SQL Server 2005 Management Studio Express
Edition", correct?
This leads me to my next question. While I don't really "care" right
now where the data is stored, I WILL care when I move my completed
application to the real SQL Server 2000 that my company uses. How
would I make the switch so that my ASP.NET application looks in a
location on another server? I have seen some articles discussing this
issue, and they all deal with modifying a .config file to use a
different connection string. Am I on the right track?
Obviously, I am a newbie when it comes to this stuff, so I would
greatly appreciate any guidance that anyone could offer me.
Thank you in advance,
I am a somewhat experienced VS 2005 user who is trying to us the
ASP.NET Web Site Administration Tool for the first time. I have
experimented with it on my local IIS and it seems to be an excellent
tool for security administration. However, I have some long term
questions.
Where does the W.S.A.T. store its information? In my local SQL Server
2000, I can see a database called "aspnetdb" - however none of the
tables contain any data (despite the fact that I have created a couple
of users & roles). Is it storing them in the local instance of SQL
Server 2005 Express that was installed with VS 2005? If so, I suppose
I need to install that "SQL Server 2005 Management Studio Express
Edition", correct?
This leads me to my next question. While I don't really "care" right
now where the data is stored, I WILL care when I move my completed
application to the real SQL Server 2000 that my company uses. How
would I make the switch so that my ASP.NET application looks in a
location on another server? I have seen some articles discussing this
issue, and they all deal with modifying a .config file to use a
different connection string. Am I on the right track?
Obviously, I am a newbie when it comes to this stuff, so I would
greatly appreciate any guidance that anyone could offer me.
Thank you in advance,