11-15-2011 11:16 PM
From the .NET palette, I chose the constructor node and put it on the diagram. A dialog should pop up and show me all the assembly available, but it doesn't. i was able to get the dialog to pop up eventually, but there is no assemblies in the dialog. Why is that?
Solved! Go to Solution.
11-16-2011 08:06 AM
@jyang72211 wrote:
A dialog should pop up and show me all the assembly available, but it doesn't.
Doesn't what? Your question is confusing. The dialog that appears only shows the assemblies that are installed in the GAC. For private assemblies you have to click on the Browse button and locate your assembly.
11-16-2011 08:11 AM - edited 11-16-2011 08:14 AM
Hi.
If I get you right, this dialog does not appear when you put a .NET Constructor in the block diagramm:
Did I understood well? If so it does not look like an expected behavious. Could you tell which version of LabVIEW and which operating system you are using?
As workaround, you can double click on the constructor to open this dialog.
Regards
11-16-2011 08:34 AM
Sorry, I should have attached a picture. Please see attached. I was able to get the dialog to come up, but there is nothing in there.
11-16-2011 08:38 AM
Oh, I understand better now.
Did it use to work on the computer before? It looks to me like the framework is not installed. Is it? Have u tried deinstalling and reinstalling the current .NET framework?
Regards
11-16-2011 08:43 AM
A simpler question: do you actually have .NET installed?
11-16-2011 08:50 AM
I have another question for you: Do you have an assembly from Cognex installed on your computer (particulary Cognex.DataMan.SDK)?
11-16-2011 10:58 AM
What is Cognex? I have attached a picture of all the .NET components installed on my computer. I am using LabVIEW 2011.
11-16-2011 10:59 AM
I think it did work, but I am not sure. I did uninstall and install the .NET again, but for a different purpose.
11-17-2011 03:48 AM
Cognex is a library one of our custommer installed and which caused the same problem. Calling a method from this assembly once fixed this problem. That is why I was asking you if by any chance you installed it too which could have been the cause of this.