最小起订量-Setup()v Setup<>()

本文介绍了最小起订量-Setup()v Setup<>()的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我有一个这样的模拟物:

I have a mock being created like this:

var mock = new Mock<IPacket>(MockBehavior.Strict);
mock.Setup(p => p.GetBytes()).Returns(new byte[] { }).Verifiable();

Setup方法的智能提示是这样的:

The intellisense for the Setup method says this:

但是模拟的方法p.GetBytes()不会返回void，而是返回一个字节数组.

But the mocked method p.GetBytes() does not return void, it returns a byte array.

或者，将另一种Setup方法定义为Setup<>，我可以这样创建模拟程序:

Alternatively another Setup method is defined as Setup<>, and I can create my mock like this:

var mock = new Mock<IPacket>(MockBehavior.Strict);
mock.Setup<byte[]>(p => p.GetBytes()).Returns(new byte[] { }).Verifiable();

此Setup方法的智能提示:

The intellisense of this Setup method states:

.
.
无论选择哪种方法，它都可以编译并测试确定.因此，我对应该采用哪种方式感到困惑. .Setup()和.Setup<>()有什么区别，我做对了吗?

.
.
Whichever method I choose, it compiles and tests OK. So, I'm confused as to which way I should be doing this. What is the difference between .Setup() and .Setup<>(), and am I doing it right?

我们应该说缺少Moq的文档. :)

The docs for Moq are somewhat lacking, shall we say. :)

setup