New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NSpec doesn't handle strong-name signed unit test DLL #72
Comments
Also possibly this too: #41 |
Interesting. I'll have to read those articles in greater detail when I can. If it's complex, maybe our best shot will be reverse engineering how the other frameworks are handling it. Or maybe just asking ;) |
@JVimes I was taking a look at how MachineSpecification (MSpec) did it's AppDomain stuff... it didn't look straight forward at all T_T |
Doh. Maybe xBehave.net or XUnit do it readably. Is it as simple as signing the NSpec dll? I don't know if unsigned projects can reference signed projects. If so, that sounds like a solution. |
@JVimes XUnit may be your best shot. You may also want to take a look at Fixie. there might be something in there that handles it more elegantly. |
Will not fix. Recommendation is to compile from source and strong name yourself. |
I have to strong-name sign my unit test DLL to friend it to a product DLL. After signing, there's an error, "Referenced assembly 'NSpec' does not have a strong name". I can disassemble and then sign/reassemble the NSpec DLL, but that's a hassle and other frameworks (xBehave.net/xUnit) work OOTB in the same situation. Perhaps NSpec can do what they're doing. I've seen them work with both signed and unsigned unit test DLLs.
The text was updated successfully, but these errors were encountered: