Measurement Studio for .NET Languages

Hi JSInc,

Registering the ActiveX component won't have any affect on the error message you are receiving.  My guess is that you are including the cwui_ocx.msm merge module in your Visual Studio deployment project.  I know why the error is occurring I just can't figure out how you got into the state you are in.  So here is a list of questions for you to answer:

1. Do you get this error when trying to add the merge module or just when building your actually setup project?     
2. What versions of Measurement Studio do you have installed? You mentioned 8.5, but did you just install the VS2008 support? By that I mean if you look on the CD, you will notice 3 different setup.exe's, each one is for a different version of Visual Studio. Based on the version number of 8.1.11.472, this looks like you probably had Measurement Studio 8.1.2 on your system before.  
3. In your VS setup project, what Measurement Studio components are you using (i.e. assemblies)
4. I assume you are also using the legacy ActiveX controls (i.e. cwgraph, cwknob, etc) and thus that's why you are including that merge module in your project?

Best Regards,

Hello Jonathan,

1. I did not try to add any merge module. I got this error when I built my actually setup (in contrast with application) project.

2. I believe I installed version 8.5 Measurement Studio. To make sure I did it, I just run the setupVS2008.exe again. Than the Installation Summary "No software will be installed or removed".

    Here is the list of references in my application project:

NationalInstruments.Analysis.Enterprise                version: 8.5.35.220

NationalInstruments.Common                                version: 8.5.35.149

NationalInstruments.DAQmx                                  version: 8.8.35.13

NationalInstruments.DAQmx.ComponentModel     version: 8.8.35.13

NationalInstruments.MaxConfiguration                   version: 8.5.35.311

NationalInstruments.Net                                          version: 8.5.35.220

NationalInstruments.UI                                            version: 8.5.35.220

NationalInstruments.UI.WindowsForms                 version: 8.5.35.220

3. I don't use any Measurement Studio component in the setup project, the only thing I use is the primary output from the application project.

4. I am not using cwgraph and cwknob controls, Measurement Studio controls I am using now are led, legend, waveformGraph and numericEdit .

Thanks,

JSInc

The NationalInstruments.Net (DataSocket) assembly pulls in the cwui_ocx.msm merge module. My guess is that you are getting this error because that merge module doesn't exist on your system. Can you please look in the Program Files\Common Files\Merge Modules directory for the cwui_ocx.msm file. Now, if you only installed VS 2008 support, you shouldn't have this file as this was an oversight on our part. However, you mentioned that you had the underlying cwui.ocx component so I am going to assume that you installed VS 2005, 2003 or VS 6.0 support on that machine at some point.

If you are not using DataSocket in your project, then you can remove this assembly reference and then your dependency chain in your setup project should dramatically reduce. This will remove the requirement for this file. 

Best Regards,

Hello Jonathan,

There is no cwui_ocx.msm file in the

Program Files\Common Files\Merge Modules directory.

Since I am using DataSocket, how can I get the cwui_ocx.msm into the directory? Or do you recommend using Network Variable instead of DataSocket?

Thanks,

JSInc

Hi JSInc,

Well that explains why you were receiving those messages when trying to build.  The question is, why don't you have that file in the first place. If you could provide me with some background information (i.e. did you ever install Measurement Studio  Support for Visual Studio 6) on what you have installed on that system and in what order, that will help. 

As far as getting a copy of cwui_ocx.msm, I can send you a copy offline, but I just need your permission to get our web team to provide me with your contact information.

In the future, I do recommend that you use Network Variable instead of DataSocket, but since it sounds like you are in the deployment phase, it might be to much work for you to update your DataSocket code to Network Variable.  If you are interested in migrating (which I recommend), check out the Migrating to Measurement Studio Network Variable From DataSocket help topic found in the NI Measurement Studio Help.

Hello Jonathan,

Thank you for your reply. I just migrated to Network Variable and found that the performance is 4 times better than DataSocket in my project.

Best regards,

JSInc

Hello Jonathan,

I found one thing nice about the DataSocket is the Attribute feature. When I have to use multiple DataSockets to send data, I can use the Attribute feature to send a group ID with it. In the reader side I can group the receive data based on the ID. I could not find similar feature with Network Variable.

Thanks,

JSInc

That's great that you migrated already to Network Variables.  As far as the attribute feature, the closest feature to that is the NetworkVariableData.TimeStamp property.  Maybe you can use that.  Either way, I think this is something we should consider implementing in the future. What I would suggest is that you file a product suggestion to us so we have your request in our database.

Thanks

Best Regards,