Epicor 9 用C#做客户化时问题?

jesse1219

E9 中
Vb.net : Dim edv EpiDataView = Ctype(oTrans.EpiDataViews("orderhed"),EpiDataView) 没有问题
转换以C#
     EpiDataView edv = (EpiDataView) oTrans.EpiDataViews("orderhed")

时提示:picor.Mfg.UI.FrameWork.EpiTransaction.EpiDataViews”是“属性”，但此处被当做“方法”来使用

hjw100

之所以一直回避用E9 新提供的C#， 是因为它新的加入。  建议仍使用VB.NET

newluo

EpiDataView edv = (EpiDataView) oTrans.EpiDataViews("orderhed")
改成
EpiDataView edv = (EpiDataView) oTrans.EpiDataViews["orderhed"];

kirman

看到就有点头痛，我要加油

hjw100

Tommy  ：

做开发的，自行围观下面内容
Both C# and VB.NET compile to Common Intermediate Language so in theory, there might be a slight difference in the compiler optimization, but support's experience is that there isn't any descernable difference when one is used over the other.

However, Epicor recommends that all new UI Customizations use C# because if you are planning on deploying these customizations to Epicor Web Access (EWA), the UI Customizations would have to be in C# (VB.NET UI Customizations can't be deployed to EWA).