Hi Gary,
Have you used any of the ASP.NET 2.0's services (such as Membership,
RoleManager, Profile ....) in your ASP.NET application? For all these
services, ASP.NET 2.0 by default use a connectionstring pointed to a local
"ASPNETDB.mdf" (under App_Data folder). here is the default
connectionstring in the machine.config file:
============
<connectionStrings>
<add name="LocalSqlServer" connectionString="data
source=.\SQLEXPRESS;Integrated
Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User
Instance=true" providerName="System.Data.SqlClient" />
............
============
Also, whenever your ASP.NET application has called any code that use those
services, if the runtime found that the "aspnetdb.mdf" is not existed, it
will try creating it. That's is possibly the cause why you find the
"ASPNETDB.mdf" file be created without your interactive operation.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
