Repository navigation
We don't need to build FakeSign before CodeAnalysis anymore - #1366
Conversation
|
Oh, is that how that was happening? I guess we did need to make a change for Concord.csproj. |
|
👍 |
1 similar comment
|
👍 |
|
Does FakeSign.exe still get copied to the output (Binaries\Release) folder? It's needed for perf tests (we have to undo the effects of FakeSign in order to ngen Roslyn assemblies) |
|
@dotnet-bot test this please |
|
@pharring this shouldn't change that. It just changes the dependency mapping. Curious though can we change these tools to use the installed NuGet? We want to remove FakeSign from the build and put it in another repo. |
|
@dotnet-bot test this please |
|
@mmitche Jenkins seems to be ignoring our manual "test this please" commands. Have you seen this? |
|
Are you asking for my permission? If so, I have no problem with you switching to use NuGet instead of building FakeSign locally. If you're asking whether it's possible for the perf scripts to get FakeSign via NuGet instead of from the drop, then I don't see a problem with that either. I just wanted to make you aware that we run FakeSign.exe as part of perf setup and that, if it disappears from the binaries drop, then the perf scripts will have to be changed. |
|
@jaredpar It seems to have picked that one up. Are you referring to earlier? It had queued all the builds but was waiting for shutdown for an update or something. |
|
See [Closed]\Test\Performance\Perf-InstallRoslyn.cmd |
We don't need to build FakeSign before CodeAnalysis anymore
…yn-tools/Azure.Identity-1.10.2 Bump Azure.Identity from 1.6.0-beta.1 to 1.10.2 in /src/dotnet-roslyn-tools
This was how we were (trying) to ensure that FakeSign built before projects that needed to be FakeSigned. Now that it's a NuGet package, we don't need this.