Setting multi-lines URLS for STAN servers

[DeployChef]

For example, I setted:
Options.NatsURL = "nats: //127.0.0.1: 4222, nats: //127.0.0.1: 4223, nats: //127.0.0.1: 4224";
It is not a valid value because the connection string is not parsed when you called stan connection factory.
When a factory is called from STAN, the Nats factory method is called where there is no call to opts.processUrlString (url);
Thus, the string is not parsed.

This leads to the fact that it is impossible to connect to a set of servers

[ColinSullivan1]

@DeployChef , Thank you for raising this issue.

This was an issue but has been resolved, see nats-io/stan.net#125. We haven't cut a release with the fix yet, but I'll look into doing so soon.

In the meantime, you can setup a core NATS connection, and then pass it to the STAN client. This is what will be required later if you want to enable TLS.

An example of creating a core NATS connection and passing it into STAN can be found here: https://github.com/nats-io/stan.net#enabling-tls

Note that you don't necessarily need to setup TLS. This is how the code might look:

        static IConnection createNATSConnection()
        {
            // get the default NATS options
            var natsOptions = ConnectionFactory.GetDefaultOptions();
            natsOptions.Url = "nats://127.0.0.1:4222, nats://127.0.0.1:4223, nats://127.0.0.1:4224"

            return new ConnectionFactory().CreateConnection(natsOptions);
        }

        static void Main(string[] args)
        {
            // Get default STAN options, then create and assign a
            // core NATS connection for the streaming client to use.
            var stanOptions = StanOptions.GetDefaultOptions();
            stanOptions.NatsConn = createNATSConnection();

            // Finally create a STAN logical connection using the
            // NATS connection we just created.
            var connection = new StanConnectionFactory().CreateConnection("test-cluster", "test-client-001", stanOptions);
        }

[ColinSullivan1]

I'm closing this issue; feel free to re-open if you continue to have issues.