Component Debugger can fail with "filename or extension is too long"

[chsienki]

When using the component debugger, we grab the command line CSC invocation of the target project and start that under the debugger. In certain projects that string overflows the maximum allowed limit for windows command lines, and leads the (confusingly titled) "filename or extension is too long" error.

We should instead put the command line in a response file and pass that instead (either when we know its too long, or just always do it).

[MithrilMan]

I think I encountered this bug as explained here https://github.com/dotnet/roslyn-sdk/issues/888

[xt0rted]

I'm pretty sure the original report for this came from me, if this is the same issue then here's the project I couldn't get to work. @davidwengier confirmed he couldn't get it to work either.

https://github.com/xt0rted/heroicons-tag-helper/tree/source-generator-debugging

Once cloned run npm ci and then then try to debug the component.