Measurement Studio for .NET Languages

[VB.NET/ASP.NET…]

I created an ASP.NET webform which uses the cwui.ocx ActiveX control. The webform uses like 10 guages and 10 sliders. When I view the page on my development machine (which is also acting as the dev server) it works fine. When another user tries to access the web page they get 2 messages:

1. Failed to load mesa.dll.

2. You have 30 days to evaluate the Measurement Studio ActiveX control. After this period the controls stop functioning after 5 minutes of execution time. To order Measurement Studio contact your National Instruments branch office or visit the online store.

After 5 minutes on every page refresh the user gets the following error:

Your Measurement Studio evaluation only controls have stopped functioning. Restart your program to resume operation. To order a development version of Measurement Studio contact your National Instruments branch office or visit the online store.

FYI: In my HTML tab I did add a codeBase to the first OBJECT Tag. Here is the beginning of it:
OBJECT id="knobFrequency" style="Z-INDEX: 104; LEFT: 200px; WIDTH: 132px; POSITION: absolute; TOP: 152px; HEIGHT: 112px"
codeBase= "http://localhost/MyWeb/cwui.ocx" classid="clsid940E4D2-6079-11CE-88CB-0020AF6845F6"
name="knobFrequency" VIEWASTEXT>
PARAM NAME="_Version" VALUE="393218"
:
:


QUESTIONS:
1. Any ideas on how to get this working? How to stop the messages?
2. Since NI does not provide pure, managed .NET, server-side ASP.NET controls I have to use this same ocx that I used to use in VB6 development. Any idea when NI will provide managed .NET, server-side, ASP.NET controls for the guages/sliders?

Thanks.

Message Edited by Support on 01-25-2005 08:03 AM

[Elton Wells]

The Mesa .dll loading error is probably because the control is instantiated on the client computer, the control is using a 3D style, but the Mesa .dll was not deployed to the client computer. The Measurement Studio CD has a merge module called NIMesaDll.msm that you should use to redistribute the Mesa .dll dependency that the cwui.ocx controls need for the 3D styles.

The licensing problem is probably because you're using the control directly in the web page and the client machine does not have a license to use the control. You can work around this by either a.) creating a user control (most easily done in VB6) that uses the cwui.ocx controls so you can distribute a control that contains a valid embedded license, or b.) follow the directions in the Microsoft
Knowledge Base article HOW TO: Use Licensed ActiveX Controls in Internet Explorer.


Hope this helps.

- Elton

[VB.NET/ASP.NET…]

1. What is a merge module and how do I "use" it to "redistribute the Mesa dll dependancy?"

2. Any word yet on when NI is going to provide manage, .NET, server-controls for ASP.NET? (Even beta?)

[Shelley]

Per your second question: "Since NI does not provide pure, managed .NET, server-side ASP.NET controls I have to use this same ocx that I used to use in VB6 development. Any idea when NI will provide managed .NET, server-side, ASP.NET controls for the guages/sliders?"
We are always interested in your product feedback and looking into additional technologies for Measurement Studio. If you are interested in ASP controls, please send me an email directly Shelley.Gretlein@ni.com and let me know which controls you'd like and the types of applications you are interested in developing. Thanks!
Shelley

[Elton Wells]

See the MSDN article Introduction to Merge Modules for information about what merge modules are. See the MSDN article Walkthrough: Creating and Consuming a Merge Module for a step-by-step guide on how to use a merge module in a redistribution project.

- Elton