Jump to content

JamesW

Members
  • Posts

    6
  • Joined

  • Last visited

  • Days Won

    1

JamesW last won the day on December 3 2020

JamesW had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

JamesW's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Week One Done
  • One Month Later
  • Conversation Starter Rare

Recent Badges

1

Reputation

  1. Hi Jim, This is the proof of concept, I'm running it on my project as we setup our new CI system. The VIPC is created using scan project for packages. I'm creating the tool that will go in the project (hopefully the idea is to run it either on check-in or local compile to build the VIPC) Then the tool that I've created to run on the CI server will install the packages in the VIPC. As both can be run from CMD line, they can be used to setup a new developer machine / switch a project and package set between LabVIEW versions quickly as well as used with the CI. (If there was a way to list all of the packages on installed a machine then I would also consider cleaning all of the packages out between projects/builds to prevent bloating using the uninstall packages by name function.) Cheers James
  2. Hi Jim, I think issue#1 is affecting issue#2 on compiling the Exe and running as admin, The popup doesn't stay, it's only when the Scan project.vi is run from a function that is launched without Admin permissions that is doesn't close! (If the VI is run without Admin permissions, UAC is required to allow it to launch - and then user interaction is seemingly required to close the dialog, hence my longwinded SendInput function to work around it) - I've been experimenting with CMD line inputs to the LabVIEW EXE today Cheers James
  3. Hi Jim, Thanks for getting back, I think your summary is a good description of what I'm trying to achieve. The resolution for issue #1 sounds good as I believe it is the registry update service that is causing me issues with UAC. for issue #2 it is the dialog titled "VIPM - Project Dependency Scan Results " (note the extra space on the end - I think that's a typo) that appears after running. If I run Scan Project with Synchronous = TRUE, the VI just hangs... If I run is with Synchronous = FALSE, the VI scans and completes but I can't kill the window. (I've set a timeout of 60secs and it's easily long enough) (Actually - I have finally found a way of killing the window, but it's horrible and took me ages, with Windows SendInput function to dismiss it, and I must run the calling application as admin due to issue#1 to get the Inputchar feed through) - I'd much rather it worked properly without having to hack. It's taken me too long to get the API 'working' and I've too many hacks to be happy that my Proof of concept is going to be reliable with JKI updates! - it was a long weekend) Cheers James
  4. Anyone got any idea how to use API to automate: 1) Launching the API without UAC issues on a win 10 PC (get a consistent requirement for elevated priviledges with VIPM - probably due to the Registry update service that is launched and IT aren't happy to make this an exclusion. 2) scanning project to create a VIPC file (if the service is already running) - can scan successfully, but "Scan Project.vi" hangs in synchronous mode for me, and in a-synchronous mode there is a dialog generated to show completion (which I can detect) but can't seem to dismiss. Using the SendKey_8.2_llb, I can find the window, but can't close the window as the application doesn't have focus. Silent mode is not respected (a bug). Tech support request has been open for nearly 2 months, but not updated since 4th Dec. Other people must be using VIPM in a CI context, I can't be the first to try this on 64bit LabVIEW surely? (Goal is to scan a project, create a VIPC file based on packages used by project, & reverse the process, so unpack a VIPC file within a project and install packages before building a project) Any suggestions of hacks to get around the JKI API not working are appreciated. Cheers James
  5. hi @Jim Kring, I've updated to the latest version, and my manager purchased a Professional License for me yesterday evening... but this is still not working. I see that the update has locked out the BD of the VIs - so I guess that was an oversight in your last package release. I can't see anything useful now for debugging now, all I'm getting is a hang. What is wrong with my attempt please? (I'm trying to use the API to populate (and create) a VIPC file based on a project name and I looks like it should be easy.) Unless it's something to do with the service keep crashing? so I can't restart every time I close it. I have to go to taskmanager and kill all VIPM things in order to be able to launch the packager manager from the shortcut again? Cheers James VIPM test - Questions.vi
  6. I believe that VIPM could be very useful for modular code control - from what I have been reading... It's currently 3pm GMT and I've spent the afternoon trying to get the API working (in the eval mode). I can't generate / read / apply a VIPC file - which is basically what I want to do - from there integration with Jenkins should be easy. I seem to always either get dialog popups everywhere or else hang on the "VIPM API_vipm_api.lvlib:Poll for VIPM Action Complete_vipm.api.vi" - just hangs with nothing going on. Have 2015, 2018 and 2020 LabVIEW installed, all 64bit, running VIPM with the 2018 version - need a solution for a meeting in the next hour for a team meeting if I am to sell this to the team edit: meeting ran over - have another week to get this working (or 12days evaluation)
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.