what merge module and/or drivers necessary to deploy app with CWNumEdit, CWGPIB, CWSerial, and CWButton

[KBr]

Thank you to Johnathan for getting me this far.  I am the person who is trying to build and deploy an app
onto another machine, of which i do not know what is on it.  I got my app to build and now i'm creating an
installer and adding merge modules based on the help....when i run the app on the target machine, it
still says "An unsupported operation was attempted".  I am assuming that i still need more merge modules
and/or drivers...and i don't know which.  I am guessing the controls that still aren't "supported" are the
ones that are from visual studio 6 support.....I am guessing that these controls are:

CWNumEdit, CWGPIB, CWSerial, and CWButton.

Could someone help me and point me in the right direction if i need to install drivers for these and/or
what merge  modules they are contained in?

THANK YOU!!

K

[KBr]

is there anybody out there that can help me with this??  I am desparate to
get this to work on the target windows xp machine!!  I installed a bunch of the
driver cds on the target machine and it STILL doesn't run...

help!

thank you!

[jlaney]

Hello,

The CWUI_OCX.msm contains the merge modules necessary for the UI Controls.  This can be found in the standard, [ProgramFiles]\Common Files\Merge Modules location.  The GPIB, and Serial are only found on the Measurement Studio for Visual Studio 6.0 CD.  They are contained in a folder called "Redist" that is on the root of the CD.  Along with these merge modules, you will have to install a GPIB and Serial driver to work with any hardware that you have installed on your machine.

-Jeff
NI

[KBr]

I feel pretty stupid, but i have the 6.0 cd and am looking at the Redist directory.....I cannot tell which MSM files are the
files that i need for GPIB and Serial....the names of the MSMs do not have any GPIB or Serial in the name...

I already have CWUI_OCX.msm in my deployment project......

Thank you for all your help!!!  i think i'm getting closer to getting this working....i hopefully just need the names of the msms
for the GPIB and Serial..

🙂
K

[KBr]

well, 

somehow i figured out that the GPIB ocx is called cwinstr.ocx......
this ocx was not registered on my target machine.....i copied
the ocx over to the target machine and registered it via regsvr32...
and the app that i'm trying to run actually ran as much as it could.

my question is, does this cwinstr.ocx have an associated merge file?
i do not understand what merge files are, but cwui.ocx has a merge
file named CWUI_OCX.msm......

can someone tell me what these merge files do, if there is a merge file
for cwinstr.ocx and if so, what is it's name???  it is not obvious by
looking on the visual studio 6 cd  redist directory....

does a merge file contain the .ocx??? and does it register it on the machine
when the deployment installer is run?????  or do i have to manually
copy over and register the ocx's???

help please!!  i'm almost finished with this !!!! 

THANK YOU AGAIN for ANY HELP!!

K

[KBr]

Can anyone tell me if there is a merge module that cwinstr.ocx is contained in??

i.e., i need to know what merge modules contain CWNumEdit, CWGPIB, CWSerial, and
CWButton....  i'm pretty sure that CWUI_OCX.msm contains at least one of these..

please help!!!

i'm almost finished!!!

if there isn't a merge module, then how do i put it in my deployment project in
visual studio 2005, so the msi will be able to install the ocx's..

HELP!! please!!!!!!!!!!

[JonathanN]

Hi KBr,

If you are using any ActiveX UI components (like CWNumEdit, CWButton) you need to include the CWUI_OCX.msm merge module as well as the NIMesaDLL.msm and nimetautils.msm.  Those merge modules you can find in the [Program Files\Common Files\Merge Modules\] directory. The CWSerial and CWGPIB ActiveX controls are part of the cwinstr.ocx file located on the Measurement Studio CD as you have already found.

When building an installer, you can simply add the cwinstr.ocx file to your setup application, and specify that it should be register when installed. You just click on the cwinstr.ocx file once its part of the setup project and then configure the Register field in the Properties Window.

Best Regards,

[KBr]

Ya WhOOOOOO!!! 

Got winstr.ocx in my deployment project, set up to register upon install, and all is well!!!

I feel pretty stupid, but I thank you very VERY much!!!

I've never worked with NI "stuff" before, AND have only had very simple deployment projects to setup so this was ALL new to me....

THANK YOU THANK  YOU THANK YOU THANK YOU!!!

K