MDI Application in Terminal Services

HI

I am pretty new to the VB.net world, and have recently had to produce a MDI VB.net (vs2003) application to be used on Terminal Services. I have exeperienced 2 problems:-

The biggest problem I am faced with at the moment is memory - it appears that although I am disposing all objects on form close (including higher level business objects and dataset/datatables, SQL connections etc) the memory used is not being released. I've read alot about the GC.Collect which I used as a test but calling this actually increased the memory useage (go figure!). I've read about calling the the SetProcessWorkingSetSize and the Working Set, but as this is on TS I was concerned I might be landing myself into more problems by calling this. Anyone got any ideas or know if calling either of these is a good idea in TS

The second problem I have is when I install on the TS server (after changing user to install, installing the application and then change user back to execute), the users profile for the shortcut to the exe (in the installation folder) is lost. When I first released this live it wasn't a problem as we modified the profile to pick up this shortcut, but after the 3rd upgrade it suddenly lost it, and since then we have to manually alter the users profile - this is despite installing this for Everyone and accepting the default install location (C:\Programfiles....) and not changing the name of the exe - has anyone got any ideas I need to get this fixed as we are wanting to write a script which will install the .MSI with all the prompts taken out so that we don't have to keep visiting site each release.

many thanks
Scooby

Answer this question

MDI Application in Terminal Services

MDI Application in Terminal Services

Answer this question