Mass compile hangs on Calculator.vi

[joeljkp]

I just installed LabVIEW 7.1, then updated to 7.1.1. When I mass compiled my LabVIEW 7.1 directory, it hangs on:

C:\Program Files\National Instruments\LabVIEW 7.1\examples\comm\dotnet\Calculator.llb\Calculator.vi

I can let it work for half an hour with CPU at 100%, and still nothing. To quit, I need to manually kill it. The log file is empty.

[THailey3]

Hi Joel,

I haven't heard of a mass compile "hanging" before. Although, I can say that the last time I mass compiled my 7.1 directory, it took about 2 hours to complete (maybe only an hour, but a while nonetheless). Do you have another computer around you that you could test this on? It's possible that something just went wrong in the installation. Give this a try and let me know what happens.

Take care,

[Bob_Y.]

One thing you could do, since you know the problem vi, is to open it and save it. Then it will not need to be recompiled.

Another thing to do is to mass compile in smaller masses. Just do one smaller directory at a time.

I hope that this helps,
Bob

[joeljkp]

Yes, I've tried opening the problem vi and re-saving it, but LabVIEW seems to hang simply opening it. Perhaps there's something inside that VI that's conflicting with something in the rest of my system?

[tst]

You could try moving that VI (or llb) to another directory, which isn't being compiled, and then move it back after the compiling is done (assuming it will be done).

[Roy_F]

The calculator example constructs an instance of a .Net assembly called calculator. I suspect the problem has to do with that assembly (or any .Net assembly on your computer perhaps?). Does this ring any bells?

[joeljkp]

The only thing I can think of is that I have .NET 2.0 Beta on my system (alongside 1.1). Perhaps that's what's causing it.

[Lycangeek]

Ah, yes. The .NET 2.0 beta and LV 7.x do not get along in many cases. It isn't the mass compile as much as the LV .NET integration code and the 2.0 beta that are having trouble.

Just to verify that this is the problem, try creating a blank VI then dropping a .NET Constructor node onto the diagram. If your system locks up with 100% CPU, you're going to need to avoid the LV .NET integration or uninstall the 2.0 beta.

[joeljkp]

Great, thank you for that answer.

[joeljkp]

Yeah, as a followup to this message, I uninstalled my .NET Framework 2.0 Beta and now my Mass Compile is going smoothly. Thanks all.