Return to Question

FINAL EDIT/SOLUTION

So after some thinking, this is now the final code for the Hazen class.. the abstract/base class TideDevice stays the same.

    internal Hazen(IRawDataReceiver rawDataReceiver) : base(rawDataReceiver)
    {
        _serialPortConnection = rawDataReceiver as SerialPortConnection;
    }
    [DataMember] private SerialPortConnection _serialPortConnection;

    [OnDeserialized] private void OnDeserialized(StreamingContext sc)
    {
        RawDataReceiver = _serialPortConnection;
    }

So as you can see, the [OnDeserialized] method will act as the constructor after deserialization. Or more specifically, it mimics the base(rawDataReceiver) part of "actual" `constructor'

That's it. Thanks @jeyoung and @JNS.

EDIT: I have extracted the Task to another method to remove the responsibility of the set accessor. But I'm still in a roadblock on fixing the code smell I initially stated. I editted the code to reflect what I have now.

EDIT2: This code is working really fine whether in unit test and integration test, so I'll leave it as is until someone points out that there is something wrong here or until a problem arises. Thank you very much!

EDIT: I have extracted the Task to another method to remove the responsibility of the set accessor. But I'm still in a roadblock on fixing the code smell I initially stated. I editted the code to reflect what I have now.

EDIT2: This code is working really fine whether in unit test and integration test, so I'll leave it as is until someone points out that there is something wrong here or until a problem arises. Thank you very much!

FINAL EDIT/SOLUTION

So after some thinking, this is now the final code for the Hazen class.. the abstract/base class TideDevice stays the same.

    internal Hazen(IRawDataReceiver rawDataReceiver) : base(rawDataReceiver)
    {
        _serialPortConnection = rawDataReceiver as SerialPortConnection;
    }
    [DataMember] private SerialPortConnection _serialPortConnection;

    [OnDeserialized] private void OnDeserialized(StreamingContext sc)
    {
        RawDataReceiver = _serialPortConnection;
    }

So as you can see, the [OnDeserialized] method will act as the constructor after deserialization. Or more specifically, it mimics the base(rawDataReceiver) part of "actual" `constructor'

That's it. Thanks @jeyoung and @JNS.

    internal Hazen(IRawDataReceiver rawDataReceiver) : base(rawDataReceiver)
    {
        SerialPortConnection = rawDataReceiver as SerialPortConnection;
    }
    private SerialPortConnection _serialPortConnection;
    [DataMember] private SerialPortConnection SerialPortConnection
    {
        get
        {
            return _serialPortConnection;
        }
        set
        {
            //TODO add null checker here
            _serialPortConnection = value;
            RawDataReceiver = value;
            Task.Factory.StartNew(async () => 
            {
                while (true)
                {
                    _serialPortConnection.Write("R");
                    await Task.Delay(Settings.SerialPortConnection.Default.WritingInterval);
                }
            }, TaskCreationOptions.LongRunning);
        }
    }

    internal Hazen(IRawDataReceiver rawDataReceiver) : base(rawDataReceiver)
    {
        SerialPortConnection = rawDataReceiver as SerialPortConnection;
    }
    private SerialPortConnection _serialPortConnection;
    [DataMember] private SerialPortConnection SerialPortConnection
    {
        get
        {
            return _serialPortConnection;
        }
        set
        {
            if(value != null)
            {
                _serialPortConnection = value;
                RawDataReceiver = value;
            }
        }
    }

EDIT: I have extracted the Task to another method to remove the responsibility of the set accessor. But I'm still in a roadblock on fixing the code smell I initially stated. I editted the code to reflect what I have now.

EDIT2: This code is working really fine whether in unit test and integration test, so I'll leave it as is until someone points out that there is something wrong here or until a problem arises. Thank you very much!