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.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

.NET callback win7/win10

We have a .NET library (our own development). It uses callback functions.
We use LabVIEW 16 (32).
I configured the callback function as "open the window when called."
Under win10 everything works correctly, when the event occurs, the function window opens. If you compile exe, it also works even under Win7.
But when developing a program under Win7, the callback does not work, the function window does not open. And after compilation in the exe, too, nothing passes.
What could be the reason?

0 Kudos
Message 1 of 7
(2,918 Views)

I'm guessing what you are trying to do is:

  • Have a Callback VI attached to an event on one of the classes in your assembly. The Callback VI will be executed by the calling thread inside the assembly.
  • You want the Callback VI to show its Front Panel when the callback event occurs

Perhaps you could post an example clarifying your intent and showing the problem?

0 Kudos
Message 2 of 7
(2,882 Views)

Thanks for answer.

I set callback vi for "open when calling" only for test.
The problem is "assembly" doesn't work when we develop/compile under win7. But the same project successfully work under win10. Furthermore, after compilation standalone application works under win10 and win7.

I can't attach the code, here only simple example.

 

This is event registration

 

event.png

 

And this called subvi

subvi.png

 

 

 

0 Kudos
Message 3 of 7
(2,876 Views)

 I have got a similar scenario to work just fine under Win7. If you can't attach some code that we can actually play with to see the defect then we are going to have difficulty in providing you any help other than wild theories.

 

Perhaps you could list all the LabVIEW, OS and CLR/.NET versions and bitness you are using and have installed as a starting point. So our wild theories have some basis to work with.

0 Kudos
Message 4 of 7
(2,864 Views)

I understand that the code would have greatly simplified the task, but I can not apply it for reasons of secrecy.

Here is the list of installed software. In the attached file, full lists.

 

win7 64 / LV2016 32
short list

Awesomium SDK 1.7.5.1
Firebird 2.5.2.26540 (Win32) 2.5.2.26540
Microsoft .NET Framework 4 Multi-Targeting Pack 4.0.30319
NI .NET Framework 4.6 4.61.49152
NI Assistant Framework 16.0.24
NI LabVIEW 2016 16.0.180
NI LabVIEW 2016 (32-bit) 16.0.191
NI LabVIEW 2016 (32-bit) 16.0.192
NI LabVIEW 2016 (32-bit) 16.0.193
NI LabVIEW 2016 Compare Utility 16.0.179
NI LabVIEW 2016 Database Connectivity Toolkit 16.0.143
NI LabVIEW 2016 Database Connectivity Toolkit License 16.0.147
NI LabVIEW 2016 Deployable License 16.0.179
NI LabVIEW 2016 Deployment Framework 16.0.181
NI LabVIEW 2016 Help 16.0.178
NI LabVIEW 2016 Help File 16.0.178
NI LabVIEW 2016 License 16.0.180
NI LabVIEW 2016 Manuals 16.0.178
NI LabVIEW 2016 MeasAppChm File 16.0.178
NI LabVIEW 2016 Merge Utility 16.0.179
NI LabVIEW 2016 Real-Time NBFifo 16.0.182
NI LabVIEW 2016 Report Generation Toolkit License 16.0.126
NI LabVIEW 2016 Report Generation Toolkit for Microsoft Office 16.0.123
NI LabVIEW 2016 Run-Time Engine Web Server 16.0.163
NI LabVIEW 2016 Scripting Code Generator 16.0.114
NI LabVIEW 2016 Search 16.0.4
NI LabVIEW 2016 Simulation 16.0.179
NI LabVIEW 2016 Web Server 16.0.165

 

 

 

win10 64 / LV2016 32

short list

Awesomium SDK 1.
Entity Framework Designer для Visual Studio 2012 - RUS 11
Entity Framework Tools for Visual Studio 2013 12
LabVIEW 2016 Installation Patch 16
Microsoft .NET Framework 4 Multi-Targeting Pack 4.
Microsoft .NET Framework 4.5 Multi-Targeting Pack 4.
Microsoft .NET Framework 4.5 SDK 4.
Microsoft .NET Framework 4.5 SDK - русский языковой пакет 4.
Microsoft .NET Framework 4.5.1 Multi-Targeting Pack 4.
Microsoft .NET Framework 4.5.1 RC Multi-Targeting Pack for Windows Store Apps 4.
Microsoft .NET Framework 4.5.1 SDK 4.
Microsoft Advertising SDK for Windows 8.1 - ENU 8.
NI .NET Framework 4.6.2 4.
NI LabVIEW 2016 (32-bit) 16
NI LabVIEW 2016 Compare Utility 16
NI LabVIEW 2016 Database Connectivity Toolkit 16
NI LabVIEW 2016 Database Connectivity Toolkit License 16
NI LabVIEW 2016 Deployable License 16
NI LabVIEW 2016 Deployment Framework 16
NI LabVIEW 2016 Help 16
NI LabVIEW 2016 Help File 16
NI LabVIEW 2016 License 16
NI LabVIEW 2016 Manuals 16
NI LabVIEW 2016 MeasAppChm File 16
NI LabVIEW 2016 Merge Utility 16
NI LabVIEW 2016 Real-Time NBFifo 16
NI LabVIEW 2016 Report Generation Toolkit License 16
NI LabVIEW 2016 Report Generation Toolkit for Microsoft Office 16
NI LabVIEW 2016 Run-Time Engine Web Server 16
NI LabVIEW 2016 Scripting Code Generator 16
NI LabVIEW 2016 Search 16
NI LabVIEW 2016 Simulation 16
NI LabVIEW 2016 Unit Test Framework Toolkit 16
NI LabVIEW 2016 Unit Test Framework Toolkit License Files 16
NI LabVIEW 2016 Web Server 16
NI LabVIEW 2016 f2 16

 

 

Download All
0 Kudos
Message 5 of 7
(2,851 Views)

Nothing stands out. What version of Win10 are you running (build)?

 

If you can't create a reproducible case (with a non-secret version of your assembly or otherwise) then it might be difficult to get to the root of the issue.

0 Kudos
Message 6 of 7
(2,842 Views)

win10 

ver 1803

build 17134.48

0 Kudos
Message 7 of 7
(2,836 Views)