-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not publish in tests.sh #23398
Do not publish in tests.sh #23398
Conversation
{ | ||
directory = Path.GetDirectoryName(directory); | ||
} | ||
return directory == null ? null : path; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the case of directory == null
we should throw an exception. Everything is busted at that point. Should have a declarative error message stating what went wrong.
(Waiting for #23405 to go in, then going to heavily refactor this PR) |
It's gross, but we need to publish *something* until ILAsm is exposed as a normal assembly
else | ||
{ | ||
ilasmExeName = "ilasm"; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider using a conditional operator here.
retest windows_release_unit32_prtest please |
ILAsm is the only asset needed, so put that in CoreToolset
Ping @jaredpar
Note that CoreToolset is currently publishing into
Binaries/Tools
directly. This makes sense for the binary paths (Binaries/Tools/ilasm
), but it clutters the Tools directory immensely (lots of dlls, e.g.System.IO.Pipes.dll
)I also synced the location of
dotnet
to be the same as the place where the windows build installs it, which isBinaries/Tools/dotnet
I also tried running
dotnet-xunit.dll
directly out ofBinaries/Tools
instead of digging into.nuget
, but that was giving super weird errors, so I left that for a later time.Also note that #23316 would be super nice to have here, but that PR has super absurd errors, so that can go in separately.