You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. For the marority of cases the difference is immaterial. There are a few cases though where the runtime matters:
Tracking down certain classes of analyzer bugs
Performance investigation
The export command should be changed to emit both files to support these scenarios.
The text was updated successfully, but these errors were encountered:
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. For the marority of cases the difference is immaterial. There are a few cases though where the runtime matters:The export command should be changed to emit both files to support these scenarios.
The text was updated successfully, but these errors were encountered: