I have .Net LOB Application developped for a customer.  It works juste fine 29 days out of 30. The application files (.exe, .dll, .config) are simply copied in a shared folder on their server.  Then, the users (around 5-10 concurrent users) execute the application FROM THE SAME SHARED LOCATION.  There is no installation required (after the initial installation). Just like Office on a server in fact...For example : \\FileServer01\PROGRAMS\BigSoft\BigSoft.exeHowever, I sometime encouter weird behavior, and that's where i need help.  For example, the application is executed by 3 user (shown in the Task Manager).  A forth user try to open it, and it opens and load data correctly. Then, when trying to open a particular UserControl, it totally crash.   I simply copied the whole executing folder, and then it was working correctly for that user.  I re-ran the main shared .exe file : crashing again.  for the same exact function.I checked, and no particular database access, file read are done yet.  the error occurs on many different place that dont access stuff yet.  Simple Usercontrols behing created.   I guess there is something to do with memory?  or i dunno..in fact, a simple way to reproduce the error, and I think there is a link between these 2 scenario, is to execute the software, than RENAME the .exe file while executing.  The tools will continnue running, but will start to crash randomly (it is difficult to hit the error.  Like in Random.).So my question : 1 - Do I deploy my application in the worst way possible??2 - If my deployement strategy is fine, why this random error occurs?My hypothesis :  1 - memory problems (yeah, but no..13 Gigs out of 20Gigs used globally on the server) 2 - the .exe is somewhat not totally loaded in memory when executed, or I don't know what (I remember from my delphi days, that there was a way to ask Delphi to load the full program in memory,instead of relying on the base .exe file)Help!!
Deploying a LOB .NET Application on a Terminal Server
.net;deployment;server