Sorry I forgot to add that other core features involve background threads such as incoming connection handling (if listening), connection keep alives, and incoming packet thread pool etc. Looking at the source I don’t think it’s possible to get away without calling Shutdown() for version 2.3.1.
I do like the idea of under the majority of circumstances NetworkComms.Net, particularly if not listening, can shutdown without needing to call Shutdown though.
We are currently working heavily to get a Beta out of the next release and probably won’t get a chance to look at this before then but I will add a post to the feature request forum as a reminder.
Marc