Sign Up

EU Cyber Resilience Act (CRA) — First Deadline September 2026

If you sell LabVIEW-based software and systems in the EU, please be aware that new CRA regulations may require you to implement security vulnerability reporting starting September 11, 2026. The VIPM Team has prepared guides to help you understand how this applies to your software applications and published packages, since it's important you understand these regulatory requirements (click the Learn More link to read these guides). Thank you for your help in keeping security front-and-center within the LabVIEW community.

Learn more

Try out the new Jake: AI Coding Assistant for LabVIEW!
Get answers to questions about LabVIEW and discuss your code.

Developer Assistant by Felipe Pinheiro Silva - Toolkit for LabVIEW Download

A tool to provide instant feedback on your code while editing or even fixing it for you.

Discussion Watch

1

130

screenshot

Version	2.0.2.5
Released	Oct 17, 2025
Publisher	Felipe Pinheiro Silva
License	MIT
LabVIEW Version	LabVIEW>=20.0
Operating System	Windows
Dependencies	jdp_science_jsontext felipefoz_lib_lv_rainbow_terminal felipefoz_lib_dev_hooks
Project links	Homepage Discussion

Description

NO MORE keyboard shortcuts muscle memory. NO MORE Ctrl+Space + Ctrl+F, Ctrl+Space + Ctrl+something.

NO MORE too late failed VI Analyzer ("...now it is too late to fix that, I will create an issue and fix next time...").

NO MORE technical debt due to code quality issues hanging in the story board.

FIX your code WHILE you are EDITING with the DEVELOPER ASSISTANT and its hooks.

Instead of outsourcing your work to be verified by CI (Continuous Integration) or your colleague, be sure your code is compliant, already during edit time.

The solution is the Developer Assistant, a daemon running alongside your LabVIEW project that monitors the whole folder where the project is located. As soon your editing VI is saved, the assistant takes action, running your formatter or a quick scripting test.

From v2.0 it supports Git History for the current VI and running VI Analyzer Tests.

WARNING: Once you start using this tool, you may exhibit symptoms of addiction, as editing code will never be the same again.

NOTE: DISCLAIMER: this project does not make use of any type of Artificial Inteligence Technology, it is pure LabVIEW scripting.

More on the tool: https://gitlab.com/felipe_public/lv-dev-assistant

Release Notes

2.0.2.5 (Oct 17, 2025)

### Bug Fixes
- main: ignore errors when closing references from closed projects [#12]

felipefoz was a contributor to this release

2.0.1.4 (Sep 17, 2025)

### Performance Improvements

* fix some missing closed references

felipefoz was a contributor to this release

2.0.0.3 (Sep 16, 2025)

### BREAKING CHANGES
* adds support for reading new settigs from config
### Features
- adds free label with commit info to remote VI [#10]
- adds function to run hook filtered by trigger type
- adds initial git timeline support
- adds keyboard flush events and new optional hook args property
- adds keyboard monitor
- adds keyboard shorcut support and merged results
- adds new properties to hooks and validation
- adds possibility to launch LVCompare to the commit selected [#10]
- adds prototype for running unit test and keyboard inputs
- adds support for reading new settigs from config
- double clock shows window user extended commit information [#10]
- FileSystemWatcher: include filter and update fs watcher [#6]
- implement showing git file history in listbox [#10]
- main: adds button for starting getting started window

### Bug Fixes
- active-vi: mistake with unbundling the wrong path
- adds double quotes in paths calls in cmd lines git and lvcompare
- adds get vi name method instead of opening/closing ref [#7]
- adds support for private data control [#7]
- ase: moves to be an external dependency from vipm.io
- check if file or folder exist instead of path valid only [#8]
- dialog: updates message in the error dialog
- enforce check and error handling in active vi name [#8]
- git-timeline: do not check for relative path on not a path
- lv-compare: do not launch lvcompare if remote was deleted
- main: adds missing destroy event ref
- main: main vi was not reporting project path and git fail with external VIs
- opening reference for hooks in target app instance [#11]
- project discovery is from vi to instance now
- remove previous support for running ut, now from dev hooks [#4]
- sysexec: adds embedded error reading
- update show commit to disable btn when not supported [#10]
- utf8: show names in commit msg in utf8 format
- vi was failing due to receving empty vi file path [#4]

felipefoz was a contributor to this release

1.0.2.7 (Jan 04, 2025)

* checks validity of app refernce before using it #3
* makes user popup dialog to depend on the error dialog

felipefoz was a contributor to this release

1.0.1.6 (Jan 04, 2025)

* update error handling strategy
* validate event checks ref valid before getting path #3

felipefoz was a contributor to this release

1.0.0.5 (Jan 03, 2025)

[1.0.0]

- initial release

felipefoz was a contributor to this release

Show all release notes (+5 more releases)

Download Package

Versions

2.0.2.5 (Oct 17, 2025)

2.0.1.4 (Sep 17, 2025)

2.0.0.3 (Sep 16, 2025)

1.0.2.7 (Jan 04, 2025)

1.0.1.6 (Jan 04, 2025)

+ 1 more

Published by

All Contributors

Post an Idea Post a Resource

Recent Posts

Forum Posts