The settings are controlled through Web.config, so you can also edit that file.
I personally prefer using a configuration class for this, which allows storing settings in Web.config (or external files) and then also are easily accessible and writable through this class (assuming the user account has rights to write to web.config).
You can find the article and component here:
http://www.west-wind.com/presentations/configurationclass/configurationclass.aspI pretty much use this in all of my applications, since it's just a simple way to have a common configuration storage mechanism that's easy to use unlike the native .NET APIs (along with doing selective encryption, strong typing etc.)
+++ Rick ---
>In SQL Server, I have created a user for a specific database. In the connection string, I have entered the proper username and password. From a desktop application, I can add new records in one of the table. However, from the Web application, the only way to add a new record is to go in the Web site ASP.NET pane and enter an administrative account in the Application pane for the Identity settings. I would like to avoid that step. Considering that I am defining an account to be used in the connection string, is there a way to avoid doing any setting at the Web site level?
