blocks|key|1519111|text|在过去的几年里，我看到并编写了相当多的C#+/+Excel+COM+Interop代码，我几乎在所有情况下都看到使用工作表。我从来没有见过微软在这个问题上有任何明确的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1519112|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have seen and written quite a bit of C# / Excel COM Interop code over the last few years and I've seen Worksheet used in almost every case. I have never seen anything definitive from Microsoft on the subject.

blocks|key|1519199|text|MSDN显示Worksheet接口只是从_Worksheet和DocEvents_Event接口继承而来。似乎只需提供工作表对象可能引发的事件，而不是其他任何事件。据我所知，Worksheet没有提供自己的任何其他成员。所以，你最好在所有情况下都使用Worksheet接口，因为你不会因为它而失去任何东西，并且可能需要它公开的事件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1519200|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel.worksheet(office.11).aspx|1|http://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel._worksheet(office.11).aspx|2|http://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel.docevents_event(office.11).aspx^0|6|9|K|A|V|F|2F|9|3H|9|6|9|0|K|A|1|V|F|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@$9|12|A|13|1|14]|$9|15|A|16|1|17]|$9|18|A|19|1|1A]]|E|$]]|$1|F|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]|N|$5|I|J|K|E|$L|O]]|P|$5|I|J|K|E|$L|Q]]]]

MSDN shows that the <a href="http://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel.worksheet(office.11).aspx" rel="noreferrer"><code>Worksheet</code></a> interface simply inherits from the <a href="http://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel._worksheet(office.11).aspx" rel="noreferrer"><code>_Worksheet</code></a> and <a href="http://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel.docevents_event(office.11).aspx" rel="noreferrer"><code>DocEvents_Event</code></a> interfaces. It would seem that one simply provides the events that a worksheet object might raise in additional to everything else. As far as I can see, <code>Worksheet</code> doesn't provide any other members of its own. So yeah, you might as well just go with using the <code>Worksheet</code> interface in all cases, since you don't lose anything by it, and potentially might need the events it exposes.

blocks|key|1519265|text|如果您查看Reflector中的PIA程序集(Microsoft.Office.Interop.Excel)，Workbook接口具有以下定义...|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1519266|public+interface+Workbook+:+_Workbook,+WorkbookEvents_Event|code-block|syntax|javascript|1519267|Workbook为_Workbook，但添加了事件。Worksheet也是如此(对不起，我只是注意到你说的不是Workbooks)……|1519268|public+interface+Worksheet+:+_Worksheet,+DocEvents_Event|1519269|DocEvents_Event+...|1519270|[ComVisible(false),+TypeLibType((short)+0x10),+ComEventInterface(typeof(DocEvents),
+++++++++++++++++++++typeof(DocEvents_EventProvider))]
public+interface+DocEvents_Event
{
++++//+Events
++++event+DocEvents_ActivateEventHandler+Activate;
++++event+DocEvents_BeforeDoubleClickEventHandler+BeforeDoubleClick;
++++event+DocEvents_BeforeRightClickEventHandler+BeforeRightClick;
++++event+DocEvents_CalculateEventHandler+Calculate;
++++event+DocEvents_ChangeEventHandler+Change;
++++event+DocEvents_DeactivateEventHandler+Deactivate;
++++event+DocEvents_FollowHyperlinkEventHandler+FollowHyperlink;
++++event+DocEvents_PivotTableUpdateEventHandler+PivotTableUpdate;
++++event+DocEvents_SelectionChangeEventHandler+SelectionChange;
}|1519271|我会说最好使用Worksheet，但这就是不同之处。|1519272|entityMap|0|LINK|mutability|MUTABLE|url|http://www.red-gate.com/products/reflector/^0|5|9|1J|8|5|9|0|0|0|0|8|9|9|Q|9|1J|9|0|0|0|F|0|0|7|9|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|F|3|G|5|H|7|1A|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1B|8|@$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|1K|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1O|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

If you look at the PIA assembly (Microsoft.Office.Interop.Excel) in <a href="http://www.red-gate.com/products/reflector/" rel="noreferrer"><code>Reflector</code></a>, the <code>Workbook</code> interface has this definition ...

<pre><code>public interface Workbook : _Workbook, WorkbookEvents_Event
</code></pre>

<code>Workbook</code> is <code>_Workbook</code> but adds events. Same for <code>Worksheet</code> (sorry, just noticed you were not talking about <code>Workbooks</code>) ...

<pre><code>public interface Worksheet : _Worksheet, DocEvents_Event
</code></pre>

<code>DocEvents_Event</code> ...

<pre><code>[ComVisible(false), TypeLibType((short) 0x10), ComEventInterface(typeof(DocEvents),
 typeof(DocEvents_EventProvider))]
public interface DocEvents_Event
{
 // Events
 event DocEvents_ActivateEventHandler Activate;
 event DocEvents_BeforeDoubleClickEventHandler BeforeDoubleClick;
 event DocEvents_BeforeRightClickEventHandler BeforeRightClick;
 event DocEvents_CalculateEventHandler Calculate;
 event DocEvents_ChangeEventHandler Change;
 event DocEvents_DeactivateEventHandler Deactivate;
 event DocEvents_FollowHyperlinkEventHandler FollowHyperlink;
 event DocEvents_PivotTableUpdateEventHandler PivotTableUpdate;
 event DocEvents_SelectionChangeEventHandler SelectionChange;
}
</code></pre>

