When the Settings file is locked by a virus scanner we are receiving an EBusy error on Windows machines. When we attempt to retry the operation (set, get, etc) our Settings file will be truncated. We have noticed this issue on 3.2 however it appears to be fixed in the 4.0.2 release. Our problem with migrating to 4.0.2 is the missing watch functionality which we are using. Have you experienced the truncated file issue in 3.2? Is there a recommended way to successfully retry using version 3.2?
When the Settings file is locked by a virus scanner we are receiving an EBusy error on Windows machines. When we attempt to retry the operation (set, get, etc) our Settings file will be truncated. We have noticed this issue on 3.2 however it appears to be fixed in the 4.0.2 release. Our problem with migrating to 4.0.2 is the missing watch functionality which we are using. Have you experienced the truncated file issue in 3.2? Is there a recommended way to successfully retry using version 3.2?