03-06-2017 03:48 PM
Dufei,
Unfortunately, Ren is out of office. I've reached out to him and am rereading your instructions (thank you for the detail) and see if I can recreate the issue and have more next steps.
03-16-2017 04:25 PM
Dufei,
We were able to reproduce the error, and it looks like your application was built with a trial version of Measurement Studio. You need to make sure that you build the deployment with a licensed version of the control.
It's also a possibility that the Python script is copying a bad version of the control to Visual Studio.
I spoke to some colleagues and one recommendation was to reinstall Measurement Studio and rebuild the deployment.
03-16-2017 07:37 PM
Thank you, I will try to do what you suggested.
My application was built on a licensed Measurement Studio (version 12), however, the 3DGraph.ocx was not showing up in the license info list. When I installed the MS, the 3DGraph.ocx was install from a separated CD-ROM and it did not ask me for serial number. I doubt it might be the problem. You may tell me how to enter the license information to the "Legacy" 3DGraph.ocx.
I will report to you what I end up with.
Dufei
03-17-2017 03:28 PM
This KnowledgeBase article may also be helpful. Apologies if this has already been posted.
http://digital.ni.com/public.nsf/allkb/60B1DE0C85624B55802568D90031AF89
03-17-2017 07:22 PM
Yes, I did came cross this KB.
I tried to reinstall the Measurement Studio, however, it still does the same thing.
Since you were trying to help me in the middle of the session, so please read all the back/forward communications that we previous had before. My problem was: there is no problem using and saving the 3DGraph component in my application, the "Evaluation Copy" banner only shows up in the IronPython script session. According to IronPython claims, it can seamlessly use the class, objects etc. that were built in the .Net environment. What I did was to build a public 3D drawing class that uses the 3DGraph component, and then use this class in the IronPython script.
Dufei
03-18-2017 03:33 AM
Hi, Maggie and all others,
After I wrote the reply to you, I suddenly realized that it might be the policy of NI that it does not allow developer to wrap the licensed NI components for the third party to use, that is exactly what I did even though I was trying to use the wrapped DLL in my applications. Since the DLL and implemented methods (which utilize the 3Dgraph component) are public, therefore it can be called from any other application as long as they know the interface of the methods. NI will certainly block this kind of practice.
If this is true, I will then accept the banner as it is and drop the question.
03-24-2017 10:49 AM
Hey Dufei,
I'm back in office. I talked to our R&D department on calling NI components from python . The practice itself is not supported. "Not supported" does not mean that it won't work. It means that R&D did not test it. Because of that, we can't guarantee it will work as expected.
As I mentioned previous, the CW3DGraph control is a non-licensed class library and is licensed in the registry. It does not need to be activated and does not enter an invalid state after MStudio evaluation period expires. I tried install an evaluation copy of MStudio on the laptop that I reproduced the issue with and the evaluation banner went away. My best guess is the ActiveX control was registered properly when MStudio was installed. Since it shouldn't enter an invalid state after MStudio expires, I expect it to keep working.
03-27-2017 12:59 AM
Thank you very much for the reply.
This might be the answer even though it is not so convenient for the end users. They have to install the evaluation copy of the Measurement Studio, just to properly register the 3DGraph.ocx component, since the registration of the component by command line did not work. I will ask my clients to try this approach to see if the problem be solved.
Dufei Fang