-
Notifications
You must be signed in to change notification settings - Fork 6
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
System.BadImageFormatException #50
Comments
Are any of your assemblies compiled to x32 or x64 (instead of AnyCPU)? |
Yes, we call a x86 DLL to connect to hardware so need to be x86.
…On Fri, Aug 16, 2019, 2:24 AM Gáspár Nagy, ***@***.***> wrote:
Are any of your assemblies compiled to x32 or x64 (instead of AnyCPU)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#50?email_source=notifications&email_token=AAQT5LCMLPISKAZMTKGXR3LQEZB3RA5CNFSM4IL6USE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4NZCSI#issuecomment-521900361>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQT5LASHJ365LCFM7W2GGTQEZB3RANCNFSM4IL6USEQ>
.
|
Unfortunately this setting is not detected automatically yet. I believe by adding a file
|
I am getting same error for Debug-x64, specflow 1.9.0, nUnit 2.6.2, Deveroom for SpecFlow, .Net4.7.2, and VS2019. Server stack trace: Exception rethrown at [0]: Warning: InvokeDiscovery: The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled. My steps in .feature file look good, but there is no connection with step implementation. |
Since the last update I'm getting this when I do a build. If I try to generate step definitions I get told that all steps are bound. If I switch back to SpecFlow I don't get the error.
The text was updated successfully, but these errors were encountered: