We've installed our flagship app on a Windows Terminal Services farm for a couple of our remote users. The network guys are complaining that folks are saving reports and files to the folder where the app is installed, and not to their %APPDATA% folder. Talk has centered around simply changing the working directory to the path pointed to by %APPDATA% if the %TERMINAL_SERVICES% environment variable is set. In a small, test app of two pbls, this works file. For example, when a file SaveAs dialog opens, it defaults to the user's appdata/roaming folder, not the folder where the exe is running as it does now for the big app.
I've always thought that the class loader or whatever it's called, only loads libraries as needed. In my way of thinking, how does it know where the libraries are if you change the working folder? And what about bitmaps? We don't store the full path when inserting a picture into our apps.
Am I being overly concerned and everything will still work with no rework of the app? I don't think so.
Larry