Hi.
I got this working by checking the saving and fetching events. So there I am able to stop all processing until I am able to ping the BOS Service using the IdeaBlade.Core.HttpFns.PingServer() method.
By getting this to work I came across the next problem and I would like to know if there is a work around for this problem.
Lets say I have a person entity, and before I save, I disable my Network Adapter, so on the Saving event I am not able to ping the server, which is the expected behaviour, and I give notification to the user, I then enable the network adapter again, then the ping goes through and the person entity is persisted correctly.
But taking the same scenario, Before I save the person entity, I kill the ServerConsole application, so now on the saving event, I am also not able to ping the BOS Server. I then start the ServerConsole again, and then I am able to ping the Server again, but this time the person entity is not saved. I get a "there is not endpoint listening error".
Here is the questions then.
1. What should I do on the client side when the ServerConsole crashes while the users are logged in. Because restarting the BOS ServerConsole application alone does not work.
2. Do you keep a reference to the current working ServerConsole, that is unique for the ServerConsole ? Otherwise how come it works when the network adapter is disabled and enabled again, but not when restarting the BOS Service ?
3. Is there anyway to notify the front end when the BOS Service crashes ?
I know I can catch the exceptions, but would like to do something before the exceptions occur.
Kind regards
Edited by CaptainOrgange - 13-Oct-2011 at 9:51pm