-
Notifications
You must be signed in to change notification settings - Fork 80
Controlling the task output #165
Comments
Here is a quick code up of the idea of adding When going through this though I wonder if Thoughts? |
We had the same issues for our WPF libraries. I think SkipVerify is much more than just skipping missing files verification, so I definitely think we should introduce a new option for this. Or... maybe we could just auto-skip .xaml files (but then, what's next?). |
Another idea I had was essentially adding glob support for files to ignore when linking. This would allow a very granular approach to filtering out problematic files. The default could simply be *.xaml. |
Yes, but that wouldn't solve your #line directive issue, would it? |
I think it would solve that. For that project we'd just override it to ignore both |
Last night I was looking into the possibility of moving dotnet/roslyn to using the GitLink MSBuild task. Previously we were using the command line tool as a post build step. That works but had a couple of issues we were hoping the task would resolve. Most notable: performance and completeness.
Using the build task appears to fix the performance issues we were seeing with the command line tool. However it has another problem that is blocking adoption. Whenever it finds a file in the PDB that it can't find in the Git tree it will issue an MSBuild warning and dump output to the console.
This blocks adoption in roslyn because we build with
/TreatWarningsAsErrors
and have a couple of patterns that GitLink can't handle. The patterns are:#line
directives: these are done for self hosting a number of compiler features. As a result though the PDB has a couple of lies about missing files in it.The XAML problem may be solvable but likely not the
#line
directive. The PDB is deliberately lying to GitLink here so not much for GitLink to do.Been thinking about this over the evening. Wondering if we could get an option to tell GitLink to not warn on missing files. That should be off by default but for cases like Roslyn, where we know we're going to lie a bit, we could turn it on for the projects where it happens. Something along the lines of
Example of the XAML missing file warning:
The text was updated successfully, but these errors were encountered: