Skip to content

We don't need to build FakeSign before CodeAnalysis anymore - #1366

Merged
jasonmalinowski merged 1 commit into
dotnet:masterfrom
jasonmalinowski:master
Mar 18, 2015
Merged

jasonmalinowski merged 1 commit into
dotnet:masterfrom
jasonmalinowski:master

Conversation

@jasonmalinowski

Copy link
Copy Markdown
Member

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.

@jasonmalinowski

Copy link
Copy Markdown
Member Author

Possible reviewers include (but are not limited to) @jaredpar, @amcasey, @agocke.

@amcasey

amcasey commented Mar 18, 2015

Copy link
Copy Markdown
Member

Oh, is that how that was happening? I guess we did need to make a change for Concord.csproj.

@amcasey

amcasey commented Mar 18, 2015

Copy link
Copy Markdown
Member

👍

1 similar comment
@jaredpar

Copy link
Copy Markdown
Member

👍

@pharring

Copy link
Copy Markdown
Contributor

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)

@jaredpar

Copy link
Copy Markdown
Member

@dotnet-bot test this please

@jaredpar

Copy link
Copy Markdown
Member

@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.

@jaredpar

Copy link
Copy Markdown
Member

@dotnet-bot test this please

@jaredpar

Copy link
Copy Markdown
Member

@mmitche Jenkins seems to be ignoring our manual "test this please" commands. Have you seen this?

@pharring

Copy link
Copy Markdown
Contributor

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.

@mmitche

mmitche commented Mar 18, 2015

Copy link
Copy Markdown
Member

@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.

@jaredpar

Copy link
Copy Markdown
Member

@pharring mostly just asking if it was possible to do this. If so I can take care of it. Can you point me in the direction of these scripts so I can update them?

@mmitche I think Jenkins was just waiting for me to complain to you so I could look the fool 😄

@pharring

Copy link
Copy Markdown
Contributor

See [Closed]\Test\Performance\Perf-InstallRoslyn.cmd

jasonmalinowski added a commit that referenced this pull request Mar 18, 2015
We don't need to build FakeSign before CodeAnalysis anymore
@jasonmalinowski
jasonmalinowski merged commit 8205401 into dotnet:master Mar 18, 2015
JoeRobich added a commit that referenced this pull request Aug 18, 2026
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants