-
April 2nd, 2007, 05:14 PM
#1
Gracefully disconnect standalone .NET adapters
Is there a way to gracefully disconnect standalone .NET adapters when a LS server is stopped or fails?
We developed a standard alone .NET adapter to connect to LS and everything works as expected. The problem comes in when the LS server process has to stop (or fails), it terminates the .NET adapter process as well. It is as if the DotNetAdapter_N2.dll calls Environment.Exit() (or End statement in VB) when a remoting error occurs, resulting in the entire process being terminated.
Some background: The standalone .NET component we are developing retrieves states, pushes data and has other functionality that services not just to LS but to other components as well. Therefore if DotNetAdapter_N2.dll terminates the entire process upon remoting failure we can not use it within our process.
Similar Threads
-
By sebandres in forum Client SDKs
Replies: 1
Last Post: May 4th, 2011, 09:26 AM
-
By LS_Developer in forum Adapter SDKs
Replies: 2
Last Post: April 19th, 2011, 11:03 AM
-
By sjohn in forum Adapter SDKs
Replies: 7
Last Post: February 18th, 2008, 08:50 AM
-
By wattsw in forum Adapter SDKs
Replies: 2
Last Post: November 13th, 2006, 05:12 PM
-
By cvs_fif in forum Adapter SDKs
Replies: 8
Last Post: September 25th, 2006, 02:36 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 06:41 PM.
Bookmarks