Membership connection string

[Steven Blair]

Hi,

My web application was poitning to a cal instance of Sql 2005.
Connection string setup in the web.config and is working fine.
I know need it to point to a security Database on a remote Sql Server
2005, so the connection string is updated and using ASP.NET
configuration shows me the new settings (I create some new users here).
The problem is, when I attempt to login, my application keeps using the
local Database and not the remote.
Is the connection string cached somewhere?

Any help is appreciated.

Steven

*** Sent via Developersdex http://www.developersdex.com ***

[Nicholas Paldino [.NET/C# MVP]]

Steven,

When you changed the web.config file, a new instance of your web app
should have been started (assuming that it was already running). The
original instance will still run, until it finishes servicing the current
sessions (I believe it is sessions, not just current requests, I could be
wrong).

The info in web.config is not cached when you change it.

Have you tried restarting the web app?

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Steven Blair" <st**********@btinternet.comwrote in message
news:OD**************@TK2MSFTNGP04.phx.gbl...

Hi,

My web application was poitning to a cal instance of Sql 2005.
Connection string setup in the web.config and is working fine.
I know need it to point to a security Database on a remote Sql Server
2005, so the connection string is updated and using ASP.NET
configuration shows me the new settings (I create some new users here).
The problem is, when I attempt to login, my application keeps using the
local Database and not the remote.
Is the connection string cached somewhere?

Any help is appreciated.

Steven

*** Sent via Developersdex http://www.developersdex.com ***

[Steven Blair]

Tried restarting the app from the IDE several times.
We fixed the problem by restarting the IDE. However, I suspect the
ASP.NET Development server was still running and maybe that was the
thing that should be stopped.

Thanks for the help.

*** Sent via Developersdex http://www.developersdex.com ***