Friday, 29 August 2003
Thursday, 28 August 2003
WebSite Deployment
Trying to get the Custom actions in a Deployment Projects to work is tough, I have added a user interface dialog based on one of the CheckBox dialogs setup the text and assigned a property name. I the custom actions I then try to execute an application based on a condition RUNSIC = "Checked". No the application does not run. The help was on MSDN Disk 2 April 2003 ?
Contact with friends
Had emails from Gavin and Andre', its great to hear from them again. We lost touch for about 5 years. I must try and get hold of PietM, BobC and Jono.
Managed Service Mutex
Today we tried to use a mutex in a managed service. Creating the mutex in the OnStart and trying to release the mutex in the OnStop.
FAIL: the mutex can only be released by the thread that owns it; the OnStop is called on a different thread to the OnStop. It’s like changing the channel and then giving the remote away.
Some other method will have to be found to tell the other components to stop.
Previously on my UDPCatcher Service I did not experience this scenario, this new service loads up another app domain. Best we look at the whole problem again.
Update: Paul has removed the mutex code and using thread.Suspend and thread.Resume.
The title of this entry has given me a thought "Manages Service Mutex" the Mutex Service, the caller will make a connection to the service and do an async read, the async read complete could mean the mutex is now in your ownership. Ship a little class lib and start the service and bang you have a Mutex that is bound to a tcpip connection, I think this can be handed around.
FAIL: the mutex can only be released by the thread that owns it; the OnStop is called on a different thread to the OnStop. It’s like changing the channel and then giving the remote away.
Some other method will have to be found to tell the other components to stop.
Previously on my UDPCatcher Service I did not experience this scenario, this new service loads up another app domain. Best we look at the whole problem again.
Update: Paul has removed the mutex code and using thread.Suspend and thread.Resume.
The title of this entry has given me a thought "Manages Service Mutex" the Mutex Service, the caller will make a connection to the service and do an async read, the async read complete could mean the mutex is now in your ownership. Ship a little class lib and start the service and bang you have a Mutex that is bound to a tcpip connection, I think this can be handed around.
Subscribe to:
Posts (Atom)
Tags
