Closed wherget closed 5 months ago
Would any of you mind having a look at this PR @EvaisaDev or @Lordfirespeed? You can check my usage from the mentioned PR in LLL. If this is indeed an issue (and I'm not just weirdly holding it wrong, I feel like I can't be the first person to use the MSBuild patcher o.O), is this even the right way to go about fixing it?
As is,
Default.LoadFromAssemblyName
may fail to load the Serilog dependency when using the MSBuild SDK, leading to exceptions like:This PR adds code to attempt to manually resolve the assembly from the
PatcherCommonAssemblyDir
before deferring to theDefault
Context.Additionally it changes the LoggingConfiguarion for the MSBuild Task to also emit Debug messages. These are only shown when MSBuild'ing with verbosity detailed or higher anyway, but filtering them out in the Task leaves them completely inaccessible.