Application Builder error in building .exe with .NET

[DWendelboe]

I have an application that is almost complete. It runs great under the Labview environment, but when I try to make an .exe file to move the application to the manufacturing floor I get a build error.
My application uses some .NET functions which ultimately reference System.Messaging in the <GAC> (C:\Windows\assembly\ on my machine). THe application seems to compile OK, but then it attempts to copy the System.Messaging assembly from the <GAC> into the application build set. Application Builder balks and gives the build error shown in the picture below. The second attached picture shows that the System.Messaging assembly is in fact present in the <GAC>.

Should the application be trying to copy this file anyways? Isn't System.Messaging in the <GAC> considered a system resource which must be installed seperately (in my case by the IT department who wrote the .NET interface).

[pacific]

Hi DWendelboe,

I think you are getting that error becuase of file permissions and the use of absolute paths.

The following thread has a similar problem discussed:
http://forums.ni.com/ni/board/message?board.id=170&message.id=237061&requireLogin=False

But I cannot say for certain if that is the reason. Can you post your code?

[DWendelboe]

Thanks for responding Prashant. I've attached the code in Project form (.lvproj).

[CarlaU]

Hi DWendelboe,

Are you using LabVIEW 8.5? If so, I belive that there has been a Corrective Action Request reported on this issue (CAR ID#71651 or 4E485CF2). There is another forum post that I found that deals with a very similar issue to this one. I do know that this issue was fixed in LabVIEW 8.5.1. You can see that it is listed on the known bug fixes from the LabVIEW 8.5.1 readme. I hope this helps!

[DWendelboe]

Thanks for your input. I am using LabVIEW v8.5.1

I performed a radical test on this problem. I removed EVERYTHING from the VI. So there absolutely nothing in it. I then did a "Save All", and then a "Build".
The same error occurred. With nothing in the VI ??? The problem must be in the Project itself. There is no code left. Wow!

Tomorrow I will try to rebuild this VI and project from a clean project and VI.

[CarlaU]

Hi DWendelboe,

I agree with you that the error seems to be due to the actual project files. I would also suggest that you try to build a new project and start with just a blank VI and see if it builds successfully. If so, try adding a simplified version of your project files (in a new VI) and try that. Keep increasing it slowly until it either all builds or you get to the point where the build is unsucessful. Let us know if this works!