Jeff Johnson wrote on 2012-09-20: > I have an application on Terminal Services at a large company. I have > several classes and procedures external to the executable in order to be > able to update them because updating the main executable on TS is a > difficult process. The external classes, apps and procedures seems to > work but I was wondering if there isn't a better more organised way to > update an executable running on several application servers. > > TIA
Jeff, A loader application. It would copy the required files from a common store to a user path, then launch the executable in the user path, then exit. The loader application will only be in use when a user is starting the application. The files in the common store should never be in use. Yes, the executable and required files will be copied all over the place, but there is a mechanism that updates them on the fly. Tracy Pearson PowerChurch Software _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
