Wrapper classes generated by VC++

[Billy H]

I'm using Measurement Studio 6, VC++6 SP5.

I used the MS6 Add/Remove wizard to add several NI gui components to my exisiting (large) project. When I use the ClassWizard, VC++ generates wrapper classes for each of the NI controls. So, for example I must use CCWPointer (generated) instead of CNiPointer.

I also created a test app using the MS6 appwizard. This does not appear to use any wrapper classes. This gives a far neater project as it doesn't need to maintain those extra generated files and classes. I compared the .dsp's and the .dsw's, but can't find any relevant differences.

So, can I use MS6 components without generating those wrapper classes? How?

Thanks,
Billy.

[Elton Wells]

Ideally, you never have to use the wrapper classes when using Measurement Studio components. When you added the UI components with the Add/Remove Components wizard, you should have seen the same behavior in your large project as you did in the smaller test project. There should definitely be a difference between the two projects' files, so try doing a Save All and diffing the .dsw/.dsp files.

If for some reason you're not able to get the wizard to work, take a look at the "Manually Adding Components to an MFC-Based Project" topic in the Measurement Studio reference.

- Elton

[Billy H]

My project files have all the settings as described in the reference topic - "Manually Adding Components to an MFC-Based Project". These settings were added automatically by the Meas Studio 'Add/Remove' Wizard.

I also compared again against the smaller apps project files and can't see a difference in the Measurement Studio parts. My app works ok, but the wrapper classes are messy.

Any other ideas why VC++ generates wrapper classes for the Meas Studio components ?

Thanks in advance,
Billy.