Nunit not releasing a DLL used in a test / can't delete in teardown -


I have an application that is unmanaged, and clearly interconnected with a buggy, DLL.

I have been compensated by checking my application to check all kinds of error conditions when DLL is running, like DLL has gone into an infinite loop.

I'm trying to test this handling in my application, and so I deliberately coded a DLL which goes in the infinite loop on purpose.

In my unit test, I want to change the name of the original DLL, I want to copy in my 'broken' DLL, run the test, see the timeout code, then remove the broken DLL And replace the original DLL.

However, I guess this is unofficial access to my tyride method because nUnit still has some kind of DLL 'Open'.

How can I issue DLL to nUnit?

Well, I worked around it by dividing the trouble tests in nearby assemblies. I now have 3 test assemblies, 1 out of which there are large numbers of tests, and in each of the 1 I have problems in the tests.

Therefore, I still do not know how to release the DLL, but to exclude the tests, two of those tests include set up and tyrund code, which is any disorder Can be saved from other tests. I do not need anymore in different assemblies.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -