LabVIEW 2011 Bug: Builder does not tell you why it was unsuccessful

[RobCole]

This isn't a question so much as a warning about a builder bug.

When building an executable, I specified a custom configuration file:

When I build the application, what I got from the builder was:

No information at all about why the build failed.

I did get a successful build - AFTER I closed the editor (notepad) that I had the .ini file open in.

The builder should tell us why it failed. I think it's a bug.

     Rob

[mudson]

Robert,

Thanks for the heads up.  I'll check around to see if anyone else has reported similar behavior.

[NIquist]

---

@mudson wrote:

I did a little digging.

This specific issue is not listed among the fixes in LabVIEW 2012.

I'll look into getting it included in SP1 but it doesn't sound like a showstopper - so it may be a little while before this particular malfunction is addressed.

---

Expecting any IDE to identify and report every possible configuration error a human can make in such a complicated system is rather unrealistic IMHO.  This should not be considered a "bug" since it can never be fully "fixed".  I agree that it would be nice if it could do better though.  At least NI could make the Builder admit that it can't figure out what's wrong by outputting an 'Unknown Error" message rather than leaving the explanation blank.

[RobCole]

Thank you. It was, however, pointed out to me that this thread also points out this problem and possible fixes. So this is not a unique problem - although other had different reasons for the same issue. None of the listed fixes there were relevant to my problem.

Rob

[gmart]

In these cases, what is helpful is the exact steps that resulted in the problem. I tried to reproduce what you said (having the ini file open in an editor - notepad) and could not get the error. The build succeeded.

[RavensFan]

Is it possible it wasn't Notepad but some other editor?

Notepad doesn't tend to lock files.  But if another editor did lock the file, then I can see how an error would be caused when the builder tries to access the file.

[RobCole]

I can reproduce the error using these steps:

The .ini file is already in the destination directory.

I opened the .ini file (from the destination directory) with Notepad++.

When I tell LabVIEW to build, the blank error is what I get.

If the .exe is open / running I get an access violation error. But not if the .ini file is open.

     Rob

[RavensFan]

Notepad++ is not the same thing as Notepad.  So perhaps my theory of file locking is coming into play.

If you open the file in Notepad++ and then try to open it somewhere else (Notepad, another Notepad++, MS Word, a file open function in LabVIEW), do you get an error?

[RobCole]

Okay, I did that quickly since I was busy in the project at the time. However, if I open the file in Notepad (as opposed to Notepad++), I get the same problem. I just started my computer, so there is nothing else open. Well... okay... Firefox is open so I can read the forums. But Firefox has never caused problems before.

Rob