1)...project location is not trusted
This normally means you've installed it on a network share (a UNC path). This is not the preferred way to install a .net project on a developer's computer.
2)...make sure application for wdproj is installed
This is the web deployment project explained in the deployment chapter. You don't need this for testing on your local computer.
Regarding SQL, your best best is to use SQL Express, since that doesn't even require a connection string, and you can automatically connect to the DB distributed in the code download without making any changes to web.config.
Deploying to a full version of SQL is a little harder, but you can read about that in the deployment chapter, and do some web searches on it. In this case you'll have to attach the DB files to your SQL Server instance and you'll need the right credentials to set up the connection string.
It's very unlikely that this connection name is used by TheBeerHouse: PC315417827683. It's also a bit unlikely that your instance name is SQL05. And I think the AttachDBFilename option is only for the express version.
I suggest you D/L and install the free SQL Express, and then use an unmodified web.config file. Save the more advanced options for later.
Eric
|