It would seem that some change in service pack 2 of the framework is now preventing my app.config file from reaching the client machine when the client is accessing my application via HTTPS. After a prolonged wait the application continues without having read the file. Interestingly enough I can, using the WebClient and StreamReader objects get the file into memory on the client, again after a prolonged wait, the application functions normally when our HTTP clients access it. The app 'hangs' when calling ConfigurationSettings.AppSettings.
Normally in instances like this I would start by looking at proxies or firewalls involved, however as I am able to uninstall and reinstall the base framework, and have it work, then install SP1 and continue to work, then failing after the install of SP2, I'm led to believe something has change in the framework that I need to compensate for. I've been unable to find any information that might shed some light on this. The application is a rich client, with a URL code group security policy with FullTrust. My question then is, is anyone aware of any changes in SP2 that would account for this behavior? Regards, Dave Thorson =================================== This list is hosted by DevelopMentorŪ http://www.develop.com You may be interested in Guerrilla .NET, 24 March 2003, in London http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com
