Per Samuelsson

> will you manipulating the target assembly in the context of MSBuild? That's the idea, yes. But it's not isolated to that scenario, as the sample illustrate. And I will...

> ... assembly resolver for .NET Core ... Is that [BaseAssemblyResolver](https://github.com/jbevain/cecil/blob/3145301c039bfef6f9bfe0f1526f076b3652a5fc/Mono.Cecil/BaseAssemblyResolver.cs) compiled with `NET_CORE` defined? > ... assumes the published case, where all package references are copied in the target...

@receiptline I'm currently evaluating `receiptline` and really enjoy it so far. My aim is to get it to work with Star `webPRNT` and Epson `ePOS-Print XML`. I've accomplished the first...

By tweaking some parts with the help of what you wrote above, I finally got it to work now. I can't thank you enough - you are a hero! 🥇...

Oh, from what I read, I have understood the proposed solution would be to use `X-forwarded` and similar, and put this as a responsibility of the destination. But that is...

Thanks @Tratcher for a fast and clear response. 👍 Feel free to close this issue as resolved. Keep up the good work. Just a short comment on the answer: >...

I have this in VS Code since earlier this morning, after I bumped some assets. I think it was the `"C# Base language support"` extension I bumped, and it's now...

I have `Microsoft.Azure.Functions.Worker.Sdk 1.17.2` and the latest tooling, `4.0.5611`. This issue persist. Deleting `bin` and `obj` works as a workaround still.