I am developing a process to access an application and make DLL calls to it via COM Object.
The thing is, after I call Activator.CreateInstance, the application login’s dialog shows up, and the control is returned to UiPath only AFTER the login is made, which makes it impossible for me to continue the automation.
I have found a way, though, using a VB Macro invoked inside of a Excel Scope. In this scenario, the VB calls the login screen BUT UiPath is able to input the credentials in a Parallel activity, and the macro resumes afterwards.
Anyone knows why when I use Activator.CreateInstance (on an assign Activity, on even Invoking C# code), the Parallel Activity is unable to start the login process?
Do you have a suggestion as how could I address this situation so I can eliminate the VB macro and the Excel Scope, that I only use to invoke it?
Thanks a lot!