Okay...This Application Settings stuff is driving me nuts. Something conseptually so simple should not be this hard to get working.
Here is my
I have a .NET 4 application in which I generated a web reference from a web service wsdl.
I see that it creates an endpoint property in the app.config file which corresponds to a settings class that is autogenerated. I compile my release code and copy the executable and config file to a local drive.
By default, the url points to the endpoint that was added by the designer.
Now, I want to change my application configuration to point to the production version the the webservice.
To do this I thought all I had to do was change the value in the app.config file. However, the application never reads from the config, it's always taking the default setting compiled into the settings class. I'm at a loss as to why this is happening.
I have search through this forum and there are so many different posts on application settings but all I want to do is change the config file manually without having to recompile. I'm not doing any runtime settings modifications.
What if down the line we change the alias to the web service hosting the service. I can't imagine Microsoft really expects us to have to rec
View Complete Post