You clean + build all and assume everything went well as you see no error.You have multiple projects within a same solution.The main reason may simply be that your project dependencies are messed up! What I figured is that there is always a good reason for this problem to occur (And is not a Microsoft bug! - Well, VS could get better at flagging it though :-)). I have add the same problem various times and none of the answers from this treat could help or if they did it was by using a nasty work around. So it needs to dispose its local property _serviceProvider in its own Dispose method, because the test class constructor SQL_Tests instanciated it.
_serviceProvider = fixture.ServiceProvider Var fixture = new DbFixture() // NOTE: MS Dependency injection framework didn't initialize when the fixture was a constructor param, hence it is here The same pattern you need for the test class itself - it needs its own Dispose method (as shown for the DbFixture class above): public SQL_Tests(ITestOutputHelper output)
STONEHEARTH ALPHA 24 DEBUG AUTO BUILD CODE
Put cleanup code in 'Dispose(bool disposing)' method
STONEHEARTH ALPHA 24 DEBUG AUTO BUILD FREE
// TODO: override finalizer only if 'Dispose(bool disposing)' has code to free unmanaged resources TODO: free unmanaged resources (unmanaged objects) and override finalizer dispose managed state (managed objects) Protected virtual void Dispose(bool disposing) That will help to end the tests in a clean way and unlock related locked files as soon as the tests ended.Įxample (DBFixture is used by xUnit tests): public class DbFixture: IDisposable Then, dispose the related contained propertys and explicitly assign them to null. Note that you can just add IDisposable interface to your DbFixture and let IntelliSense add the Dispose pattern. That will cause the assembly files being locked even if the tests completed. What helps then is to check if you can add a Dispose pattern, for example if you're adding a DbFixture and the database contacts isn't disposed properly. Other test runners, like xUnit can cause the same issue. After killing the process, was able to rebuild process, without restarting OS or VS2013. In my case it was Resharper Unit Tests runner (plus NUnit tests, never had such problem with MsTests).
0 kommentar(er)
