J
Jane Jie Chen
Guest
We have one WPF application and one window service. WPF application and service are not communicated each other.
WPF application controls instrument. The service run on itself and will be launched when PC starts.
The service is to perform auto backup database each day at same time (i.e. 11:30pm). There is one restriction for backup database when WPF application is running instrument, auto backup database should hold until instrument run finish and then it can start auto backup database.
So far, we use global mutex. when WPF application start run instrument, it acquires mutex and block it.
when service ready to backup database, it checks mutex if available, if the mutex is not available, means instrument is running. the service will wait in a loop and checking until the mutex becomes available.
If the mutex is available, means instrument is not running, service can start backup database.
During testing, we see some limitation with using mutex.
Is there other good way to share data between two .Net processes? Thx!
Continue reading...
WPF application controls instrument. The service run on itself and will be launched when PC starts.
The service is to perform auto backup database each day at same time (i.e. 11:30pm). There is one restriction for backup database when WPF application is running instrument, auto backup database should hold until instrument run finish and then it can start auto backup database.
So far, we use global mutex. when WPF application start run instrument, it acquires mutex and block it.
when service ready to backup database, it checks mutex if available, if the mutex is not available, means instrument is running. the service will wait in a loop and checking until the mutex becomes available.
If the mutex is available, means instrument is not running, service can start backup database.
During testing, we see some limitation with using mutex.
Is there other good way to share data between two .Net processes? Thx!
Continue reading...