Can not find dll, and finds dll.config only

[Doughboy02]

I keep getting this issue whenever I run anything other than an "[InProccess]" run.
I am currently trying to run a [SimpleJob] just so I can control the warmup and call count and so on... Here is the issue, I don't feel comfortable pasting the whole log.

// *** Execute *** // Launch: 1 / 1 Did not find C:\Users\XXX\bin\Release\netcoreapp2.2\win-x64\publish\8a5aaa1a-8e58-47c8-825b-89a7acbaa72b\bin\Release\netcoreapp2.2\8a5aaa1a-8e58-47c8-825b-89a7acbaa72b.dll, but the folder contained: 8a5aaa1a-8e58-47c8-825b-89a7acbaa72b.dll.config Executable C:\Users\XXX\bin\Release\netcoreapp2.2\win-x64\publish\8a5aaa1a-8e58-47c8-825b-89a7acbaa72b\bin\Release\netcoreapp2.2\8a5aaa1a-8e58-47c8-825b-89a7acbaa72b.dll not found ExitCode != 0 No more Benchmark runs will be launched as NO measurements were obtained from the previous run!

Sorry if someone has asked this already, I haven't been able to find it or solve it...

[jonso4]

@Doughboy02 were you able to solve this? I am running into the same issue!

[Doughboy02]

Sorry I can't remember if I was able to fix this or not. I ran into it during an internship and I no longer work there and do not have access to the code :(

(edit) This question can be removed unless it will provide use to others. I am no longer in need for this to be fixed.

[Meimax]

Since I found this issue the second time today in response to the same problem: In my case there was a directory.build.props file which overrode the default build path. The workaround mentioned in #1457 did not work for me, instead i just created a new project with a blank directory.build.props file.

[timcassell]

@Meimax Build path overrides like that will be fixed in the next release. Other directory.build.props properties will still affect the build for now until #2467 is merged. You can try the latest nightly version if you want.

[Meimax]

Thanks for the quick response. This issue is the first result when I google it so I just wanted to maybe give a hint to others searching for the same problem.

[colejohnson66]

Can confirm that 0.13.13 nightly fixes it.