Strange behavior when using vb.net's background worker

Discussions and Tech Support related to using the iMacros Component for .NET in your applications.

Moderators: Community Moderators, iMacros Moderators

Forum rules
Before asking a question or reporting an issue:
1. Please review the list of FAQ's.
2. Use the Google search box (at the top of each forum page) to see if a similar problem or question has already been addressed. This will search the entire contents of the forums as well as the iMacros Wiki.
3. We can respond much faster to your posts if you include the following information:

CLICK HERE FOR IMPORTANT INFORMATION TO INCLUDE IN YOUR POST

Answering your own posts (e.g. attempting to "bump" your topic) drops your topic from the list of unanswered threads, so it may actually receive less views.

Strange behavior when using vb.net's background worker

by hexinx on Mon Aug 03, 2015 12:20 am

Hello,

I've been using iMacros component to scrape off text from sites. I recently decided to use the "Background worker" component in .net to handle the component's functioning so I can keep the UI responsive. But, this is causing the iim component to behave strangely, I'm not able to get the same result when I play macros when from inside the background worker's asynchronous running, It gives me a #EANX# when the same script works perfectly when used by a regular .play() macro call from outside the background worker.

Any idea why? Probably something related to threading which I don't understand...
hexinx
 
Posts: 3
Joined: Sat Aug 01, 2015 5:08 am

Return to iMacros Component for .NET

Who is online

Users browsing this forum: No registered users and 1 guest

-->