`SetPort` throws when called before `Initialize`

[caguiclajmg]

VTSWebSocket.SetPort (and consequently CoreVTSPlugin.SetPort) throws when called before calling Initialize, presumably due to _logger being unset here at the time of the SetPort call:

VTS-Sharp/VTS/Core/VTSWebSocket.cs

Lines 165 to 166 in e97f68d

	public bool SetPort(int port) {
	_logger.Log(string.Format("Setting port: {0}...", port));

This makes it impossible to pre-select the VTS instance you'd want to connect to. As a workaround, theoretically (haven't tried it yet) I should be able to do: Initialize -> SetPort -> Disconnect -> Initialize but that's super clunky.

PS: Is there any specific reason why some of the internals are lazily initialized (e.g. in Initialize instead of a constructor)?

[FomTarro]

Good catch. That's very funny, I'll try to fix that when I have time.

These classes are all lazily initialized because they started life 4+ years ago as Unity components, which do not support constructors. I then worked backwards to try to make them more engine agnostic, without breaking any existing patterns. I could probably add a constructor to the Core class, though.

Sorry for the inconvenience, please feel free to submit a pull request with a proposed fix if you have time!

[caguiclajmg]

These classes are all lazily initialized because they started life 4+ years ago as Unity components, which do not support constructors. I then worked backwards to try to make them more engine agnostic, without breaking any existing patterns. I could probably add a constructor to the Core class, though.

Ah I see, that makes perfect sense; I guess I am the minority here consuming from plain .NET.

feel free to submit a pull request with a proposed fix if you have time!

I'd be happy to contribute, I'm hacking one together right now. Thanks for the inputs!