In the web.config... I am sorry, it was the connectionstring.config. I made some changes to the connectionstring pointing to our sql2005 server database.
Steps you could take:
Create a new folder on one of the drives of your webserver, Setup a website in IIS, point to the new created folder as the website location.
Build the site in vs2005/2008 on your local drive. Then Copy the content of the builded "Web" folder to the folder on the webserver you have configured a new website for. You only need to copy the content of the "Web" folder to new created website directory to get it running for testing. Then go to the testdomain in your browser (you have setup in IIS) testwebsite/install/install.aspx . Create acount, follow the steps presented.
If you test it on your local machine you need to create a virtual directory and copy the content of the "Web" folder to your web dir. Or point to the "Web" folder directly.
Notes:
- With "Web" folder I mean the /Web/ folder what was extracted from the zip.
- Also make sure that in IIS, website properties, the [.NET tab] the 2.0 framework is selected.
- Also make sure asp.net ajax1.0 extensions are installed on the server running IIS
SQL:
In SQL server (express) login with SA account, create a new database (for example "testshop").
In connectionstring.config (in "Web" folder) alter the active connection string, if you have the DB running on a server point to the servername\SQLname and to the "testshop" dbname.
In my case it is:
<add name="dashCommerce" connectionString="Server=SQLDEVSERV\SQL2005 ;Initial Catalog=testshop;User Id=sa;Password=sa-password;" providerName="System.Data.SqlClient" />
* I dont recomend to use the SA user in production environment, but since we are testing... *
Hope this helps