This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
This document contains the <product> <version> known issues that were discovered before and since the release of <product> <version>. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
The following are known issues in NI-RFSG .NET Class Libraries 1.2.0
Uninstalling NI-RFSG .NET Class Libraries does not uninstall the NI-RFSG .NET Class Libraries Help from Visual Studio.
Upgrading NI-RFSG .NET Class Libraries does not upgrade the NI-RFSG .NET Class Libraries Help in Visual Studio.
The NI-RFSG examples may produce a warning - "Warning: Found conflicts between different versions of the same dependent assembly". You can safely ignore this warning. This has been explained in following KnowledgeBase article.
The installer displays the message 'Installing Help', and installs help for the dependencies, even if you did not select Documentation during driver installation.
The installer displays message 'Integrating Help into Visual Studio' even if Visual Studio is not installed on your computer.
When you click the links in the NI-RFSG Instrument Driver Programming Flow topic from the NI-RFSG .NET 4.0 Help, a script error dialog box appears. Click No to view the help. This error occurs if you access any topic under NI-RFSG LabVIEW Reference from this window.
This installer includes version 1.4 of NationalInstruments.ModularInstruments.Common.dll, which is not compatible with earlier versions. This incompatibility can cause compile or run time errors in some circumstances when you use types from NationalInstruments.ModularInstrument.Common.dll directly in your program. Refer to the following Knowledge Base article for more information.