Forum Discussion
tristaanogre, yes, it is.
I want to add one remark. I run tests in Visual Studio, while I'm debugging them. Then I put .dll on remote computer and run them using NUnit console. Problem is reproduced in this case.
- tristaanogre8 years agoEsteemed Contributor
Gotcha...
So, is it possible for you to post the actual code that is generating the error messages in your DLL? The reason being is that somewhere in your code, something is being read in as a DBNull value and you are attempting to cast that as some other value (string, integer, something).
If you can't post the code for privacy reasons, the next best suggestion is to take a look through your code and make sure you do any necessary checks for a "NULL" value... like if you are trying to grab information from internally in your AUT and use it in your test code. Your test code may not be using a database but your application under test may be and, if that's the case, it could be returning a NULL value that your test isn't designed to handle.
This is all conjecture and best guess but that's where I would start looking, based upon the error message you are seeing.