Herrmel

I just discovered this aswell and found out this only occurs in Assemblies compiled with debug-Configuration. Thought I'd share my observation. I'd guess it's something like a Placeholder for debug...

Is there any Update on this as I'm facing the same problem for my dll's. Or will this be addressed with release v3?

Yeah I had to do a workaround myself. I compiled a Version without the line where the wrong .net-Assembly is loaded and added the correct .net core assemblies via paths...

> I'm not sure I like the idea of the priority flag because it would change the existing behavior of AdditionalDocPaths. I originally meant that to be a way to...

> Interesting... Having been spared the horrors of writing culture-aware code for most of my career, I generally tend to ignore those little `de` folders scattered around, but I can...

This seems related to a problem I reported wich continously got blamed as external 2 times: #19813 I found out that my problem does not occurr in every Version of...

1. I think your takes are completly accurate as far as I can see. Especially the part with the bad auto translated Docs by microsoft most developer have to avoid....

I opened this Bug in the PowerShell repository first and was guided to this repository. More Details here: [#18771](https://github.com/PowerShell/PowerShell/issues/18771)