M
MrAvgProgrammer
Guest
I have a WinForm application which gets installed to a mapped drive on the network. This process will get repeated for every Desktop/Laptop that needs to use this exe.
End Result Mapped drive contains all my DLL's and the EXE. All network users point to this EXE. It works great in this environment.
My issue is a different client is trying to use a Terminal Server(TS)/ Remote Desktop Environment to run my software. If using the same mentality they should be map a network drive and then install my software on each user session.
BUT their IT guy said you only need to install apps 1 time on a server. So he did 1 time and the users are experiencing random app crashes, freezes, and strange errors that I have not been able to reproduce on any of our development machines. Their IT person is reluctant to attempt to install on every user session claiming, "It doesnt matter".
What is the proper/ recommended way of installing software on a TS so that user sessions are not "stepping on each others toes"? That is what I believe it happening.
Thank you for any suggestions or feedback.
Continue reading...
End Result Mapped drive contains all my DLL's and the EXE. All network users point to this EXE. It works great in this environment.
My issue is a different client is trying to use a Terminal Server(TS)/ Remote Desktop Environment to run my software. If using the same mentality they should be map a network drive and then install my software on each user session.
BUT their IT guy said you only need to install apps 1 time on a server. So he did 1 time and the users are experiencing random app crashes, freezes, and strange errors that I have not been able to reproduce on any of our development machines. Their IT person is reluctant to attempt to install on every user session claiming, "It doesnt matter".
What is the proper/ recommended way of installing software on a TS so that user sessions are not "stepping on each others toes"? That is what I believe it happening.
Thank you for any suggestions or feedback.
Continue reading...