.NET application resizing issue

[ruggersway]

We are seeing an issue with occasional instances of clients reporting .NET applications are not restoring properly after having been minimized. Initially we thought it was an issue with the application until we noticed that once this was happening it also affected other .NET applications.

Basically, all you see if the Title bar after restoring the application. It isn't even the full size bar. It will be about 3 inches wide, you will see the top left icon, part of the application name, and the minimize/restore/close buttons.

Additionally, in some instances the application will restore off-screen and you have to right-click the item on the taskbar and choose move. If you maximize instead of restore then you can see the application full-screen but you can't minimize or restore the application.

Has anyone ever seen this? I'm kind of at a loss right now. I know the users are running under a fairly strict group policy but I don't know if that could impact the behavior or not.

Any help or ideas would be greatly appreciated.

Thanks

[Plater]

That is strange, I've not heard of that.
Are you making any calls to win32 API, like any SHELL commands are anything that would cause the other applications to go loopy?
It sounds like the .NET CLR is loosing its information on the size/orientation of Display/Screen devices. And possibly also previous window location.

[tlhintoq]

Thought 1:
Nearly all of my apps use the same 'skeleton' of base code as a start point, and that skeleton include methods for resizing and repositioning a window after events like SizeChanged. Any chance your applications do something similar, so one code change has rolled out to multiple programs in revision updates?

Thought 2:
You mentioned strict policies... If the applications are trying to do their own window position save/restore methods but the user doesn't have permission to read/right from the registry or wherever you are saving the data, will the application respond well if it receives 'null' width, height, location values?

Or the values could be corrupt: Are they just trusted or is some range checking taking place to see that a location of {-1920,-400} is even on the current user's desktop?

Thought 3:
Could values from one workstation (user Bob on station 4 that has 3 monitors) be getting applied when he logs into a different station? (user Bob on station 2 that only has 1 monitor) because all values come from the user's directory on the server regardless of which workstation he uses?