Pablo Monteiro

Closing this issue due to lack of activity, if anything new, open a new one.

Hello @vladimirKa002, I believe I understand what you mean, I was curious and did some local tests, I really didn't find a way that works. Looking at swashbuckle it seems...

Hi @chucker , I'll look into it and get back to you.

Hello @Karql and @chucker I tried to simulate the problem, but all attempts worked without errors. I created a [unit test](https://github.com/phmonte/Buildalyzer/pull/266) to simulate the problem and a [project ](https://github.com/phmonte/BuildalyzerSample/tree/main/ClassLibrary1) in...

@Karql thanks, now it's possible to reproduce, I'm investigating.

I believe I found the problem, it's [here](https://github.com/phmonte/Buildalyzer/blob/140a2e00c3a72707d3b715fa88998d76510bfedf/src/Buildalyzer/ProjectAnalyzer.cs#L257). It uses the dll address to send to msbuild, I'm testing some alternatives.

The msbuild result is captured through the log, there is a custom log that does all this work, removing it will be a bit complex, I'm thinking about other alternatives...

Hi @Karql , I did some tests in the last few days, from extracting a dll to manipulating the assembly, unfortunately I was not successful. I believe the healthiest solution...

@Karql I ended up forgetting to mention it. There are 2 dlls, could you test by removing them? -MsBuildPipeLogger.Logger.dll -Buildalyzer.logger.dll I really believe it will solve your problem.

Thanks for confirming, I believe it's not the best solution, but it's the only one that enables PublishSingleFile due to current restrictions. I will make some of your suggestions.