(Robot API) Problem with robotom interface when many Robot versions installed

(Robot API) Problem with robotom interface when many Robot versions installed

Anonymous
Not applicable
604 Views
3 Replies
Message 1 of 4

(Robot API) Problem with robotom interface when many Robot versions installed

Anonymous
Not applicable

Hi guys,

 

I created an application which communicates with Robot via robotom.tlb library of 2016.

Unfortunately one of my clients has Robot 2016 and 2014 installed, and 2014 is set 

as default launching version.

So despite I attached robotom.tlb reference from 2016 version to my app, it opens in background 2014 version

which try to open 2016 version project and it causes that app doesn't answer.

 

Any idea how to force use 2016 version of Robot by my app?

 

Thank in advance,

Maciek

0 Likes
605 Views
3 Replies
Replies (3)
Message 2 of 4

Rafal.Gaweda
Autodesk Support
Autodesk Support

There is only one version of Robot COM components in windows system always related to last used (=last registered = last started Robot).
Start Robot 2016 and then run your application.



Rafal Gaweda
0 Likes
Message 3 of 4

Anonymous
Not applicable

Hi again!

 

Thanks for quick response.

 

Unfortunately, I tried a solution above and it didn't help 😞

I run Robot 2015, loaded project, closed Robot, and my app was still stubborn to use 2011 as an interface.

 

I experimented with (2011) robot.exe /unregserver, and  (2015) robot.exe /regserver and it didn't help too.

 

Then, out of nowhere, I changed the name of (2011) robot.exe, to robot2011.exe, leaving the name of (2015) robot.exe unchanged.

And it helped at last !!! 

 

So this is my solution so far.

 

0 Likes
Message 4 of 4

m_redmerski
Participant
Participant

I think You can always copy Interop.RobotOM.dll to Your project directory and referency dll via direct dll. I don't know how this solution conform to the licensing issues but should working.

 

Btw dynamo plugin for RSA has such solution.

 

Regards,

0 Likes