I would say it's best bet to use <code>Worksheet</code>, but that's the difference.

blocks|key|1304327|text|如果我没记错的话--我的记忆有点模糊，自从我拆开Excel+PIA已经有很长一段时间了--是这样的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1304328|事件本质上是对象在发生某些事情时调用的方法。在.NET中，事件是简单明了的委托。但在COM中，将一大堆事件回调组织到接口中是很常见的。因此，在给定对象上有两个接口--“传入”接口，即您希望其他人调用您的方法，以及“传出”接口，当事件发生时，您希望调用其他人调用的方法。|1304329|在可创建对象的非托管元数据(类型库)中，有三种定义:传入接口、传出接口和coclass，coclass表示“我是一个实现传入接口和传出接口的可创建对象”。|1304330|现在，当类型库自动转换为元数据时，这些关系将被保留下来。如果有一个手工生成的PIA，让类和接口更符合我们在托管世界中的期望，那会更好，但遗憾的是，这并没有发生。因此，Office+PIA充满了这些看似奇怪的重复，其中每个可创建的对象似乎都有两个与其关联的接口，在它们上面有相同的东西。其中一个接口表示coclass的接口，另一个接口表示该coclass的传入接口。|1304331|_Workbook接口是工作簿coclass上的传入接口。工作簿接口是表示coclass本身的接口，因此继承自_Workbook。|1304332|长话短说，如果您可以方便地使用工作簿，我会使用工作簿；_Workbook是一个实现细节。|1304333|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

If I recall correctly -- and my memory on this is a bit fuzzy, it has been a long time since I took the Excel PIA apart -- it's like this.

An event is essentially a method that an object calls when something happens. In .NET, events are delegates, plain and simple. But in COM, it is very common to organize a whole bunch of event callbacks into interfaces. You therefore have two interfaces on a given object -- the "incoming" interface, the methods you expect other people to call on you, and the "outgoing" interface, the methods you expect to call on other people when events happen.

In the unmanaged metadata -- the type library -- for a creatable object there are definitions for three things: the incoming interface, the outgoing interface, and the coclass, which says "I'm a creatable object that implements this incoming interface and this outgoing interface".

Now when the type library is automatically translated into metadata, those relationships are, sadly, preserved. It would have been nicer to have a hand-generated PIA that made the classes and interfaces conform more to what we'd expect in the managed world, but sadly, that didn't happen. Therefore the Office PIA is full of these seemingly odd duplications, where every creatable object seems to have two interfaces associated with it, with the same stuff on them. One of the interfaces represents the interface to the coclass, and one of them represents the incoming interface to that coclass.

The _Workbook interface is the incoming interface on the workbook coclass. The Workbook interface is the interface which represents the coclass itself, and therefore inherits from _Workbook.

Long story short, I would use Workbook if you can do so conveniently; _Workbook is a bit of an implementation detail.

I'm currently writing about dynamic typing, and I'm giving an example of Excel interop. I've hardly done any Office interop before, and it shows. The <a href="http://msdn.microsoft.com/en-us/library/dd264733(VS.100).aspx" rel="noreferrer">MSDN Office Interop tutorial</a> for C# 4 uses the <code>_Worksheet</code> interface, but there's also a <code>Worksheet</code> interface. I've no idea what the difference is.

In my absurdly simple demo app (shown below) either works fine - but if best practice dictates one or the other, I'd rather use it appropriately.

<pre><code>using System;
using System.Linq;
using Excel = Microsoft.Office.Interop.Excel;

class DynamicExcel
{
 static void Main()
 {
 var app = new Excel.Application { Visible = true };
 app.Workbooks.Add();

 // Can use Excel._Worksheet instead here. Which is better?
 Excel.Worksheet workSheet = app.ActiveSheet;

 Excel.Range start = workSheet.Cells[1, 1];
 Excel.Range end = workSheet.Cells[1, 20];
 workSheet.get_Range(start, end).Value2 = Enumerable.Range(1, 20)
 .ToArray();
 }
}
</code></pre>

I'm trying to avoid doing a full deep-dive into COM or Office interoperability, just highlighting the new features of C# 4 - but I don't want to do anything really, really dumb.

(There may be something really, really dumb in the code above as well, in which case please let me know. Using separate start/end cells instead of just "A1:T1" is deliberate - it's easier to see that it's genuinely a range of 20 cells. Anything else is probably accidental.)

So, should I use <code>_Worksheet</code> or <code>Worksheet</code>, and why?

Excel interop: _Worksheet or Worksheet?

我目前正在写一篇关于动态类型的文章，我给出了一个Excel互操作的例子。我以前几乎没有做过任何Office互操作，它显示了。C# 4的使用_Worksheet接口，但也有一个Worksheet接口。我不知道有什么不同。在我的简单得离谱的演示应用程序中(如下所示)，要么工作得很好--但如果最佳实践规定了其中之一，我宁愿适...

问Excel互操作：_Worksheet还是Worksheet？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Excel互操作：_Worksheet还是Worksheet？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Excel互操作：_Worksheet还是Worksheet？
EN