Tim Bussmann

Thanks for the repro sample, this is very helpful! 👍 IIRC, there have been a few optimizations around resolving message types and assembly scanning which are most likely related to...

Ok so I played around with v8 and v7 a bit and this isn't directly a bug in the logic of NServiceBus but rather related to how assembly loading and...

> both your blog post and also the Microsoft employees in the issue linked above recommend avoiding Assembly.LoadFrom() on .NET Core. Would you trust upcoming .NET versions to maintain this...

I wanted to add an additional comment about some potential approaches to "fix" this by making message-type resolution work for this specific scenario. Ultimately, the problem is caused by the...

@mikeminutillo I've changed my primary email recently but it doesn't seem that signing the CLA again resolves the check. Feel free to cherry pick the suggested change into a new...

@mikeminutillo I force pushed my changes with my github assigned email so CLA assistant should be happy now.

Related: https://github.com/Particular/NServiceBus.SqlServer/issues/1216

> Did you setup a copy of the modified docker image and test this locally? @Riolku tbh I'm struggling a bit with this. locking at the docker files in `.docker`...

thanks the `-v /path/to/your/judge/checkout/including/this/PR:/judge` did the trick (although it required some extra workarounds when running on Windows) > (Instead of editing /judge-runtime-paths.yml in the container you can also pull this...

> The code causing this error is... kind of wrong. I'm honestly a bit confused because a different PR will handle /proc/self differently. based on the `Must pass a normalized,...