Re: Membership Provider deployment/App_Data directory just wont die!!! :-)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Maybe that didn't help:

Here is another link:
http://www.devx.com/asp/Article/29256/1954?pf=true

which talks about using Access.

Of course you don't care about Using Access.
You care about "not using the default".


"sloan" <sloan@xxxxxxxxx> wrote in message
news:%23tZq7czwHHA.5036@xxxxxxxxxxxxxxxxxxxxxxx
I think what you're looking for is:

<remove name="AspNetSqlRoleProvider" />

See
http://technet2.microsoft.com/Office/en-us/library/23b837d1-15d9-4621-aa0b-9ce3f1c7153e1033.mspx?mfr=true

or do some googling



"Jeppe Jespersen" <jdj at jdj dot dk> wrote in message
news:%23ZfzScywHHA.5008@xxxxxxxxxxxxxxxxxxxxxxx
I'm deploying a web app that uses the Membership API. Great stuff. Until
deployment :-(

On my development maching, i run everything from a database registered in
the SQL Server Management Studio. That is, my aspnetdb and a "homebrew"
database for other purposes. In my web.config, I have set up a
connectionstring, and have defined a new provider that uses this
connectionstring. Like this:

<connectionStrings>
<add name="aspnetConnectionString"
connectionString="Server=.;database=aspnetdb;Integrated Security=True;"
/>
</connectionStrings>

My provider is defined as follows:

<membership defaultProvider="AspNetSqlMembershipProvider" >
<providers >
<clear/>
<add name="AspNetSqlMembershipProvider"
connectionStringName="aspnetConnectionstring"
enablePasswordRetrieval="true"
enablePasswordReset="true"
requiresQuestionAndAnswer="true"
applicationName="/[APPLICATIONNAME-FRA-DIN-VELKOMST-EMAIL]"
requiresUniqueEmail="false"
passwordFormat="Clear"
maxInvalidPasswordAttempts="5"
minRequiredPasswordLength="6"
minRequiredNonalphanumericCharacters="0"
passwordAttemptWindow="10"
passwordStrengthRegularExpression=""
type="System.Web.Security.SqlMembershipProvider,System.Web,
Version=2.0.0.0, Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" />
</providers>
</membership>

What I was hoping, was that this configuration would completely bypass
the
App_Data folder. On my dev machine, this seems to work, except that it
DOES
create the database files in App_Data - but it still uses my "original"
aspnetdb database that is registered on the SQL Server (not Express).

I coult live with that if it only worked on my production server - but it
doesn't.

So.... how do I use ONLY the registered database on my non-express SQL
Server without ASP.Net creating App_Data folders (and contents) when I
don't
want or need it?

Jeppe Jespersen
Denmark







.

Relevant Pages

  • RE: Accessing SqlServer(Express) data on the server
    ... As for the ASP.NET, it is built upon the .net framework, so generally all ... you can change the connectionstring to point to another ... manually create another database (named "MyASPNETDB" in SQL Express ... you can even use SQL Server authentication(specify username/password ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: ADP - Copy mdb table to SQL Server
    ... opening a table using ADO in code requires ... connect to sql server and to your database. ... I suspect that the ConnectionString Provider I am using is incorrect - ...
    (microsoft.public.access.formscoding)
  • Re: Transfer data(base) from MSDE to SQL Server
    ... Live just means that database is 'in use'. ... I do care about learning how to do it all:) ... Starting with learning what DTS is all about. ... I know little else about SQL Server or DTS, ...
    (microsoft.public.sqlserver.replication)
  • Re: Session variable. Secure ?
    ... well - as long as you have a secret (connectionstring with password) you can't escape having that secret in memory in plain text. ... Use integrated security for the database and no password is exposed at all. ... SQL Server, you could run the application pool under a special ... session/application variables get submitted "across the wire" og ...
    (microsoft.public.dotnet.security)
  • Re: I seem to be locked out of my database
    ... some reason the SQL Server was switched over to SQL Server only ... tell us which account you think should be using the SQL Server ... open an ADO connection from your webpage), try to connect to the database ... I have a connectionstring right now that reads like this: ...
    (microsoft.public.sqlserver.security)