How to stop creating the aspnetdb.mdf database
If you use the asp.net membership providers, having visual studio keep this sql database file around for deployment can sometimes be convenient. However, what if you want to use your own production database specified in the web config for the membership tables and don't want this database to be created everytime you deploy to production? There is a solution to this problem. You simply disable this in the machine.config of your framework version. Here is how to turn this off.
- Browse using windows explorer to c:\windows\microsoft.net\framework\your dot net version\config
- Open the machine.config file in visual studio or notepad
- Scroll down until you get to a line for connectionstrings
- Comment out this line
- <add name="LocalSqlServer" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient" />
- Build your application
Once you delete the aspnetdb.mdf file and rebuild, it shouldn't come back again.
Revision number 2, Friday, January 20, 2012 5:34:01 PM by tmorton
You must Login to comment.
|
Tue, Jan 3, 2012 6:46 AM
by mehrdad_t
|
when site is deployed ,there is no access to machine.config this solution is incorrect ,it's better to solve a problem by this way: in web.config connectionStrings> remove name="LocalSqlServer"/>
.. or connectionStrings> clear/>
...
|
|
Sun, Jan 22, 2012 3:28 AM
by morefays
|
if you modify the machine.config it will effect all the application not instead of one application better to used web.config file instead of machine.config
|
|
Wed, Jan 25, 2012 1:26 AM
by yrb.yogi
|
as suggested use web.config file to remove this section. machine.config file changes apply to all .net application while web.config file is application specific.
|
|
Wed, Mar 7, 2012 9:34 AM
by venkatmca008
|
if I change machine.config It will affect all apps.
|