C＃.NET中的DDE [英] DDE in C#.NET

问题描述

我知道.NET语言不再支持DDE。是否有第三方库

将此添加回来？我有几个应用程序，我将被要求通过DDE与仪器控制应用程序通信的
端口。

坚持迁移到C＃的无能的管理员我们不明白我们

不能强迫仪器软件以任何其他方式进行通信。他们的回答是，你不能只是点网吗？

解决方案

我是不确定你的经理是多么无能为力，因为他们不想听到他们不想要的话。您是否尝试使用过时一词？


尽管如此[叹气]您可以试试这个：

http://www.vsnetfr.com/lien.aspx?ID=5161


这里还有一个有用的帖子，以及到另一个图书馆的链接：

http：/ /trout.snt.utwente.nl/ubbthrea...b=5&o=&fpart=1

我在Google大约两分钟内发现这一切顺便说一句。


--BOB


" stolikmc" < ST ****** @ discussions.microsoft.com>在消息中写道

news：66 ********************************** @ microsof t.com ...

我知道.NET语言不再支持DDE。是否有第三方库？
将此添加回来？我有几个应用程序，我会被要求通过DDE移植到与仪器控制应用程序通信的C＃。
坚持迁移到C＃的无能的管理员不理解
我们不能强迫仪器软件以任何其他方式进行通信。
他们的回答是，你不能只是Dot Net吗？

" stolikmc" < ST ****** @ discussions.microsoft.com>在消息中写道

news：66 ********************************** @ microsof t.com ...

我知道.NET语言不再支持DDE。是否有第三方图书馆
将此添加回来？

试试这个：
http://www.gotdotnet.com/Community/U。 ..4-2ed516b75181

它对我有用，不幸的是我让它只在控制台上运行

应用程序

就我而言，
DDE仍被股票报价软件使用

等，这就是为什么MSFT不再对我感兴趣的原因。

这个协议


RGDS PSG

Bob，


感谢您的回复。经理们不喜欢听到不这个词。

已过时

也没有用它们来削减它。在任何情况下，问题都在于

工具

制造商，他们永远不会更新，直到市场停止购买他们的过时

废话。大多数人仍然在GWBasic中为他们基于串行的

工具提供示例代码......

这带来了.NET的另一个弱点;至少对于工业实力

开发！我猜.NET的确是针对B2B和webby的东西。不适合我们

齿轮头工厂自动化人员只想要一个RAD环境工作

in。


你''再说吧，我应该使用搜索引擎。告诉我

老式的，先去专家而不是interNUTS; ^）

============== =

" Bob Grommes"写道：

我不确定你的经理是多么无能为力，因为他们不想听到他们不想要的东西。您是否尝试使用过时一词？

然而[叹气]您可以尝试这样做：

http://www.vsnetfr.com/lien.aspx?ID=5161

那里这里也是一个有用的帖子，以及另一个图书馆的链接：

http://trout.snt.utwente.nl /ubbthrea...b=5&o=&fpart=1

顺便说一句，我在大约两分钟内发现了这一切。
--BOB

stolikmc < ST ****** @ discussions.microsoft.com>在消息中写道
新闻：66 ********************************** @ microsof t.com。 ..

我知道.NET语言不再支持DDE。是否有第三方库？
将此添加回来？我有几个应用程序，我将被要求通过DDE移植到与仪器控制应用程序通信的C＃。
坚持迁移到C＃的无能的管理员不明白

我们

不能强迫仪器软件以任何其他方式进行通信。

他们的

回答，可以你只是点网吗？

I know .NET languages no longer support DDE. Is there a 3rd party library
that adds this back in? I have several applications that I''ll be asked to
port to C# that communicate with instrument control applications thru DDE.
The clueless managers that insist on migrating to C# don''t understand that we
can''t force the instrumentation software to communicate any other way. Their
answer, "Can''t you just Dot Net it?"

解决方案

I''m not sure your managers are clueless so much as they don''t want to hear
what they don''t want to. Have you tried using the word "obsolete"?

Nevertheless [sigh] you can try this:

http://www.vsnetfr.com/lien.aspx?ID=5161

There is also a useful post here, along with a link to another library:

http://trout.snt.utwente.nl/ubbthrea...b=5&o=&fpart=1

I found this all in about two minutes with Google, by the way.

--Bob

"stolikmc" <st******@discussions.microsoft.com> wrote in message
news:66**********************************@microsof t.com...

I know .NET languages no longer support DDE. Is there a 3rd party library
that adds this back in? I have several applications that I''ll be asked to
port to C# that communicate with instrument control applications thru DDE.
The clueless managers that insist on migrating to C# don''t understand that we can''t force the instrumentation software to communicate any other way. Their answer, "Can''t you just Dot Net it?"

"stolikmc" <st******@discussions.microsoft.com> wrote in message
news:66**********************************@microsof t.com...

I know .NET languages no longer support DDE. Is there a 3rd party library
that adds this back in?

try this one:
http://www.gotdotnet.com/Community/U...4-2ed516b75181
it works for me, unfortunatelly I''ve made it run only in console
applications

as far as I''m concerned DDE is still being used by stock quotes software
etc., that''s why it is a pity for me that MSFT is no longer interested in
this protocol

RGDS PSG

Bob,

Thanks for your reply. Managers just don''t like to hear the word "No".
Obsolete
doesn''t cut it with them either. In any case the problem lies with the
instrument
manufacturers who never update until the market stops buying their out of date
crap. Most still give example code in GWBasic for their serial based
instruments...
which brings us to another weakness in .NET; at least for industrial strength
development! I guess .NET''s really aimed at B2B and webby stuff. Not for us
gear-head Plant Automation guys who just want a RAD environment to work
in.

You''re right, I should have though of using a search engine. Sue me for being
old-fashioned and going to the experts instead of the interNUTS first ;^)
===============
"Bob Grommes" wrote:

I''m not sure your managers are clueless so much as they don''t want to hear
what they don''t want to. Have you tried using the word "obsolete"?

Nevertheless [sigh] you can try this:

http://www.vsnetfr.com/lien.aspx?ID=5161

There is also a useful post here, along with a link to another library:

http://trout.snt.utwente.nl/ubbthrea...b=5&o=&fpart=1

I found this all in about two minutes with Google, by the way.

--Bob

"stolikmc" <st******@discussions.microsoft.com> wrote in message
news:66**********************************@microsof t.com...

I know .NET languages no longer support DDE. Is there a 3rd party library
that adds this back in? I have several applications that I''ll be asked to
port to C# that communicate with instrument control applications thru DDE.
The clueless managers that insist on migrating to C# don''t understand that

we

can''t force the instrumentation software to communicate any other way.

Their

answer, "Can''t you just Dot Net it?"

这篇关于C＃.NET中的DDE的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！