.NET Standard Adoption as of January 2017

Updated 2/16 to include Elasticsearch

As should be obviously from my recently blog posts, I have really been enjoying working with .NET Core. Clearly I am not alone, as a significant number of libraries have been porting over to the .NET Standard.

Below is a list libraries that have added support for the .NET Standard, meaning that they should be able to run cross platform on both Windows and Linux.

While I have not yet had the opportunity to try all of the libraries listed below, I have had great luck with the ones that I have tested, and I am simply ecstatic to see this list growing as fast as it is.

Technology	NuGet Package	.NET Standard Support
Autofac	Autofac	Released for 1.1
Cassandra	DataStax C# Driver for Apache Cassandra	Released for 1.5
Couchbase	Couchbase SDK 2.0	Beta for 1.5
Elasticsearch	Elasticsearch.Net	Released for 1.3
Kafka	Confluent.Kafka	Preview for 1.3
log4net	Apache log4net	Released for 1.3
MongoDB	MongoDB.Driver	Released for 1.4
NLog	NLog	Beta for 1.3
RabbitMQ	RabbitMQ.Client	Released for 1.5
RavenDB	RavenDB Client	Released for 1.3
Redis	StackExchange.Redis	Released for 1.5
Sqlite	Microsoft.EntityFrameworkCore.Sqlite	Released for 1.3
WebSocket Client	WebSocket4Net	Released for 1.3

How have these libraries been working out for you? Is there a better option than what I have listed? Please leave a comment and let me know!

Enjoy,
Tom

IOC Container for Tact.NET

Autofac now supports .NET Core, but other IOC frameworks such as Ninject and Unity have yet to port over. While I was looking into IOC frameworks for .NET Core, I had a bad idea...I, for fun, wrote my own Container in Tact.NET!

So, why did I do this? Honestly, it was just a fun academic exercise! I do think that this is a pretty good container, and I intend to use it in some of my personal projects. Would I recommend that YOU use this? Probably not yet, but I would invite you take a look and offer feedback!

Container Design

I have broken the container into two interfaces: IContainer for registration, and IResolver for consumption. There is a abstract class, ContainerBase, that can be inherited to easily create a container that matches other frameworks; for example, I intend to create a IDependencyResolver for ASP.NET.

You may notice that the IContainer does not have any lifetime management methods, that is because ALL of them are implemented as extension methods...

Registrations

To create a new lifetime manager you have to implement the IRegistration interface. There are already implementations for quite a few:

• InstanceRegistration
• PerResolveRegistration
• PerScopeRegistration
• SingletonRegistration
• TransientRegistration

Resolution Handlers

The last part of the container is the IResolutionHandler interface. These resolution handlers are used when an exact registration match is not found during dependency resolution. For example, the EnumerableResolutionHandler will use ResolveAll to get a collection of whatever type is being requested. Another very different example, the ThrowOnFailResolutionHandler will cause an exception to be thrown when no match can be found.

• EnumerableResolutionHandler
• FuncResolutionHandler
• LazyResolutionHandler
• ThrowOnFailResolutionHandler
• UnregisteredResolutionHandler

I think that is a pretty good start, but I am hoping that this will continue to grow with time.

Enjoy,
Tom

Can I port my application to .NET Core?

I am very excited about .NET Core, and I am looking forward to porting my projects to it. Generally porting your own code is a straight forward task, but updating all of your dependencies can be quite daunting. Good news: the guys over at Octopus have built an awesome little site that helps you determine the state of your dependencies!

I Can Has .NET Core

Enjoy,
Tom