Hi guys
Just got back from hol, hence the late reply.
I'm not sure it's anything as complicated as this ya know. Just to reiterate, I have a local login / membership provider and an extra table for my dynamic content in the local AspNetDB inside Web Developer Express. I've created a MSSQL database on my remote server (note it's shared hosting so i don't have access to IIS, but this wasn't a problem on the other sites I've deployed there) and what is happening is:
-
The login fails as it appears that the membership application is still looking for my local service provider, even though I've changed the connection string to point toward the remote server db.
-
The table with the dynamic content however is actually working fine, i.e. looking at the remote database for the content.
Based on this, it would appear that the connection string etc isn't the problem. Maybe the service provider?
Now, when I head to the site config in VWDE 08, and look under security settings, even though I have a remote connection string, it is still looking at the local server fofr membership. In every other site I've deployed remotely, when I launch the site config tool, it looks at the remote site as it should using the connection string, allowing me to add users etc to the remote app.
Any thoughts are massively appreciated!
Thanks
Mark
"Worked upto average" -
em:two, 2007.Music to rock the socks of you:
Green Ball Flyers