Last post Dec 08, 2006 08:19 AM by remember_alestris
Nov 17, 2006 11:10 AM|Mishi|LINK
This db is a part of connection string in web.config but the file is not included in PWS package.
Nov 17, 2006 03:55 PMfirstname.lastname@example.org|LINK
So, did you create a site with the starter kit?
Nov 17, 2006 06:31 PM|Mishi|LINK
I down loaded the the starter kit. Selected the VB part of it which is Zip file. Created new website with this zip file. Then tried to run the site, but encontered with errors during creating database. I decided to create Personal database manually in SQL
Server express by attaching Personal.mdf. Then I realized there must be another mdf file. But I cannot find it.
That's what I have done so far.
I didn't find any straight forward manual to guide me through.
Nov 18, 2006 08:51 AMemail@example.com|LINK
Posting the errors would help you receive suggestions on how to correct them. If you're going to manually create the databases, you'll need to create the membership database as well. ASPNET_REGSQL.EXE is your friend there.
Dec 08, 2006 08:19 AM|remember_alestris|LINK
When you run the site for the very first time, it will create the mdf's as long as you have SQL Server Express 2005 installed.
If you prefer to use SQL 2000 exclusively, you'll need to create a new database and provision it with the roles and memberships API's.
This is done by
1.Running the aspnet_regsql.exe from the command prompt. (found in start menu> programs>Microsoft visual studio 2005>visual studio tools>visual studio 2005 command prompt)
2. Running the personal-add.sql script against the db ( this can be found in the app data folder of the project)
3. Modifying the connection string in the web.config to point to the new database. I would change the name LocalSqlServer to something more relevant.
4. Adding providers in the connection string for roles and membership, and then pointing these providers to the new connection string's name.
This should get everything running smoothly, at least locally. Deployment will be another issue, as your host probably will change the ownership of all your objects, and the app will fail when trying to use a login that was perfect locally.
Hope some of this was helpful. I can provide example of my working web.config if needed.