Sign in to follow this  
Followers 0
Avaya

Blocking dlls?

6 posts in this topic

Hi,

I'm writing scripts in AutoIT from some time but I wanted recently to run them on building machine (CI). I simply added new task to Windows Scheduler so it runs my scripts at 3:00AM every day. Scripts operate on directory where binaries of my soft are put (binaries that are used by soft being tested of course), and they are supposed to be deleted before every build. But my script seems to block those dlls (although it's script ends properly) and they cannot be deleted which causes error on CI machine. Anyone had similar problem?

Thanks for help!

Share this post


Link to post
Share on other sites



Your terminology is confusing. You seem to use the word script to define the script you have written and your soft.

I think your software is not releasing the dll's proper, causing them to remain in use?

Share this post


Link to post
Share on other sites

#3 ·  Posted (edited)

As 'script' I mean my AutoIT script thats launching and making some GUI operations on software. Software is being build in CI technology (it means that after each build all binaries are deleted and replaced with new ones) on building machine so that's where my script has to be launched. Script performs some work and then exits with code 0 or 1, but dlls of an application that the script is testing are blocked and unable to be deleted.

Hope it's clear now ;-)

Edited by Avaya

Share this post


Link to post
Share on other sites

but dlls of an application that the script is testing are blocked and unable to be deleted.

Obviously, while the script is testing the dll's, these are blocked and therefore can not be deleted.

It honestly sounds like you have no idea what's going on, and who's doing what. Have you tried making an activity diagram?

Share this post


Link to post
Share on other sites

Obviously, while the script is testing the dll's, these are blocked and therefore can not be deleted.

It honestly sounds like you have no idea what's going on, and who's doing what. Have you tried making an activity diagram?

Make sure you used DllClose() on any DllOpen() handles if you're making any calls to the dlls in your script.

Also, if the software is releasing the handles on the files, i.e., using the close function on the files.


[topic="80940"] AutoScript Creator, Script to automate anything![/topic]

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0