Skip to content

Conversation

@radekdoulik
Copy link
Member

Instead of trying to create it in the location of the original
assembly as that might not be writable.

Instead of trying to create it in the location of the original
assembly as that might not be writable.
Copy link
Member

@jonathanpeppers jonathanpeppers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we make this test use -o?
https://github.com/xamarin/java.interop/blob/d39699ff541005c1a95338d4a0df6c642f356e24/Makefile#L175-L178

And then make it fail if all the expected assemblies aren't in the output directory?

@radekdoulik
Copy link
Member Author

We might run it twice, so that we test both cases.

@radekdoulik
Copy link
Member Author

build

@radekdoulik
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@radekdoulik radekdoulik merged commit 8ed9677 into dotnet:master Aug 21, 2019
@radekdoulik radekdoulik deleted the pr-put-temporary-assembly-in-o-dir branch August 21, 2019 16:09
steveisok pushed a commit that referenced this pull request Aug 30, 2019
)

Instead of trying to create it in the location of the original
assembly as that might not be writable.

Added test for -o, --keeptemp and -f parameters to test
whether the new and temporary assemblies were created
in the output directory
@github-actions github-actions bot locked and limited conversation to collaborators Apr 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants