complog
complog copied to clipboard
jaredpar
Basic Compilation Log support
Today if there are two binlogs or complogs in a file, commands like `complog export` will pick one of them. That is fine but should probably issue a diagnostic saying...
Today the export command creates build files that effectively `dotnet exec csc.dll` for the generated .rsp file. This means it strongly favors .NET Core based compilers vs .NET Framework ones....
When the compiler is hosted as an API today, the binaries are loaded from our referenced NuGet packages. This works in the vast majority of scenarios due to the back...
Running the `replay` command without arguments re-runs the compilation in memory. That doesn't output anything to disk yet the command is outputting a path ```cmd > complog replay Outputting to...
Items that could be included for NuPkg - Where a package was downloaded from - What packages a project used (direct or indirect)
Introduce a `complog serve` command that fires up a source browser instance on a compiler log and runs the server locally. https://github.com/jaredpar/SourceBrowser
Right now everything is a DLL reference, needs to support compilation references. Just unwinding the MVID
A vulnerable version of this package is being brought in by Microsoft.CodeAnalysis. Remove this once we move to a version of the package that requires a version that isn't vulnerable.
This package is being brought in through MSBuild.StructuredLogger -> Microsoft.Build.Core.Utilities. Once the root package is updated to require a non-vulnerable version we can remove this explicit reference.