Dear sir, Thank you for your quick response and sorry for causing the confuse. We developed a material transferring control system(MCS) that operate in TFT/Semiconductor FAB clean room and need to operate 24 hours per day whole year exceprt during PM. Our customer need to request a shutdown for bug fix from another manufacture department who usually reluctantly want to stop this system because it will stop the whole line and the equipment will be idle during this bug fixed operation.( The saft operating buffer time usually needs 1:00 hour.) The plugin assembliy needs to handle event sending from transferring equipment and do the normal or exception handle(such as the carrier id NG,mismatch or duplication handle) .It's from this part that new requirement coming out and we need to add some rule check handling or fix some codes in the assembly and yes, fix bug too.
The system is winform based and develop in C# based on .net 1.1, so it's not a web stuff. I know that IIS uses appdomain to manage assembly reload issue. We can do it in the default appdomain but like I said, I still survey a better solution for this issue. Script engine is the ongoing topic, I use TSQL to write some stored procedures that let me feel Sql server's script engine is so powerful that I can revise Tsql codes or add new function stuff during runtime. Best regards Peter On 12/22/05, J. Merrill <[EMAIL PROTECTED]> wrote: > > It is apparently not a web app, right? (If it is, IIS knows how to use a > new version, discarding the old version as soon as it has finished all its > outstanding requests.) > > Not knowing what the program is doing, where it gets the input it's > supposed to be processing, what it does with the results, and exactly what > "cannot be stopped" means (will someone die if a request isn't processed, or > will your company lose $1,000,000?), it's hard to really make a > suggestion? After all, if the current program has a bug, is it worse to > miss a few requests or to provide the wrong answer to some of them? > > If you can write a main program that does the work by calling code in > another assembly, that main program can (hopefully) be written so that it > never has to change. It can have a mechanism (like a file being changed) > that tells it that a different assembly needs to be used; the main program > can switch to using any new assembly that does the real work (presumably > better than the other one), and stop using the old one, at any point. It > seems you're sort of trying to do that, but the details of what's being > processed etc make a difference. > > At 09:09 PM 12/20/2005, peter lin wrote (in part) > >Dear all, > > We develop a system that cannot(better not) be stopped while bug > fixed > >or rule changed. > > > J. Merrill / Analytical Software Corp > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
