Sign In| Join
Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 08, 2005 09:17 PM by sjmac
Member
20 Points
4 Posts
May 08, 2005 09:17 PM|LINK
<connectionStrings> <add name="aspnet_staterKits_Test_TimeTracker" connectionString="Data Source=.\SQLExpress;Integrated Security=True;AttachDBFilename=|DataDirectory|aspnetdb.mdf;"/> <remove name="LocalSqlServer"/> <add name="LocalSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;AttachDBFilename=|DataDirectory|aspnetdb.mdf;"/> </connectionStrings>
Am I right that this references the aspnetdb twice, and so the TimeTracker.mdf is never used?
I think this means that all the timetracker data goes in to the same database as the user and role information. Is this intentional? Is it a bad thing?
Steven
sjmac
Member
20 Points
4 Posts
Beta 2 release apsnetdb and TimeTracker DB mix up?
May 08, 2005 09:17 PM|LINK
<connectionStrings>
<add name="aspnet_staterKits_Test_TimeTracker"
connectionString="Data Source=.\SQLExpress;Integrated Security=True;AttachDBFilename=|DataDirectory|aspnetdb.mdf;"/>
<remove name="LocalSqlServer"/>
<add name="LocalSqlServer"
connectionString="Data Source=.\SQLExpress;Integrated Security=True;AttachDBFilename=|DataDirectory|aspnetdb.mdf;"/>
</connectionStrings>
Am I right that this references the aspnetdb twice, and so the TimeTracker.mdf is never used?
I think this means that all the timetracker data goes in to the same database as the user and role information. Is this intentional? Is it a bad thing?
Steven