更好的SVG旋转文本渲染(Better SVG rotated text rendering)

 不，您不应该为此目的抛出ArgumentNullException ，因为它专为解决null引用而设计。 
 
 
 
 当空引用（在Visual Basic中为Nothing）传递给不接受它作为有效参数的方法时引发的异常。 
 
 
 相反，你应该使用ArgumentException或你自己的子类。 让我们说InvalidUserException或类似的东西。 
 
 即使是msdn谈论 。 
 
 
 
 ArgumentNullException的行为与ArgumentException相同。 它提供的应用程序代码可以区分由空参数引起的异常和由非空参数引起的异常。 对于由非空参数引起的错误 
 
 
 所以很显然，如果argument为null ，则使用ArgumentNullException和ArgumentException 。 
 
 也就是说，理想情况下，您甚至不应允许某人使用无效的用户名创建User实例。 我真的设计我的User类，它永远不会包含Name为null 。 

No you shouldn't throw ArgumentNullException for this purpose as it is designed specifically to address null references. 
 
 
 
The exception that is thrown when a null reference (Nothing in Visual Basic) is passed to a method that does not accept it as a valid argument.
 
 
Instead you should be using ArgumentException or your own subclass of it. let's say InvalidUserException or something similar.
 
Even msdn talks about.
 
 
 
ArgumentNullException behaves identically to ArgumentException. It is provided so that application code can differentiate between exceptions caused by null arguments and exceptions caused by arguments that are not null. For errors caused by arguments that are not null
 
 
So it is clear that if argument is null use ArgumentNullException and ArgumentException otherwise.
 
That said, Ideally you shouldn't even allow someone to create an instance of User with invalid username. I'd really design my User class in such a way that it can never contain Name as null.