Measurement Studio for VC++

cancel
Showing results for 
Search instead for 
Did you mean: 

Do I need to install hot fixes for memory leaks in UI components for ms 6.0 for C++ if I installed a version that came with the .NET package

I recently got a copy of Measurement Studio for VC.Net
I installed the copy of ms 6.0 which came with it. Are the hot fixes incorparated into this version or do I need to install them. Where do I find out about the problems with measurement studio. I just stumbled on to the memory leak problem, although I had seen it during profiling. This seems like a big issue and if there are others I would like to know about them.
0 Kudos
Message 1 of 5
(3,720 Views)
Hello,

The Measurement Studio 6.0 CD that ships with Measurement Studio 7.0 for .NET is different in 2 ways:

1. It no longer includes CVI for installation.
2. It includes an updater to fix issues that we re solved by the time Measurement Studio 7.0 shipped (see attachment).

There may be a readme in teh base directory of the CD that talks about what is updated by the updater.

Jeff
NI
Message 2 of 5
(3,720 Views)
Thanks Jeff, that is exactly what I was looking for.
In the future how do I found out about bug fixes as they are found?
0 Kudos
Message 3 of 5
(3,720 Views)
That is a question I don't really know an answer too.

I do know that if there is an issue found with a released product that we have a fix or workaround for in R&D we create a knowledgebase(KB) entery for the problem.

The KB search can be made from the product support pages located:
http://www.ni.com/support/

You can choose a product to narrow the search and see the top 10 support issues for a given product. I hope this helps you.

Jeff
NI
0 Kudos
Message 4 of 5
(3,720 Views)
OK, thanks for the help. I don't know if the lack of centralized error reporting "place" is a "marketing" decision, but just to complain a little: I have had this product for two years and was never made aware of the problems which have fixes. I just happened to stumble into your ftp site and found out about them. It seems like a bad idea to make the client go digging around in the knowledge base to discover this stuff, especially since the memory leaks are not reported by the standard VC++ IDE, you have to use purify or some other commercial product. What is worse, having someone�s control system go down in release or admitting there are some problems up front? I think developers would understand the spiral cycle of software rele
ase.
0 Kudos
Message 5 of 5
(3,720 Views)