Archived: Measurement Studio 2010 Bug Fixes

NI does not actively maintain this document.

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.

개요



The following items are changes from Measurement Studio 2009 to Measurement Studio 2010.

If you have a Bug ID, you can search this list to validate that the issue has been fixed.
ID Fixed Issue
154564 Measurement Studio ASP.NET Web Forms controls may throw an InvalidOperationException in Internet Information Services (IIS). If you access the page from more than one place, or if you refresh the page very frequently, you may see this InvalidOperationException.
180681 A memory leak exists in WebForms.NetworkVariableDataSource when Dispose is not called before the host page is unloaded.
190486 If you call Graph.ToImage(Size), the DrawGridLines method draws the graph axes incorrectly. If the destination size is not set to the same value as the graph image size, the axes do not scale correctly.
193763 Visual Studio Setup Projects for DataSocket applications do not automatically add the logos.msm merge module.
193809 If you deploy a network variable application to a machine that acts as the variable server, the machine may crash after you install the application. If you install your application after the NINETVARSERV redist installer, your application installer will stop the Shared Variable Engine service. If this service is not running, applications that use network variable may crash.
194621 If a graph includes multiple axes, ZoomXY may not zoom accurately. If a graph has multiple X or Y axes, the overload ZoomXY(referencePlot, xData, yData, width, height) zooms accurately for the axes associated with the plot that are referenced in the first parameter. However, the axes not associated with the given plot do not zoom accurately.
194685 TdmsFile.ConvertFileFormat may intermittently throw a TdmsException.
196747 Using a single network variable writer from multiple threads may cause your application to hang.
197154 Some applications on a target computer may report errors or terminate unexpectedly after installing a distribution that was created on a computer with Measurement Studio 2009 installed.
Refer to KnowledgeBase Article 53F9JDXU for more information and a patch installer.
197171 Using SingleToneInformation.GetDetectedSignal may return results that are 180 degrees out of phase.
203199 The Axis.EndLabelsAlwaysVisible property is not cloned when you call the Clone method on an X or Y axis.
215669 Measurement Studio adds National Instruments references to the web.config file of non-Measurement Studio projects.
223012 A .NET graph that throws an exception when calling PlotComplexWaveformsAppend, PlotComplexWaveformsAppendMultiple, PlotWaveformsAppend, or PlotWaveformsAppendMultiple becomes unresponsive and does not redraw.
224471 TDMS file groups with the WaveformLayout.PairedTimeAndSampleChannels property may become corrupted.
227696 Appending data and adding properties to a TDMS file in a specific sequence can corrupt the TDMS file data.
235353 Zooming a .NET graph multiple times with minor gridlines or ticks visible can result in a hang.
240792 Setting the DefaultReadValue of a NetworkVariableBinding to a null reference (Nothing in Visual Basic) results in a NullReferenceException.
243788 Writing data to a TDMS file using AppendAnalogWaveform can result in different number of X and Y values.
247826 The TDMS .NET API leaks memory when creating or reading channels or channel groups.
249777 Some ranges can result in incorrect ticking on graph axes with a logarithmic scale.
249802 The waveform, scatter, and complex graph cursor positions cannot be set before the cursor is added to a cursor collection if SnapMode is set to ToPlot.
252409 Cursors with a SnapMode of ToPlot or NearestPoint slow plotting dramatically when they are not visible.

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).