This isn't the case. All my other sites work fine and my hoster didn't do
this.
In 2.0 the web.config is handled differently if precomiled it seems. In my
web deployment project I clicked 'enable web.config file section
replacement' and put this: appSettings=appsettings.config;
Then I created an appsettings.config and added the whole <appSettings>
section.
Is this correct? After I publish do I modify the appsettings.config to make
these changes?
Thanks.
[quoted text, click to view] "Ewild" <Ewild@discussions.microsoft.com> wrote in message
news:5E07F9B5-09FE-4BE4-963F-667AAD132FAA@microsoft.com...
> Admins can lock settings. here is a link.
>
>
http://msdn2.microsoft.com/ms178693.aspx >
> Eric
>
> "VB Programmer" wrote:
>
>> I used to be able to change minor settings in my web.config file when it
>> was
>> on the web server, such as <appSettings> elements. In ASP.NET 2.0 I
>> noticed
>> that there is a web.config AND a PrecompiledApp.config file. So, how can
>> I
>> change <appSettings> (or other) elements once it's been deployed to the
>> server?
>>
>> Thanks!
>>
>>
>>