Do I really have to buy Measurement Studio 8.5 to use the user interface class libraries with VC++ 2008

[souldog00]

I have Measurement Studio 8.1.0.  Are you guys really going to force me to spend $1199, to have you recompile Measurement Studio with MFC 9, to upgrade to 8.5 if I want to use VC++ 2008.  I have reviewed the "additional functionality" and need none of it.  Is there another way?

[drohacek]

Measurement Studio 8.5 does not include support for VC++ 2008/MFC 9. This support is planned for the next release, currently scheduled for the end of the year.

Measurement Studio 8.5 does include support for using the .NET class libraries in Visual Studio 2008/.NET Framework 3.5.

With respect to the cost, if all you need are the user interface class libraries, these are available in the Measurement Studio Standard Edition, which is currently $499. We understand that it is frustrating to have to pay to upgrade to a new version of software when you intend to take advantage of only a few (or one) of the new features. Unfortunately, we are not in a position to be able to offer features a la carte. We consider adding support for a new version of MFC to be a feature in that it requires non-trivial engineering effort for us to deliver it.

David Rohacek

National Instruments

Message Edited by drohacek on 08-27-2008 08:19 AM

[ifreak]

I agree with souldog... I think NI should give me upgrades to software for free if I don't want any of the new features.

Oh wait... If I don't want the new features... Maybe I shouldn't upgrade?  

[souldog00]

I did not say I wanted it for free.  That there is significant engineering effort to recompile this class library using the new compiler is nonsense.  The "new" version of MFC just added some fluff and there is nothing that would break a CWnd based implementation like this controls library.  No matter.  Luckily I wrapped all use of measurement studio in a extension DLL and used the pimpl idiom.  So nothing else  in my project explicitly needs the NI implementation of these controls

1.  One can just create a regular DLL statically linked to MFC that wraps the analysis library and compile it with VC 2005.  This can then be used with applications compiled with VC 2008.

2.  I just wrote the user interface library myself.  The only control that presented some challenge is the Graph.

So you are right.  I don't need the upgrade .

[drohacek]

I agree that recompiling a single project with a new version of MFC is not that much effort. My original response was a little bit misleading. It isn't just the new version of MFC that requires significant effort, it is support for the new version of Visual Studio as a whole that requires significant effort.

I think that the solution that you came up with is perfectly fine for your needs.

The significant engineering effort I was referring to is invested in the following:

• Creating and managing new projects for each library that we provide
• Updating our source code to comply with changes to MFC and the compiler
• Generating new projects and solutions for every example program
• Updating Visual Studio integration features to support the new ADE; this includes wizards, DAQ Assistant, etc.
• Updating, running, and evaluting the results of automated tests to verify that the new version of MFC has not broken anything
• Updating, running, executing, and evaluating the results of manual tests to verify that the new version of MFC has not broken anything
  • Manual tests are required to verify some user interface functionality
  • Manual tests are required to verify most Visual Studio integration functionality
  • Manual tests are required to verify some example functionality
• Generating new documentation
• Updating our build process to generate all of the components to be installed
• Creating and testing a new installer for the product

David Rohacek
National Instruments

[souldog00]

Ok, I agree that QA does involve engineering effort and support for the IDE does involve engineering effort.  I guess I was not clear.  What I would suggest is to just recompile and offer the binaries.  Maybe a couple hundred dollars.   Don't  offer any support and don't guarentee that they will work.  (we both know they will).  I believe you do something  similar with the driver development code (although it is free).  I for one do not need IDE support.

Sorry for my sour attitude.  I just was porting a 150,000 line project to VC++ 2008, and everything went fine except oine DLL which depends on Measurement Studio.  Although I don't need the upgrade features of Measurement Studio,  I want some of the features of VC++ 2008.  Problem is now I have to do all the QA on my version of these controls.

I am sure I will most likely upgrade when you guys get the newer version finished later this year.

[drohacek]

No worries. I definitely understand your frustration at the MStudio libraries being a hang-up on a project like that. I've made a note of your suggestion and will discuss it with others who make decisions on these kinds of things.

David Rohacek

National Instruments

[souldog00]

Thanks, I appreciate it.