JKI Discussion Forums
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Bug? Build Scripts not working in LabVIEW 2011

#1
User is offline   jgcode 

  • Group: Members
  • Posts: 131
  • Joined: 14-January 09
VIPM 2011.0.1 (build 1692)

Steps to reproduce the bug (if it can be reproduced)
Create a package in VIPM using LabVIEW 2011
Add a Pre and Post build hook and configure to return information

Expected behavior (what would happen if the bug didn't exist)
When the package is build, information is available in each script (through variant attributes)

Attached Image: 2009 - Pre.png
Attached Image: 2009 - Post.png

Actual, observed behavior (the bug)
No information available in either build script as variant input is not updated

Attached Image: 2011 - Pre.png
Attached Image: 2011 - Post.png

Attached File  Test Hook.zip (21.28K)
Number of downloads: 30
[Code is in LabVIEW 2009]

If I run this in LabVIEW 2009 it works fine, but when I run it in LabVIEW 2011 it doesn't work.
This is on the same PC (Windows 7 x64) so it must be related to a change in LabVIEW 2011?

Attached is the code used in the above report (Build Hooks aren't excluded in build spec but doesn't matter).
This issue would not affect un/install scripts as they have no data passed to them.

Cheers
-JG

This post has been edited by jgcode: 18 January 2012 - 07:12 PM

0 kudos

#2
User is offline   jgcode 

  • Group: Members
  • Posts: 131
  • Joined: 14-January 09
Is there any workaround to get the data into the hook?

Cheers
-JG
0 kudos

#3
User is offline   Ashish 

  • Group: JKI Team
  • Posts: 26
  • Joined: 31-July 06
  • Gender:Male
JG,

Thanks for sharing your observations. It does help to improve our product quality.

I was able to reproduce the behavior and filed Case 13110 for us at JKI to manage the issue for future VIPM release.

Feel free to share any additional information related to this issue.

Thank you.
Ashish Uttarwar
Product Support Engineer and Certified LabVIEW Developer, JKI
0 kudos

#4
User is offline   jgcode 

  • Group: Members
  • Posts: 131
  • Joined: 14-January 09

View PostAshish, on 24 January 2012 - 05:57 PM, said:

JG,

Thanks for sharing your observations. It does help to improve our product quality.

I was able to reproduce the behavior and filed Case 13110 for us at JKI to manage the issue for future VIPM release.

Feel free to share any additional information related to this issue.

Thank you.


Thanks Ashish - do you have a workaround to get access to the data?

Cheers
-JG
0 kudos

#5
User is offline   Ashish 

  • Group: JKI Team
  • Posts: 26
  • Joined: 31-July 06
  • Gender:Male
JG,

Regarding workaround, are you asking to get access to the data displayed in the dialogs (as shown in your screenshots) after successful build?
Ashish Uttarwar
Product Support Engineer and Certified LabVIEW Developer, JKI
0 kudos

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic