Yes, and? That's exactly the behavior you want. The run-time changes the web.config file, Visual Studio notices the changes and offers you to reload it so you can see the new changes in the file and not be fooled by an old presentation of the file.

What's wrong about that? Are you sure you fully understand the concepts of the implementation you're working on?

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!

Hi,

Ok when I run in design I get the message which is fine I get that, if I run on local host it works fine, bith my site & the code you supplied, it's only when I publis to live it seems not to work so I'm guessing it's not my code (phew) but something to do with IIS?

Can you define "live"? What do you know about this server? Maybe its using separate application pools, or maybe the opposite: maybe your site runs in the IIS process and is not restarted automatically. Or, maybe it's a caching issue and you get server an old page? Impossible to tell for me from a distance

I can't help you further with this I am afraid; you'll need to work this out with the one running the live server....

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!

Thank you for all your help, I appreciate the time.

Louisa