Home Community Idea Exchange LabWindows/CVI Ideas

LabWindows/CVI Idea Exchange

Community Browser
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Post an idea
0 Kudos
mjl

Allowing install on Pre Windows 10

Status: New Submitted by Member on 11-02-2022 08:04 AM 1 Comment

I develop software for many older systems that can not be upgraded or are running windows embedded.  I just tried to create a new application and could not install it from my distribution.  I found out I had to go and edit the setup.ini.  NI Installer Requires Windows 10 64-Bit (Version 1507) or Newer.  I've been using CVI since the DOS days.  One of the advantages has always been that I could recompile and I generally didn't have to worry about Windows updates screwing up my software.  This change seems ridiculous all of a sudden.

 

0 Kudos
RobertoBozzolo

Automate opening an existing project in the proper release of CVI

Status: New Submitted by Proven Zealot on 07-18-2016 05:39 AM 2 Comment

At present, when you double-click on a .cws or .prj file the most recent version of the CVI IDE is launched with the selected .prj or .cws file loaded.

However, both project and workspace files include the release of CVI they are developed on, so it would be possible to search in the system whether that release is installed and open it instead of the most recent one. This is crucial when you need to modify a program already deployed to a customer but do not want / is not possible to update the target machine configuration installing a newer Run-Time module than the one already installed.

At present you have no control over this event, but consider also that in case you make modifications to the UIR files also, it may become difficult to revert to the original IDE format; for this reason when I need to update an old program I need firstly to open the project file in notepad to see which CVI release to use for this.

 

If automating the launch in the correct release is not possible, at least issue a warning stating the difference in the IDE release used with respect to the original one.

0 Kudos
leonardojc

Support newer versions of C runtime on real-time systems

Status: New Submitted by Member on 04-06-2016 07:03 AM Comment

The most recent version of the C runtime that comes with the Phar Lap ETS is msvcr90 from 2008. That really restricts the usage of more recent third-party libraries on real-time targets shipping this operating system.

 

Support for msvcr{100,110,120,140}, even with stubs for most of their functions, would be greatly appreciated.

View All (3)
0 Kudos
j.romero

Add Current User directory in default folders for distribution interface

Status: New Submitted by Member on 07-25-2014 09:02 AM Comment

The following choices are availables:

[Program Files]
[Program Files (x86)]
[Desktop]
[Windows Volume]
[Windows]
[System]
[SysWOW64]
[System16]
[Program Data]
[Public Documents]
[Common Files]
[Common Files (x86)]
[Start»Programs]
[Start Menu]
[Startup]
[Temp]
[Favorites]
[Fonts]
[Templates]
[Send To]
[National Instruments]
[National Instruments (x86)]
[LabVIEW]
[CVI]
[CVI Shared]
[CVI Public Documents]
[IVI Std Root]
[VXI PnP]
[VXI PnP OS]

 

The User folder corresponding to CSIDL_PROFILE is not available. And no way to use it.

Labels:
0 Kudos
tstanley

Setting Active Distribution via ActiveX

Status: Under Consideration Submitted by Active Participant on 10-09-2013 04:05 PM 1 Comment

Hi,

 

It would be handy when automating the build process with the CVI ActiveX interface to have the ability to change the active distribution, as mentioned in this thread:

http://forums.ni.com/t5/LabWindows-CVI/Setting-active-distribution-kit-using-ActiveX/m-p/504888/highlight/true#M28708

 

Thanks.

Labels:
0 Kudos
Peter Cooper

Provide A Capability To Run A Batch File Or An Executable Automatica​lly After The Installati​on Been Completed From The CVI 2010 Distributi​on Kit

Status: Already Implemented Submitted by Member on 05-19-2011 02:27 PM 2 Comment

Have you ever wanted to run a customizable batch file or executable after a CVI Application has been deployed? In my case I do. In my case, I want to automatically run a batch file that sets the Environment Paths in Windows of my executables and DLL's after the installation is completed. To make this work currently I am requiring the person who is installing the application to manually run a batch file to set up the Environment Paths in Windows. Potentially error prone if the paths are not set for my applications. My batch file would be written as: "Set Path <etc> from the command line prompt. CVI 2010 does not have this capability.

 

In older versions of CVI I think this feature existed but I do not know which CVI version National Instruments removed it from.

 

There may be other cases that I might want to run an executable(s) that sets up the application up in a default situation for first time use only.

 

I am sure there are other cases where other CVI Developers who would want this capability too.

 

In TestStand this feature exists in the "TestStand Deployment Utility" under the Custom Commands tab.   

Labels:
View All (4)