-
Notifications
You must be signed in to change notification settings - Fork 842
Use dotnet publish to deploy fsharp.core.unittests for coreclr #1733
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
Conversation
KevinRansom
commented
Nov 12, 2016
- Build fsharp.core.dll to nuget package.
- use built nuget package for fsharp.core in fsharp.core.unittests coreclr build
- Get tuplesample.dll from nuget rather than local
- remove a couple of unnecessary nuget.config files
|
@dotnet-bot test this please |
|
Publish + unittests? Where are the unittests published to? And why? Am 12.11.2016 09:50 schrieb "Kevin Ransom (msft)" <[email protected]
@dotnet-bot https://github.com/dotnet-bot test this please — |
|
It uses dotnet publish to move the tests and required dependencies to testbin so that they can run. Previously it was done using hacky file copies. Kevin |
|
Ah Ok. I thought this was dotnet build is already doing. Thx Am 12.11.2016 10:01 schrieb "Kevin Ransom (msft)" <[email protected]
|