Get ActiveX dll properties?

[PrimusEng]

Dear Artem!

Thank you for your email, but I have some additional questions:

1) In your procedure CreateVirtualFlashOCX I change only 'C:\Flash9e.ocx' to 'Test.dll' if I have my automation object packed into Test.dll activeX library
( all other code remains untouched)
2) How could I access properties and methods from my dll? - for instance if I have there property 'Left' - how could I set or get property value; if I have method 'Calc' - how do I call it?
3) If I have exe application which includes automation object, how could I register it? - by default application register itself.
4) How to write to registry - Vista have here limitations!!

Regards, P.

[Artem A. Razin]

2) How could I access properties and methods from my dll? - for instance if I have there property 'Left' - how could I set or get property value; if I have method 'Calc' - how do I call it?

As usually, when you don't use BoxedApp SDK.

3) If I have exe application which includes automation object, how could I register it? - by default application register itself.

In this case, BoxedApp can't help.

4) How to write to registry - Vista have here limitations!!

You create private /virtual key entries that are visible only within your application.

Thank you.

[PrimusEng]

PrimusEng wrote:
3) If I have exe application which includes automation object, how could I register it? - by default application register itself.

In this case, BoxedApp can't help.

What you advise me to do in this case. I have AutoCAD VBA code which are calling my protected application through COM automation( my EXE application is a COM server, so it should be registered when I start it. What is your solution, since you said BoxedApp can't help in this case.

Regards, P.

[Artem A. Razin]

What you advise me to do in this case. I have AutoCAD VBA code which are calling my protected application through COM automation( my EXE application is a COM server, so it should be registered when I start it. What is your solution, since you said BoxedApp can't help in this case.

So you have a COM, out-of-process, server, but you don't want to write in system registry, right?

Current version of the BoxedApp works within a single process. But your COM server is out-of-process, it works in a separate process.

But we are planning to extend BoxedApp features to make possible co-working of a several processes that access to a single virtual file system and a single virtual registry.

Thank you.