Build name conflicts (NI Report Generation Toolkit)

[Matthew_Kelton]

A new thread was created for Cyber's problem.  It can be found here.

[stonpc01]

So those of us still using the 8.6 version, we have to upgrade to 2009 to have the "build as LV8.X" option, or is there some update we can download?  My company just updated me from 8.0 to 8.6 (which I fought) and I'm having the same troubles here.  We don't use installers because of permission problems, so we just give out the .exe (but now we also have to give out hundreds of support VIs).  Any chance we can get the update without upgrading to 2009?  Thanks.

[Andrey_Dmitriev]

---

stonpc01 wrote:
So those of us still using the 8.6 version, we have to upgrade to 2009 to have the "build as LV8.X" option, or is there some update we can download?  My company just updated me from 8.0 to 8.6 (which I fought) and I'm having the same troubles here.  We don't use installers because of permission problems, so we just give out the .exe (but now we also have to give out hundreds of support VIs).  Any chance we can get the update without upgrading to 2009?  Thanks.

---

Unfortunately no chance.

In LabVIEW 2009 the method for storing SubVIs inside of executable was changed. Now its possible to save SubVIs with same name without conflict. As result in LabVIEW 2009 is possible to have single executable (mean single exe file) with Report Generation Toolkit. Already checked this  and it works (to be honest - I haven't perform full check for functionality yet, just build). Take a note that "build as LV8.x" option should be unchecked, otherwise you will get exactly the same trouble as with LabVIEW 8.6.

Andrey.

[stonpc01]

It is rediculous for NI to think we should pay for new software when we already bought their broken software.  8.0 had no problems with the exe and did not produce the extra VIs.  I know the extra VIs are produced in 8.6 because of classes, but they should update 8.6 with a hotfix of some sort to fix this issue.  Although they don't believe it is a big deal, why would we want our customer (whether internal or external) to have all those extra VIs with the exe???  It's silly for us to spend the extra money on 2009 when we just bought 8.6 not that long ago.  Argghh...guess I'll have to do the .dll thing 😞

[tst]

I think that every version of LabVIEW you can buy today comes with free upgrades for a year, so you might be able to get 2009.

Andrey, one thing to look out for is that every folder inside the EXE is considered as a real folder. That means, for instance, that if you want to strip until you reach the folder, the strip will end while still inside the EXE.

[Andrey_Dmitriev]

---

stonpc01 wrote:
It is rediculous for NI to think we should pay for new software when we already bought their broken software.  8.0 had no problems with the exe and did not produce the extra VIs.  I know the extra VIs are produced in 8.6 because of classes, but they should update 8.6 with a hotfix of some sort to fix this issue.  Although they don't believe it is a big deal, why would we want our customer (whether internal or external) to have all those extra VIs with the exe???  It's silly for us to spend the extra money on 2009 when we just bought 8.6 not that long ago.  Argghh...guess I'll have to do the .dll thing 😞

---

Theoretically you can install old Report Generation Toolkit (delivered with LabVIEW 8.0) also with LabVIEW 8.6. Some manual work may required (for manual transfer VIs and probably palettes from 8.0 to 8.6), but this should work. By the way, extra VIs caused by build conflict - its not bug, its "feature" (because Toolkit in general working properly)

Andrey. 

[jack1]

Hi TST

Just hit the same problem with version 8.6 being unable to build the Report files etc into exe file. For my developments this is really bad news. I have dropped back to version 8.51 and no problem, as others have suggested so will now be sticking with that.

On a side note I don't know what your subscription is to NI but I have been paying a wedge each year on top of the software purchase to cover me for quarterly fixes and telephone support.

Doubt if I will upgrade to 8.9 due to lack of work last year leading to my subscription lapsing and then when requesting renewal was quoted the year support fee plus half of full developer cost again. Shame really as the product is very good on the whole but experiance over the last few months makes me wonder and although commited to Labview due to my historic and future projects will be looking at alternative sources for hardware.

Arh well who cares as we say here in blighty,

[jonathanupr]

I am having the same issues with the build (as explained by the original poster on page1 of this thread). 

When building the executable, all of the following files get put into three distinct folders within the Build folder (NI_HTML, NI_Report, NI_Standard Report).

As stated, this doesn't occur in 8.5.

Is there a solution to this?

[Darren]

---

jonathanupr wrote:

I am having the same issues with the build (as explained by the original poster on page1 of this thread). 

When building the executable, all of the following files get put into three distinct folders within the Build folder (NI_HTML, NI_Report, NI_Standard Report).

As stated, this doesn't occur in 8.5.

Is there a solution to this?

---

There is no workaround in 8.6.  In 2009, you can deselect "Use 8.x file layout" in the Advanced page of your build settings to move all the contents in those folders into your EXE.

[jonathanupr]

I'm not too versed in how to fix the issues I'm seeing within the project folder under dependencies... see attached jpg.

Some files/libraries I could load and unlock,others seem plain stubborn though.

Any suggestions?

thanks