Skip to content

Conversation

@cloudRoutine
Copy link
Contributor

@cloudRoutine cloudRoutine commented Nov 17, 2016

gitignore 'tests/fsharpqa/testenv/bin/'

after each build git picks up the detritus

this fixes that

@cloudRoutine
Copy link
Contributor Author

Anyone who has preview3 or preivew4 of the dotnet cli installed on their machine can run into issues when they try to build the coreclr version of fsc, or just use the cli within the repo. global.json locks the SDK version to prevent those issues.

@cloudRoutine cloudRoutine changed the title gitignore 'tests/fsharpqa/testenv/bin/' Minor Build Configuration Improvements Nov 17, 2016
global.json Outdated
@@ -0,0 +1,6 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

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

What are the issues. The repo should only use the cli found in tools\dotnet/cli. If we are not including the path to that when we need to then there is a bug.

So please remove this file. the rest looks great.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the issue arises is when you want to use dotnet <command> in the terminal, like if you want to build, restore, or run only one particular project

Copy link
Contributor Author

Choose a reason for hiding this comment

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

but the hack to make dotnet behave is simple enough too

Copy link
Contributor

@KevinRansom KevinRansom left a comment

Choose a reason for hiding this comment

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

Please remove the global.json

thanks

@mmitche
Copy link
Member

mmitche commented Nov 17, 2016

@dotnet-bot test this please (testing CI move to other server)

@KevinRansom
Copy link
Contributor

Thanks @cloudRoutine

Kevin

@KevinRansom KevinRansom merged commit 9bcfe0b into dotnet:master Nov 17, 2016
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.

4 participants