Leading on from the previous blog post on reducing code noise when checking for null parameters, these help functions can be utilised to further reduce code noise that generally occurs in class constructors. Most constructors are purely made up of the following duplicated checking/assignment code.
public class MyClass { private readonly object var1; private readonly object var1; public MyClass(object arg1, object arg2) { if (arg1 == null) { throw new ArgumentNullException("arg1"); } if (arg2 == null) { throw new ArgumentNullException("arg2"); } this.var1 = arg1; this.var2 = arg2; }
Again putting together a small helper function, making use of the previous Throw class can remove 90% of the previous argument checking/assignment code resulting in:
public class MyClass { private readonly object var1; private readonly object var1; public MyClass(object arg1, object arg2) { this.var1 = ReturnParameter.OrThrowIfNull(arg1, "arg1"); this.var2 = ReturnParameter.OrThrowIfNull(arg2, "arg2"); }
Get the code from GitHub.
As part of his fantastic ‘What is .NET standard‘ presentation at DDD12, Adam Ralph provided an amazing amount of detail in such a short amount of time. One of the most valuable points, which is completely obvious when you think about it, is how you should work with .NET standard when creating libraries. NET standard now comes in a multitude of flavours: currently 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6 and 2.0. When starting out . . .
If you’re trying to access a class library (.NET Standard) from a traditional console application (in VS2017 those can be found under ‘Windows Classic Desktop’) you will run into problems; which can feel a little strange for something that was pretty simple in VS2015 and earlier. You can add a reference to the class library project (Resharper will even volunteer to add the dependency / namespace reference if you don’t already have it). But the . . .