| || |
3rd party .NET obj either crashing TP or saying they are in use while referencing
I am running TP to test an applicaton using the Infragistics controls.
It is ok on one machine - but on 2 others when I start TP and open the driver script, sometimes when it tries to build the Intellisense for the Infragistics, when it gets to the registering the dll TP crashes and has to be restarted. On restart it starts on the next dll and the same thing can happen.
Then when running it was giving Type Mismatches and not returning objects. Manually trying to add the .NET references gives an error box saying that the object is in use by something else.
Looking on this site I see that some of this can be caused by opening the App from inside TP - and I have found that by running the app first and then TP it seems to work a lot better.
does anyone know the reason for this or a work-around as ideally the AUT would be opened from TP.
Re: 3rd party .NET obj either crashing TP or saying they are in use while referencing
Understanding what happens might help. When you add a reference to the dll for the first time the build will happen. If you look in the directory of where that dll lives... you will see that TP has created 2 new files. 1 is an Interopt file and one is a .tbl.
When you open the script moving fwd... tp checks to see if these 2 files exist. If they do a rebuild should not happen unless you choose to "update".