Difference between AddNats and AddNatsClient

[moojek]

Hi,
as in the title, I would like to know what are the differences between those two extension methods that register DI services, or rather which should I use, since from code they are rather similar (although I did not dig that much).

[mtmk]

hi @moojek thanks, good question. they come from different packages.

AddNatsClient (NATS.Extensions.Microsoft.DependencyInjection) is the one to use for most apps. It enables ad-hoc JSON serialization and registers the basic INatsClient as well as INatsConnection. I suggest this one if you don't have AOT requirement for example.

AddNats (NATS.Client.Hosting) is the minimal-dependency, AOT-friendly option. It does not register the ad hoc JSON serializer nor INatsClient. If you are keeping your dependencies very tight and/or using AOT deployments, this one is to use. it might be less user friendly is some ways.

I'll review and update the documentation (I think we did for the 3.x series but I shall double check)

[moojek]

Hi,
thanks for answer, it makes it more clear for sure.

As for the topic of documentation, I use this: https://nats-io.github.io/nats.net/documentation/intro.html?tabs=core-nats. Is it the current one? Can I find something about this topic there or you mean it will be added in some upcoming release?

[mtmk]

there is a section written in release/3.0 branch. unfortunately you can only get to it through the release PR #1070. here is the direct link https://6a4632fe623fe137e730679d--teal-klepon-7e92d0.netlify.app/documentation/advanced/dependency-injection.html

edit document improvements are here #1210. 3.0 stable will be released soon, so the main docs should get an update too.