From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
11-28-2006 03:00 AM
11-28-2006 03:30 AM
11-28-2006 03:54 AM
11-28-2006 04:04 AM
@dcharlot wrote:
Is the application itself the assembly?
11-28-2006 10:46 AM
I think the easiest solution is to create the C# code as a "C# Class Library" - you should see that as an option in Visual Studio when you go to create the project type. This doesn't create an application (.EXE), but a library (.DLL) kind of assembly. The term assembly is simply the name for the binary packaging of .NET code...it's actually a bit more than that, but it'll get you started 🙂
You then create the actually EXE application with LabVIEW, using the front panels to create your user interface. Then, rather than trying to get a mouse action in LV to become a mouse action in .NET (non-trivial in the extreme), you simply call the .NET code from LabVIEW.
If you go to examples\comm\dotnet\Calculator.llb, you'll get a good understanding of what I'm saying. It's a trivial example, but the calculator functions (add, subtract, etc) are written in C# and then compiled into a class library assembly (calculator.dll). The calculator UI is created in LabVIEW, and when you click the buttons, it calls down to .NET via the constructor/invoke/property nodes...
Let me know what questions you have after looking at that.