How to

A collection of 70 posts

How to , Software tools , Open Source

Enable LabVIEW Dialogs

Have you ever had issues with Windows file dialogs not appearing when they should in LabVIEW? If so, check out this tool.

SCC , Software tools , How to , Continuous Integration , DevOps

Git Tip: Find All Changed Files

One way to speed VI Analyzer or Blue is to only run it on changed files. Here is a way to do that.

Software tools , Unit Testing , How to

Approvals New Features - Date Scrubber and Custom DiffTool

Have you tried out Approval Testing yet? if no, why not? It's a great way to tame Legacy Code.

Unit Testing , Software Engineering , Legacy Code , Resources , Software tools , How to

Approval Testing For LabVIEW 2.0 Released

If you haven't tried approval testing yet, you definitely should. It makes unit testing a lot easier, particularly for legacy code or for verifying complicated objects.

Continuous Integration , How to

More on GitLab Custom Executors

If you are trouble visualizing how GitLab Custom Executors Work, here is a diagram that might help.

Continuous Integration , How to

Spawning VMs like Docker Containers

I've figured out how to use the KVM Executor for GitLab to spawn VMs similar to Docker Containers. It works quite well as an alternative.

How to , DevOps

Compressing KVM Disks for Win10 VMs

If you are using VMs at all, it makes sense to compress them to save disk space. Here's how to do it for KVM with Win10 guests.

How to

SSH Server on Windows 10

Did you know you can run SSH server on a Windows machine and SSH into it?

How to , Software tools

Publishing AntiDoc Documentation using GitLab Pages

I just discovered GitLab Pages recently. It has been around for a while, so this may not be news to anyone, but I'm sure it's news to at least one of my readers and I've found a somewhat novel use case for it, so I decided to do a blog post about it.

Continuous Integration , Software tools , DevOps , SCC , How to

Git SubModules and GitLab CI

I generally prefer using VIPM to share code, but sometimes submodules are useful. However, using them with GitLab CI can be tricky.

How to , Software Engineering , Software tools , SCC

The Absolute Easiest Way to Setup LVCompare and LVMerge

Setting LVCompare and LVMerge is as easy as copying a few lines of code and running them in Git Bash.

Python , How to

Using Python Classes In LabVIEW

Now in LabVIEW 2022 Q3 you can use Python objects with the Python Node. Find out how.

Python , SCC , How to

Using Git Hooks

Git Hooks can be quite useful for a variety of things. Here is a simple example to make sure you don't forget to include an issue # in your commit message.

How to , SCC

Latest Version of Git Broke LVCompare Usage

The latest Git update broke my LVCompare setup. Here's how I fixed it and how you can too.

How to , Continuous Integration , Software tools , Webinars

Build License Track

Matthias from Studio Bods, recently presented at our Mastermind Group on his tool that allows you to Build, License, and Track (BLT) your LabVIEW programs.

Continuous Integration , How to

More GitLab Runner Troubleshooting Tips

I’ve been writing a lot lately about Continuous Integration and using GitLab Runner. It’s really nice when it works and it works 90% of the time, but issues do pop up occasionally. They can be a pain to troubleshoot. I previously wrote about how to run GitLabRunner as

Continuous Integration , How to , SCC

Checking for New GitLab Releases

In my previous posts, I talked about automatic versioning and automatically creating releases. The next step is to create auto-updating code. By auto-updating I don’t mean code that automatically updates behind your user’s back ala Windows 10. You can do that if you want, but I believe the

Continuous Integration , How to , SCC

Automating Gitlab Releases

My previous post talked about versioning. I thought I would add to that discussion by talking about how I do releases and how I setup auto-updating in my apps, using the GitLab Package Repository. This a new feature I’ve started adding lately, so it’s still a work in

Continuous Integration , How to , SCC

Automatic Versioning

At the GLA Summit recently minted LabVIEW Champion Felipe Pinheiro Silva gave a 7×7 on versioning. It was interesting. Be sure to take a few minutes and watch it when the video is released. I do things slightly differently. I learned my method from another LabVIEW Champion, Stefan Lemmens.

Unit Testing , How to , Coding Philosophy

How I use Test-Driven Development (TDD)

A lot of people out there are very dogmatic about Test Driven Development. There’s a lot rules and a lot of very strong opinions. If you don’t believe me, go check out Twitter. While on Twitter, I saw GeePaw Hill’s Ten I statements about TDD. It inspired

Continuous Integration , How to

Trouble Shooting GitLabCI

I saw a post recently on LinkedIn by Jim Kring. He had some issues with a build hanging unexpectedly. They were running Jenkins under a system account and therefore it was really hard to see what was going on to be able to troubleshoot it. Jim then linked to a

Unit Testing , How to

A case for sets

Back in LabVIEW 2019, NI introduced both sets and maps. Maps became immediately popular. They should be. They are very useful constructs. However, sets seem to have gotten much less attention. In some ways, they aren’t as glamorous, but they do offer some advantages over arrays. To me, these

SCC , How to , Software tools

A Better Way To Set Up LVCompare and LVMerge

EDIT: Since I originally wrote this post, I have come up with a much easier way. I am leaving this post up for historcial reasons, but do yourself a favor and just go here I have previously written about setting up LVCompare and LVMerge. I ran into a situation where

How to , Continuous Integration , Legacy Code

Quick VI Analyzer

I haven’t talked a whole lot about VI Analyzer yet. It’s a static code analysis tool. If you come from text-based background, it is similar to a linter. It checks your code against a set of predefined rules and reports back any violations. You do need LabVIEW professional

Continuous Integration , How to

GitLab CI and Git Bash

A while back GitLab CI deprecated the batch executor for Windows runners. That meant that you could no longer directly call batch scripts from a Gitlab Runner. They had switched over to Powershell. There were workarounds. You could still write a batch script and call it from PowerShell using cmd.