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.
The ASP.NET Wiki was started by Scott Hanselman in February of 2008. The idea is that folks spend a lot of time trolling the blogs, googlinglive-searching for answers to common "How To" questions. There's piles of fantastic community-created and MSFT-created content out there, but if it's not found by a search engine and the right combination of keywords, it's often lost.
The ASP.NET Wiki articles moved to CodeProject in October 2013 and will live on, loved, protected and updated by the community.
Submit an article or tip
