We're moving one of my websites to production.
Because of a firewall and the website and database being on different
machines, the website can't connect directly to the SQL server. We've
set it up so we're running all of the database access through a WCF
service. All of this works fine.
The problem, however, I've discovered lies in the AspNetSqlProvider.
I'm not too familiar with providers other than setting it up for your
site, but from what I gather, you pass the provider object a connection
string and it automatically handles ASP.NET accounts for your website. I
can't have this on production, however, as I stated, the website and
database can't see each other and the automatic linking of the IIS and
database won't work.
Judging by this
topic, this is not an original concept/i ...
Go to the complete details ...