Describe the bug
LabVIEW searches for a mnu file when dropping a VI from the NPIO lib on a block diagram : controls_benjaminr_custom_controls.mnu

To Reproduce
Steps to reproduce the behavior:

1. install the package
2. Drop a NPIO VI on an empty block diagram

Expected behavior
No missing dependency

Screenshots

Environment (please complete the following information):

• Win10 x64
• LabVIEW Version 2017
• LabVIEW Bitness 32bit
• Runtime? No

Additional context
None

Describe the bug
I just build a very simple VI to build an executable and I've seen two issues related to build

1. If I do not uncheck Remove unused members of project libraries in Additional Exclusions, the executable cannot find the class coerrsponding to the file format (MS-Excel.lvclass for *.xlsx or *.xls, MS-Word for *.docx or *.doc). This lead to an error 7.
2. With this option unchecked, I get an error 1172. It seems that the direct dependencies are copied into data fodler, in build destination folder (NPOI.dll, NPOI.OOXML.dll), but three dependant assembly are missing (ICSharpCode.SharpZipLib.dll, NPOI.OpenXml4Net.dll, NPOI.OpenXmlFormats.dll)

To Reproduce
Steps to reproduce the behavior:

1. Open the attached project, review Main.vi (I inserted the code snippet found on the project home page on a blank VI, replaced the path control by a File Dialog, and add an Simple Error Handler after Close Document)
   Build Dependencies Issues.zip
2. Build My Application : it only point to Main.vi. Run the generated executable : you should get an error 7
3. Build My Application (fix 1). In Additional Exclusion, Remove unused members of project libraries was unchecked. Run the generated executable: you should get an error 1172
4. Build My application (fix 1 + fix 2). The three missing DLL (ICSharpCode.SharpZipLib.dll, NPOI.OpenXml4Net.dll, NPOI.OpenXmlFormats.dll) are explicitly referenced in the project, in order to force their copy into data forlder. The generated executable should run just fine.

Expected behavior
Getting a working build without build spec "trick"

Screenshots

Environment

• Target: Win 10
• LabVIEW Version 2017
• LabVIEW Bitness 32-bit
• Runtime? Yes

Additional context
Issues first encountered when building a PPL with LabVIEW 2020, reproduced with a simple example project under LabVIEW 2017.

Describe the bug
Hi,Benji.
I found that if I open an existing excel file, save it and close it, and then use excel to open the file, I will get an error.


If I change mode from createoropen to create, there will be no errors. The same thing happens in C#

alike

To Reproduce
Open an existing xlsx file for saving

Environment (please complete the following information):

• Target: [Win 10.]
• LabVIEW Version [2020]
• LabVIEW Bitness [ 32-bit]