C＃是否可以连接到现有的labview应用程序 [英] Is it possible for C# to connect to existing labview application

问题描述

我们有一个由第三方在Labview设计的应用程序。这个Labview应用程序的格式类似于我们填写信息的表格，是一个独立的程序。



运行时是否有可能让c＃连接到程序并读取输入表格的数据？



谢谢



我有什么尝试过：



我查了谷歌但没有找到任何有用的东西

解决方案

< blockquote>

Quote：

C＃是否可以连接到现有的labview应用程序

如果您没有向承包商询问该功能，为了以防万一，他没有机会做一些他没有得到报酬的工作。如果你问，这意味着你没有这样的文件。



如果需要改变很小，你可以尝试：

- 如果你能联系承包商或那家伙怎么做的工作;幸运的是，您可以恢复源代码，其中一个可能仍然有维护旧应用程序的活动。如果他们中的一个维护旧应用程序，他也可以升级到更新的版本。

- 否则，我担心你将不得不从头开始。



建议：

- 将来要求输入源代码。

- 对于非常重要的定制软件，最好组织一下这样一个事实：有人维护一个平台，可用于纠正错误或根据需要引入更改。这种服务可以设置为每年一小笔费用。当你消耗调试并进行更改时，你会付出更多。



我仍​​然使用CA-Clipper（FoxPro的堂兄）维护一套25年的应用程序。客户很高兴应用程序仍然符合其需求，并在我寻求帮助时做出回应。我得到一些额外的收入。

请看我对这个问题的评论。我刚做了一些搜索并找到了一些建议。作为与LabView相关的一切，它们非常脏。我发现一些链接比其他更有趣和相关：

集成LabVIEW和C＃1 - Erdos Miller [ ^ ]，

从其他编程语言调用LabVIEW VI - National Instruments [ ^ ]。



我建议继续我的搜索，因为你有比我更多的关于你的情况和项目的信息。



但我的主要建议是：尝试如果可以的话，尽可能地摆脱 LabView 。这不仅仅是我的意见。几年前，当我发表一篇关于反对LabView的实验物理技术的作品时，我成了LabView的强烈反对者。在那个时候，直到现代，我总是遇到同意我的人;有些人甚至说他们讨厌它，甚至一些经常使用它的人。大约20年前（实际上是晚些时候），该公司通过硬件支持制作了一个狡猾的肮脏技巧并通过许多用户创建了强大的供应商锁定。硬件供应商紧随其后，其中一家主要供应商NI成为LabView的所有者。为了NI的荣誉，我必须说他们总是提供替代方案。

参见：

LabVIEW - 维基百科，免费的百科全书 [ ^ ]，

供应商锁定 - 维基百科，免费的百科全书 [ ^ ]。

-SA

We have a application designed in Labview by a third party. This Labview application is format like a Form for us to fill info in and is a stand alone program.

Is it possible to have c# connect to the program when it runs and read the data that is input into the form?

Thanks

What I have tried:

I've looked up google but didn't find anything usefull

解决方案

Quote:

Is it possible for C# to connect to existing labview application

If you didn't ask the contractor for the feature, there is little chances that he did some work he was not paid for, just in case. If you ask, it means you don't have such documentation.

If needed changes are small, you can try to:
- If you can contact the contractor or the guy how did the job; With some luck you can recover source code and one of them may still have an activity of maintaining old apps. If one of them maintain old apps, he may also be able to upgrade to newer version.
- Otherwise, I fear you will have to start again from scratch.

Advice:
- in future, ask for source code.
- For very important customized software, it a good idea to organize the fact that someone maintain a platform that can be used to correct bugs or introduce changes as needed. this kind of service can be set for a yearly small fee. And you pay more as you consume the debugging and make changes.

I still maintain a set of 25 years old apps made with CA-Clipper (a cousin of FoxPro). The customer is happy that the apps still fit its needs and that I respond when he calls for help. and I get some extra income.

Please see my comment to the question. I've just made some search and found some suggestions. As everything related to LabView, they are pretty dirty. I found a couple of links more interesting and relevant than other:
Integrating LabVIEW and C# 1 — Erdos Miller[^],
Calling LabVIEW VIs from Other Programming Languages — National Instruments[^].

I would advise to continue my search, because you have a lot more information on your situation and project than I do.

But my major advice would be: try to get rid of LabView by all means, if you can. This is not just my opinion. I became a strong opponent of LabView years ago, when I published one of my first works on experimental physics technologies opposing LabView. At that time and up to the modern time I always meet people who agree with me; some even say they hate it, even some those who often use it. Some 20 years ago (actually later), the company made a cunning dirty trick and created strong vendor lock-in with many users, through the hardware support. Hardware vendors followed, and one of the major vendors, NI, became the owner of LabView. For the honor of NI I must say they always offer the alternatives.
See also:
LabVIEW — Wikipedia, the free encyclopedia[^],
Vendor lock-in — Wikipedia, the free encyclopedia[^].

—SA

这篇关于C＃是否可以连接到现有的labview应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！